[03:01] -queuebot:#ubuntu-release- New sync: passes-gtk (kinetic-proposed/primary) [0.6-1]
[06:28] -queuebot:#ubuntu-release- Unapproved: update-manager (kinetic-proposed/main) [1:22.10.3 => 1:22.10.4] (core)
[09:08] -queuebot:#ubuntu-release- Unapproved: base-files (kinetic-proposed/main) [12.2ubuntu2 => 12.2ubuntu3] (core, i386-whitelist)
[09:19] -queuebot:#ubuntu-release- Unapproved: update-manager (kinetic-proposed/main) [1:22.10.3 => 1:22.10.4] (core)
[09:23] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (kinetic-proposed) [12.2ubuntu3]
[09:28] -queuebot:#ubuntu-release- Unapproved: rejected update-manager [source] (kinetic-proposed) [1:22.10.4]
[09:28] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (kinetic-proposed) [1:22.10.4]
[09:38] <tjaalton> xnox: hi, dkms sru in bug 1991664 is unverified?
[09:38] -ubottu:#ubuntu-release- Bug 1991664 in linux (Ubuntu Jammy) "backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler" [Undecided, Incomplete] https://launchpad.net/bugs/1991664
[10:33] -queuebot:#ubuntu-release- New sync: low-memory-monitor (kinetic-proposed/primary) [2.1-1]
[10:46] -queuebot:#ubuntu-release- New sync: low-memory-monitor (kinetic-proposed/primary) [2.1-1]
[10:47] -queuebot:#ubuntu-release- New: accepted low-memory-monitor [sync] (kinetic-proposed) [2.1-1]
[10:47] -queuebot:#ubuntu-release- New: rejected low-memory-monitor [sync] (kinetic-proposed) [2.1-1]
[10:48] -queuebot:#ubuntu-release- New binary: low-memory-monitor [amd64] (kinetic-proposed/none) [2.1-1] (no packageset)
[10:48] -queuebot:#ubuntu-release- New binary: low-memory-monitor [armhf] (kinetic-proposed/none) [2.1-1] (no packageset)
[10:49] -queuebot:#ubuntu-release- New binary: low-memory-monitor [arm64] (kinetic-proposed/none) [2.1-1] (no packageset)
[10:49] -queuebot:#ubuntu-release- New binary: low-memory-monitor [s390x] (kinetic-proposed/none) [2.1-1] (no packageset)
[10:49] -queuebot:#ubuntu-release- New binary: low-memory-monitor [ppc64el] (kinetic-proposed/none) [2.1-1] (no packageset)
[10:58] -queuebot:#ubuntu-release- Unapproved: mutter (kinetic-proposed/main) [43.0-1ubuntu1 => 43.0-1ubuntu3] (desktop-core, desktop-extra)
[11:01] <jbicha> ubuntu-release: please review mutter 43.0-1ubuntu3 for inclusion in kinetic
[11:01] -queuebot:#ubuntu-release- Unapproved: tzdata (kinetic-proposed/main) [2022e-0ubuntu1 => 2022e-0ubuntu2] (core)
[11:05] -queuebot:#ubuntu-release- New binary: low-memory-monitor [riscv64] (kinetic-proposed/universe) [2.1-1] (no packageset)
[11:06] <sil2100> jbicha: is this a release blocker? Since we looked at the bug and it didn't feel release critical, at least not as it was written there (the nightlight one)
[11:06] <sil2100> ah, follow up upload
[11:07] <jbicha> it doesn't seem a common crasher, but I think it would block people with strange hardware from being able to use kinetic
[11:07] <sil2100> jbicha: how easy to reproduce the crash is? The bug isn't very specific to give us a good feel of how easy to repdoruce it is
[11:08] <sil2100> Is it just a crash on start or at random times for those people?
[11:09] <sil2100> Since it's a lot of patches, I'm always a bit reluctant with bigger patches right before we spin image candidates
[11:09] <jbicha> from the GNOME and Debian bug reports, I think it's a crash at start. One of the patches adds a test for this issue
[11:10] <jbicha> all the patches for this and the Night Light fix are cherry-picks from the future mutter 43.1
[11:18] -queuebot:#ubuntu-release- Unapproved: rejected mutter [source] (kinetic-proposed) [43.0-1ubuntu2]
[11:18] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (kinetic-proposed) [2022e-0ubuntu2]
[11:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Kinetic Final] (20221017) has been added
[11:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Kinetic Final] (20221017) has been added
[11:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Kinetic Final] (20221017) has been added
[11:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Kinetic Final] (20221017) has been added
[11:20] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Kinetic Final] (20221017) has been added
[11:21] <sil2100> ^ that is not true
[11:21] <sil2100> Those are not yet the release candidates
[11:22] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-drivers-common [source] (jammy-proposed) [1:0.9.6.2~0.22.04.1]
[11:23] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-drivers-common [source] (focal-proposed) [1:0.9.0~0.20.04.8]
[11:41] -queuebot:#ubuntu-release- Unapproved: tracker-miners (kinetic-proposed/main) [3.4.0-1 => 3.4.0-1ubuntu1] (ubuntu-desktop, ubuntugnome)
[11:52] <jbicha> sil2100: tracker-miners might be worth including too
[12:01] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (jammy-proposed) [264-1ubuntu0.22.04.1]
[12:04] <seb128> the tracker one is basically a one liner adapting for a end-of-cycle glib change which added a syscall use which isn't in the whitelest of the confinement, which triggers indexer errors, it's current one of the top kinetic errors and seems worth taking since the fix is trivial
[12:09] -queuebot:#ubuntu-release- Unapproved: rejected s390-tools-signed [source] (jammy-proposed) [2.20.0-0ubuntu3.2]
[12:14] -queuebot:#ubuntu-release- Unapproved: accepted tableau-parm [source] (jammy-proposed) [0.2.0-6build0.1]
[12:15] -queuebot:#ubuntu-release- Unapproved: accepted zfcp-hbaapi [source] (jammy-proposed) [2.2.0-0ubuntu1.1]
[12:17] <tjaalton> sil2100: fyi, I'm checking the jammy queue now, started from the oldest
[12:19] <sil2100> tjaalton: thanks!
[12:21] <sil2100> seb128, jbicha: I'll take the tracker-miners one, but since I want to build image candidates soonish, I won't block on it going to the release pocket
[12:22] -queuebot:#ubuntu-release- Unapproved: accepted tracker-miners [source] (kinetic-proposed) [3.4.0-1ubuntu1]
[12:27] <sil2100> Okay everyone! Since we're still waiting on new raspi kernels, I'm thinking of waiting for migration of some of the items we have in -proposed, then puttin on the freeze block and building all non-raspi candidate images
[12:27] <sil2100> With the freeze in place, I think we should be able to just rebuild raspi once that's available
[12:27] -queuebot:#ubuntu-release- Unapproved: accepted edk2 [source] (jammy-proposed) [2022.02-3ubuntu0.22.04.1]
[12:31] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-default-settings [source] (jammy-proposed) [22.04.26.1]
[12:39] -queuebot:#ubuntu-release- Unapproved: accepted qreator [source] (jammy-proposed) [16.06.1-7ubuntu1]
[12:42] -queuebot:#ubuntu-release- Unapproved: accepted php8.1 [source] (jammy-proposed) [8.1.2-1ubuntu2.6]
[12:44] <sil2100> grrr, we'll have to wait for tzdata
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted unbound [source] (jammy-proposed) [1.13.1-1ubuntu5.2]
[12:54] <seb128> sil2100, thanks!
[12:56] -queuebot:#ubuntu-release- Unapproved: xapian-omega (kinetic-proposed/universe) [1.4.21-2 => 1.4.21-4] (no packageset) (sync)
[12:56] -queuebot:#ubuntu-release- Unapproved: accepted xapian-omega [sync] (kinetic-proposed) [1.4.21-4]
[13:01] -queuebot:#ubuntu-release- Unapproved: accepted apport [source] (jammy-proposed) [2.20.11-0ubuntu82.2]
[13:04] -queuebot:#ubuntu-release- Unapproved: rejected apport [source] (focal-proposed) [2.20.11-0ubuntu27.25]
[13:05] -queuebot:#ubuntu-release- Unapproved: flash-kernel (kinetic-proposed/main) [3.106ubuntu7 => 3.106ubuntu8] (core)
[13:06] -queuebot:#ubuntu-release- Unapproved: accepted apport [source] (focal-proposed) [2.20.11-0ubuntu27.25]
[13:15] -queuebot:#ubuntu-release- Unapproved: accepted libp11 [source] (jammy-proposed) [0.4.11-1ubuntu0.22.04.1]
[13:25] -queuebot:#ubuntu-release- Unapproved: accepted nullboot [source] (jammy-proposed) [0.4.0-0ubuntu0.22.04.1]
[13:28] -queuebot:#ubuntu-release- Unapproved: accepted apache2 [source] (jammy-proposed) [2.4.52-1ubuntu4.2]
[13:34] <sil2100> bdmurray, vorlon, ginggs: let's keep an eye out for final things to migrate out of -proposed, like base-files and tzdata
[13:34] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (jammy-proposed) [8.0.0-1ubuntu7.3]
[13:37] <jbicha> sil2100: the mutter crash seems really bad for someone with hardware that isn't reporting the correct color data. Before Ubuntu 22.04 release we were aggressive in cherry-picking mutter fixes. This time we are being more selective.
[13:39] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (jammy-proposed) [2.765.11]
[13:42] -queuebot:#ubuntu-release- Unapproved: accepted flash-kernel [source] (jammy-proposed) [3.104ubuntu14]
[13:51] -queuebot:#ubuntu-release- Unapproved: bluedevil (jammy-proposed/universe) [4:5.24.6-0ubuntu0.1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:51] -queuebot:#ubuntu-release- Unapproved: kdeplasma-addons (jammy-proposed/universe) [4:5.24.6-0ubuntu0.1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:51] -queuebot:#ubuntu-release- Unapproved: kscreen (jammy-proposed/universe) [4:5.24.6-0ubuntu0.1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: breeze (jammy-proposed/universe) [4:5.24.6-0ubuntu0.1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: kwin (jammy-proposed/universe) [4:5.24.6-0ubuntu0.1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: kinfocenter (jammy-proposed/universe) [4:5.24.6-0ubuntu0.1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: plasma-desktop (jammy-proposed/universe) [4:5.24.6-0ubuntu0.1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: plasma-pa (jammy-proposed/universe) [4:5.24.5-0ubuntu0.1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: plasma-workspace (jammy-proposed/universe) [4:5.24.6-0ubuntu0.1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: xdg-desktop-portal-kde (jammy-proposed/universe) [5.24.6-0ubuntu0.1 => 5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: plasma-discover (jammy-proposed/universe) [5.24.6-0ubuntu0.1 => 5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: powerdevil (jammy-proposed/universe) [4:5.24.4-0ubuntu1 => 4:5.24.7-0ubuntu0.1] (kubuntu)
[13:52] -queuebot:#ubuntu-release- Unapproved: plasma-thunderbolt (jammy-proposed/universe) [5.24.4-0ubuntu1 => 5.24.7-0ubuntu0.1] (kubuntu)
[14:19] -queuebot:#ubuntu-release- Unapproved: insighttoolkit4 (kinetic-proposed/universe) [4.13.3withdata-dfsg2-3ubuntu1 => 4.13.3withdata-dfsg2-3ubuntu2] (no packageset)
[14:20] -queuebot:#ubuntu-release- Unapproved: accepted insighttoolkit4 [source] (kinetic-proposed) [4.13.3withdata-dfsg2-3ubuntu2]
[14:53] <seb128> sil2100, extra context on what jbicha said before, the impact of the crash is that the session would close on login so basically the system can't be used for those users. We don't know which hardware is impacted exactly but it could turn out to be a blocker in the week, Daniel said it was the top report gnome-shell issue on e.u.c
[14:59] <paride> sil2100, when testing the arm64 subiquity images the installer (subiquity or curtin, not sure) crashes while doing the actual installation (last stage, copying files)
[14:59] <bdmurray> sil2100: if the ubuntu server subiquity images aren't the final one shouldn't we mark them as disabled?
[14:59] <paride> I'm now trying to extract logs
[14:59] <paride> dbungert, ^^
[15:00] <bdmurray> paride: I think sil2100 previously said those weren't vaild - so that's my bad
[15:00] <sil2100> bdmurray: we'll be respinning those anyway, so I just left them there as is!
[15:00] <sil2100> But yeah, someone can remove those from the tracker if anything
[15:00] <paride> oh well, let's hope the new respin will work
[15:01] <bdmurray> sil2100: but "mark as disabled (prevents result reporting)"
[15:01] -queuebot:#ubuntu-release- Unapproved: pixman (focal-proposed/main) [0.38.4-0ubuntu1 => 0.38.4-0ubuntu2] (core, i386-whitelist, xorg)
[15:04] <bdmurray> we actually think testing those images would be good
[15:04] <dbungert> paride: we have a pending fix for a umount error, hopefully it's the same item
[15:05] <bdmurray> dbungert: do you have a bug for that?
[15:05] <ginggs> sil2100: bdmurray: rmadison says tzdata has just migrated
[15:05] <sil2100> \o/
[15:06] <dbungert> bug 1992977
[15:06] -ubottu:#ubuntu-release- Bug 1992977 in subiquity (Ubuntu) "Installer fails in step 'Third party drivers'" [Undecided, In Progress] https://launchpad.net/bugs/1992977
[15:07] <bdmurray> Is it just riscv64 specific?
[15:08] <dbungert> doubtful
[15:16] <paride> I think I just hit https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664 again
[15:16] -ubottu:#ubuntu-release- Launchpad bug 1921664 in qemu (Fedora) "Coroutines are racy for risc64 emu on arm64 - crash on Assertion" [Medium, In Progress]
[15:23] <dbungert> paride: any luck on getting logs out?
[15:24] <paride> dbungert, now I'm betting it's https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664, so not a subiquity/curtin bug
[15:24] -ubottu:#ubuntu-release- Launchpad bug 1921664 in qemu (Fedora) "Coroutines are racy for risc64 emu on arm64 - crash on Assertion" [Medium, In Progress]
[15:24] <paride> verifying right now
[15:28] <sil2100> Hey everyone! Freeze block is now in place o/
[16:01] <tsimonq2> \o/
[16:03] <paride> dbungert, so a manual install worked fine with qemu compiled without LTO, let's see how the automated smoke test behaves
[16:04] <dbungert> paride: appreciate it.  When you feel reasonable certain about this I want to build tagged snaps.
[16:31] <sil2100> dbungert: could you cut a new subiquity release now, if possible?
[16:32] <dbungert> sil2100: more or less, risc-v snap is an hour
[16:32] <sil2100> We wanted to build some release candidates soon
[16:32] <sil2100> Oh nooo
[16:32] <sil2100> Okay
[16:32] <dbungert> I'll start the process
[16:33] <paride> dbungert, so in automation I'm hitting another error (arm64 only): `[    1.988709] Initramfs unpacking failed: write error`, `/init: line 150: modprobe: not found`. However if I try manually on the same machine it works
[16:33] <sil2100> dbungert: can you give us a sign once the subiquity snaps are all in stable?
[16:33] <dbungert> sil2100: +1
[16:33] <paride>  don't think it's a subiquity bug, still I want see it go away
[16:34] <dbungert> makes sense
[16:35] <dbungert> https://launchpad.net/builders/riscv64-qemu-lgw01-005
[16:36] <sil2100> I think the plan right now is: we'll spin all the images that do not use subiquity, and once the snaps are published, we'll spin the server ones
[16:37] <dbungert> if it helps, most of them will be read in a few minutes
[16:37] <dbungert> ready
[16:42] -queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (kinetic-proposed) [43.0-1ubuntu3]
[16:50] -queuebot:#ubuntu-release- Unapproved: accepted flash-kernel [source] (kinetic-proposed) [3.106ubuntu8]
[17:01] <vorlon> dbungert: easier in terms of build system mechanics to wait for the snap on all archs and kick all image builds at once.  We know riscv64 image builds will be the long pole anyway
[17:02] <paride> bdmurray, arm64 passed in automation
[17:02] <paride> I'm happy again
[17:02] <paride> (I had to bump the amount of RAM we test with. Still lower than the officially recommended so OK.)
[17:21] <vorlon> initial release image candidates have been kicked off for everything except for: Ubuntu Desktop (mutter, flash-kernel), Ubuntu Server (subiquity, flash-kernel), Ubuntu Budgie (mutter)
[17:22] <vorlon> iso tracker should start to see some updates within the hour
[17:22] <vorlon> please test!
[17:22] <RikMills> \o/
[17:22] <tsimonq2> 🎉
[17:29] <vorlon> lol botched that with a wrong environment variable, just tried to build all flavors for amd64+intel-iot
[17:29] <vorlon> cancelling
[17:29] <vorlon> and restarting
[17:29] <tsimonq2> 🎉 ➡️ 😥 ➡️ 🎉
[17:29] <tsimonq2> :P
[17:40] <tsimonq2> `LiveFS lubuntu-intel-iot/kinetic/amd64+intel-iot failed to build on 20221017` ha
[17:46] -queuebot:#ubuntu-release- New sync: mint-y-icons (kinetic-proposed/primary) [1.6.1-1]
[17:51] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Kinetic Final] (20221017.1) has been added
[17:52] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Kinetic Final] (20221017.2) has been added
[17:54] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Kinetic Final] (20221017.2) has been added
[17:55] -queuebot:#ubuntu-release- Builds: Ubuntu Unity Desktop amd64 [Kinetic Final] (20221017.1) has been added
[17:56] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Kinetic Final] (20221017.2) has been added
[18:03] -queuebot:#ubuntu-release- Unapproved: gnome-desktop (jammy-proposed/main) [42.4-0ubuntu1 => 42.5-0ubuntu1] (ubuntu-desktop)
[18:03] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Kinetic Final] (20221017.1) has been added
[18:24] <bdmurray> jbicha: mutter failed to build on armhf and riscv64
[18:26] <bdmurray> or maybe just armhf
[19:02] <dbungert> sil2100: subiquity risc-v snap promoted to stable/ubuntu-22.10
[19:02] <sergiodj> hi, spaln doesn't build on 32-bit architectures anymore and therefore needs to be blacklisted (and removed) on armhf, can some AA do that please?
[19:03] <sergiodj> I'm working on the FTBFS that's affecting riscv64
[19:07] -queuebot:#ubuntu-release- Unapproved: mutter (jammy-proposed/main) [42.2-0ubuntu1 => 42.5-0ubuntu1] (desktop-core, desktop-extra)
[19:22] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Kinetic Final] has been disabled
[19:22] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Kinetic Final] has been disabled
[19:22] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Kinetic Final] has been disabled
[19:22] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Kinetic Final] has been disabled
[19:22] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Kinetic Final] has been disabled
[19:28] -queuebot:#ubuntu-release- Unapproved: snapd (jammy-proposed/main) [2.56.2+22.04ubuntu1 => 2.57.4+22.04] (desktop-core, ubuntu-server)
[19:33] <vorlon> sergiodj: are you asking because you're on +1 maintenance this week or is there some more urgent purpose?
[19:33] <vorlon> sergiodj: (it doesn't need blacklisted ftr, just binaries removed)
[19:34] <vorlon> sergiodj: removed, with the rationale that Debian has also removed the armhf binary and this version has been released to testing
[19:35] <vorlon> dbungert: so subiquity is good to go for release on all archs?
[19:36] <dbungert> vorlon: I believe so
[19:39] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Kinetic Final] (20221017.1) has been added
[19:39] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Kinetic Final] (20221017.1) has been added
[19:39] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Kinetic Final] (20221017.1) has been added
[19:39] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Kinetic Final] (20221017.1) has been added
[19:39] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Kinetic Final] (20221017.1) has been added
[19:40] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Kinetic Final] (20221017.1) has been added
[19:48] <vorlon> suspicious that base took so long to build
[19:53] <vorlon> ah just riscv64 being the long pole again
[19:55] <sergiodj> vorlon: I'm on +1 maintenance this week.  I understand we're on Final Freeze and I'm not expecting my requests to be addressed in a timely manner, FWIW.  thank you.
[19:56] <vorlon> sergiodj: ok - if there is anything with a more urgent rationale that comes up, just tag it and we'll process accordingly, thanks
[20:13] <vorlon> why has https://people.canonical.com/~ubuntu-archive/proposed-migration/kinetic_uninst.txt increased >_<
[20:14] <vorlon> aha, I did it!
[20:14] <vorlon> fixing ;)
[20:14] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (kinetic-proposed/main) [2.790 => 2.791] (desktop-core, i386-whitelist)
[20:16] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (kinetic-proposed) [2.791]
[20:17] <bdmurray> vorlon: ^
[20:17] <vorlon> bdmurray: ^ ;)
[20:17] <bdmurray> I see that now
[20:19] -queuebot:#ubuntu-release- Unapproved: mozillavpn (kinetic-proposed/universe) [2.2.0-1 => 2.2.0-1ubuntu1] (no packageset)
[20:20] -queuebot:#ubuntu-release- Unapproved: accepted mozillavpn [source] (kinetic-proposed) [2.2.0-1ubuntu1]
[20:57] <vorlon> flash-kernel and subiquity are published; spinning ubuntu-server candidates
[20:58] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (jammy-proposed) [2.57.4+22.04]
[21:04] -queuebot:#ubuntu-release- Unapproved: libidn2 (kinetic-proposed/main) [2.3.3-1 => 2.3.3-1build1] (core, i386-whitelist)
[21:36] <vorlon> ^ an opportunistic no-change rebuild to fix a misbuild I'm presumptively blaming on debhelper; it's not critical for the release
[22:13] -queuebot:#ubuntu-release- New: accepted low-memory-monitor [riscv64] (kinetic-proposed) [2.1-1]
[22:13] -queuebot:#ubuntu-release- New: accepted astra-toolbox [amd64] (kinetic-proposed) [2.1.0-1]
[22:13] -queuebot:#ubuntu-release- New: accepted astra-toolbox [ppc64el] (kinetic-proposed) [2.1.0-1]
[22:13] -queuebot:#ubuntu-release- New: accepted low-memory-monitor [arm64] (kinetic-proposed) [2.1-1]
[22:13] -queuebot:#ubuntu-release- New: accepted low-memory-monitor [ppc64el] (kinetic-proposed) [2.1-1]
[22:13] -queuebot:#ubuntu-release- New: accepted astra-toolbox [arm64] (kinetic-proposed) [2.1.0-1]
[22:14] -queuebot:#ubuntu-release- New: accepted low-memory-monitor [armhf] (kinetic-proposed) [2.1-1]
[22:14] -queuebot:#ubuntu-release- New: accepted low-memory-monitor [amd64] (kinetic-proposed) [2.1-1]
[22:14] -queuebot:#ubuntu-release- New: accepted low-memory-monitor [s390x] (kinetic-proposed) [2.1-1]
[22:43] <vorlon> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt that's the kind of update-output I like to see
[23:21] <vorlon> sergiodj: if you're keen, it looks like spirv-llvm-translator-14 requires Ubuntu-specific reconciliation of the .symbols files (looking at which archs do/don't build, I'm going to suggest it's LTO-related)
[23:54] <sergiodj> vorlon: I will add it to my TODO list for tomorrow