[00:13] -queuebot:#ubuntu-release- New binary: libppd [amd64] (lunar-proposed/universe) [2:2.0~b4-0ubuntu1] (no packageset)
[00:14] -queuebot:#ubuntu-release- New binary: libppd [arm64] (lunar-proposed/universe) [2:2.0~b4-0ubuntu1] (no packageset)
[00:15] -queuebot:#ubuntu-release- New binary: libppd [s390x] (lunar-proposed/universe) [2:2.0~b4-0ubuntu1] (no packageset)
[00:15] -queuebot:#ubuntu-release- New binary: libppd [ppc64el] (lunar-proposed/universe) [2:2.0~b4-0ubuntu1] (no packageset)
[00:43] <tsimonq2> What time in UTC is Feature Freeze? (Do we have a set time anymore?)
[00:43] <tsimonq2> (No, I don't have any last minute stack uploads... this cycle. :P)
[00:45] <bdmurray> Something like EOD Pacific time.
[00:58] <tsimonq2> Okay, cool.
[01:27] <sil2100> o/
[02:55] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Jammy 22.04.2] has been marked as ready
[04:16] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy 22.04.2] has been updated (20230223)
[04:19] <bdmurray> That'll need testing ^^
[04:20] <arraybolt3> Understood.
[04:21] <arraybolt3> zsyncing now.
[04:27] <arraybolt3> bdmurray: I see this fixes the Broadcom bug, I'm not sure whether I should test for the no-network + different keyboard layout crash bug or not.
[04:28] <arraybolt3> Are the new images supposed to have both resolved, or only just the first one?
[04:29] <arraybolt3> Er, not keyboard layout, I mean en-GB locale.
[04:31] <bdmurray> arraybolt3: It should fix https://bugs.launchpad.net/ubuntu-cdimage/+bug/2008082
[04:31] -ubottu:#ubuntu-release- Launchpad bug 2008082 in Ubuntu CD Images "Install crash with broadcom wifi" [Critical, Triaged]
[04:32] <arraybolt3> Oh, I got it mixed up with bug 2008120. Thanks for clarification.
[04:32] -ubottu:#ubuntu-release- Bug 2008120 in ubiquity (Ubuntu) "Third-party drivers are silently left unsigned when installing Ubuntu Desktop on a system with Secure Boot, Broadcom WiFi, and LVM+encryption" [Undecided, Confirmed] https://launchpad.net/bugs/2008120
[04:33] <arraybolt3> (I see you said which bug it was earlier but for some reason I got it scrambled.)
[04:47] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Jammy 22.04.2] has been updated (20230223)
[04:49] <arraybolt3> bdmurray: Works!
[04:49] <arraybolt3> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2008082/comments/9
[04:49] -ubottu:#ubuntu-release- Launchpad bug 2008082 in Ubuntu CD Images "Install crash with broadcom wifi" [Critical, Triaged]
[04:49] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Jammy 22.04.2] has been updated (20230223)
[04:52] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Jammy 22.04.2] has been updated (20230223)
[04:52] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Jammy 22.04.2] has been updated (20230223)
[04:52] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Jammy 22.04.2] has been updated (20230223)
[07:42] -queuebot:#ubuntu-release- New: accepted dm-writeboost [amd64] (lunar-proposed) [2.2.16-0.1]
[07:42] -queuebot:#ubuntu-release- New: accepted harpwise [amd64] (lunar-proposed) [3.18.10-0ubuntu2]
[07:43] -queuebot:#ubuntu-release- New: accepted tzdata [amd64] (lunar-proposed) [2022g-7ubuntu1]
[07:48] <sil2100> o/
[08:18] -queuebot:#ubuntu-release- New: accepted webkit2gtk [amd64] (lunar-proposed) [2.39.90-1ubuntu1]
[08:18] -queuebot:#ubuntu-release- New: accepted webkit2gtk [i386] (lunar-proposed) [2.39.90-1ubuntu1]
[08:18] -queuebot:#ubuntu-release- New: accepted webkit2gtk [s390x] (lunar-proposed) [2.39.90-1ubuntu1]
[08:18] -queuebot:#ubuntu-release- New: accepted webkit2gtk [armhf] (lunar-proposed) [2.39.90-1ubuntu1]
[08:18] -queuebot:#ubuntu-release- New: accepted webkit2gtk [ppc64el] (lunar-proposed) [2.39.90-1ubuntu1]
[08:59] -queuebot:#ubuntu-release- New: accepted aad-auth [source] (lunar-proposed) [0.4]
[09:06] -queuebot:#ubuntu-release- New binary: aad-auth [amd64] (lunar-proposed/none) [0.4] (no packageset)
[09:08] -queuebot:#ubuntu-release- New binary: aad-auth [arm64] (lunar-proposed/none) [0.4] (no packageset)
[09:08] -queuebot:#ubuntu-release- New binary: aad-auth [s390x] (lunar-proposed/none) [0.4] (no packageset)
[09:08] -queuebot:#ubuntu-release- New binary: aad-auth [armhf] (lunar-proposed/none) [0.4] (no packageset)
[09:09] -queuebot:#ubuntu-release- New binary: aad-auth [ppc64el] (lunar-proposed/none) [0.4] (no packageset)
[10:56] -queuebot:#ubuntu-release- New binary: rustc [amd64] (lunar-proposed/main) [1.67.1+dfsg0ubuntu1-0ubuntu2] (i386-whitelist)
[11:02] -queuebot:#ubuntu-release- New binary: rustc [s390x] (lunar-proposed/main) [1.67.1+dfsg0ubuntu1-0ubuntu2] (i386-whitelist)
[11:14] -queuebot:#ubuntu-release- New binary: vertx-docgen [amd64] (lunar-proposed/none) [0.9.4-1] (no packageset)
[11:17] -queuebot:#ubuntu-release- New binary: poliastro [amd64] (lunar-proposed/none) [0.17.0-2] (no packageset)
[11:30] -queuebot:#ubuntu-release- New binary: aad-auth [riscv64] (lunar-proposed/universe) [0.4] (no packageset)
[11:57] <juliank> Should we force-skiptest icu?
[11:58] <juliank> It's blocked by boosts which are now set to never run
[11:58] <juliank> And pyicu is needly waiting for a neutral run
[11:59] <juliank> Why is OLD_NEUTRAL considered "No test results?"
[11:59] <juliank> Or rather we should force-badtest the boost
[12:00] <juliank> and I guess force-skiptest pyicu/2.10.2-1build1 too rather than wait for the arm64 queue to tell us it's still neutral
[12:00] <juliank> (openlp is neutral because there's no tests in it)
[12:04] -queuebot:#ubuntu-release- New binary: rustc [armhf] (lunar-proposed/main) [1.67.1+dfsg0ubuntu1-0ubuntu2] (i386-whitelist)
[12:12] -queuebot:#ubuntu-release- New: accepted poliastro [amd64] (lunar-proposed) [0.17.0-2]
[12:12] -queuebot:#ubuntu-release- New: accepted vertx-docgen [amd64] (lunar-proposed) [0.9.4-1]
[12:51] -queuebot:#ubuntu-release- New binary: rustc [arm64] (lunar-proposed/main) [1.67.1+dfsg0ubuntu1-0ubuntu2] (i386-whitelist)
[12:53] -queuebot:#ubuntu-release- New binary: libppd [amd64] (lunar-proposed/universe) [2:2.0~b4-0ubuntu2] (no packageset)
[12:53] -queuebot:#ubuntu-release- New binary: libppd [armhf] (lunar-proposed/universe) [2:2.0~b4-0ubuntu2] (no packageset)
[12:53] -queuebot:#ubuntu-release- New binary: libppd [s390x] (lunar-proposed/universe) [2:2.0~b4-0ubuntu2] (no packageset)
[12:53] -queuebot:#ubuntu-release- New binary: libppd [arm64] (lunar-proposed/universe) [2:2.0~b4-0ubuntu2] (no packageset)
[12:53] -queuebot:#ubuntu-release- New binary: libppd [ppc64el] (lunar-proposed/universe) [2:2.0~b4-0ubuntu2] (no packageset)
[13:31] <sil2100> Hello hello! Final stretch! Please test the iso images for 22.04.2!
[13:35] -queuebot:#ubuntu-release- New binary: libppd [riscv64] (lunar-proposed/universe) [2:2.0~b4-0ubuntu2] (no packageset)
[13:55] -queuebot:#ubuntu-release- New: accepted aad-auth [amd64] (lunar-proposed) [0.4]
[13:56] -queuebot:#ubuntu-release- New: accepted aad-auth [armhf] (lunar-proposed) [0.4]
[13:56] -queuebot:#ubuntu-release- New: accepted aad-auth [riscv64] (lunar-proposed) [0.4]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [amd64] (lunar-proposed) [2:2.0~b4-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [ppc64el] (lunar-proposed) [2:2.0~b4-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [amd64] (lunar-proposed) [2:2.0~b4-0ubuntu2]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [armhf] (lunar-proposed) [2:2.0~b4-0ubuntu2]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [riscv64] (lunar-proposed) [2:2.0~b4-0ubuntu2]
[13:56] -queuebot:#ubuntu-release- New: accepted aad-auth [arm64] (lunar-proposed) [0.4]
[13:56] -queuebot:#ubuntu-release- New: accepted aad-auth [s390x] (lunar-proposed) [0.4]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [s390x] (lunar-proposed) [2:2.0~b4-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [ppc64el] (lunar-proposed) [2:2.0~b4-0ubuntu2]
[13:56] -queuebot:#ubuntu-release- New: accepted aad-auth [ppc64el] (lunar-proposed) [0.4]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [arm64] (lunar-proposed) [2:2.0~b4-0ubuntu2]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [arm64] (lunar-proposed) [2:2.0~b4-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted libppd [s390x] (lunar-proposed) [2:2.0~b4-0ubuntu2]
[13:59] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Jammy 22.04.2] has been marked as ready
[14:22] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Jammy 22.04.2] has been marked as ready
[14:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Jammy 22.04.2] has been marked as ready
[14:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Jammy 22.04.2] has been marked as ready
[14:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Jammy 22.04.2] has been marked as ready
[14:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Jammy 22.04.2] has been marked as ready
[14:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Jammy 22.04.2] has been marked as ready
[14:51] <dbungert> sil2100: you inquired specifically about the Ubuntu Pro attach status for 22.04.2 with live server, I just ran that test and it is working fine.
[15:46] <sil2100> dbungert: more good news then, thank you!
[16:03] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Jammy 22.04.2] has been marked as ready
[16:03] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Jammy 22.04.2] has been marked as ready
[16:03] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+icicle [Jammy 22.04.2] has been marked as ready
[16:03] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+licheerv [Jammy 22.04.2] has been marked as ready
[16:03] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+nezha [Jammy 22.04.2] has been marked as ready
[16:03] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Jammy 22.04.2] has been marked as ready
[16:03] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive [Jammy 22.04.2] has been marked as ready
[16:05] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Jammy 22.04.2] has been marked as ready
[16:05] <sil2100> Any volunteers to check up on the arm* base tarballs?
[16:05] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy 22.04.2] has been marked as ready
[16:05] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Jammy 22.04.2] has been marked as ready
[16:05] <sil2100> waveform, jawn-smith, danilogondolfo: ^ ?
[16:08] <waveform> sil2100, will take a look this afternoon but quite a bit on the ISO tracker is already marked done (many thanks to pwlars and dviererbe)
[16:09] <sil2100> waveform: yes yes, but I mean the ubuntu-base tarball ones, I think the arm ones didn't get tested yet
[16:09] <sil2100> And you have easy access to arm* hardware :)
[16:15] <paride> sil2100, hey, I marked the subiquity images as ready
[16:15] <dbungert> :tada:
[16:21] <sil2100> paride: \o/
[16:37] <sil2100> Any volunteers for the remaining base  tarball tests?
[16:37] <sil2100> I don't expect any issues, so basically in like 15-20 minutes I'll start the point-release process
[16:38] <sil2100> It's done on mirrors being disabled, so until I switch then on, we can always back off
[17:01] -queuebot:#ubuntu-release- Unapproved: ubuntu-drivers-common (jammy-proposed/main) [1:0.9.6.2~0.22.04.1 => 1:0.9.6.2~0.22.04.2] (desktop-core)
[17:01] -queuebot:#ubuntu-release- Unapproved: ubuntu-drivers-common (kinetic-proposed/main) [1:0.9.6.3 => 1:0.9.6.3.1] (desktop-core)
[17:04] <danilogondolfo> sil2100: ack
[17:05] <xnox> sil2100:  this is suspiciously sounds like https://launchpad.net/ubuntu/+source/dkms/3.0.6-4 but sounds different as none of those regressions are in jammy
[17:06] <sil2100> xnox: yep! But we confirmed that the dmks issues with broadcom have been actually already present in .1
[17:06] <sil2100> So oh well
[17:07] <sil2100> Ok, releasing!
[17:07] <xnox> fun
[17:07] <xnox> go ahead =)
[17:08] <xnox> vorlon:  re:dkms in lunar bug filed, triaged, and partial revert of upstream change uploaded https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2008269
[17:08] -ubottu:#ubuntu-release- Launchpad bug 2008269 in dkms (Ubuntu) "dkms prevents installing vendored-in dkms packages" [Critical, Fix Committed]
[17:08] <xnox> the revert returns to status quo, i guess we separately should decide what we want.
[17:12] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Jammy 22.04.2] has been marked as ready
[17:12] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Jammy 22.04.2] has been marked as ready
[17:12] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Jammy 22.04.2] has been marked as ready
[17:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Jammy 22.04.2] has been marked as ready
[17:13] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Jammy 22.04.2] has been marked as ready
[17:13] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Jammy 22.04.2] has been marked as ready
[17:13] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Jammy 22.04.2] has been marked as ready
[17:13] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Jammy 22.04.2] has been marked as ready
[17:13] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Jammy 22.04.2] has been marked as ready
[17:22] <adrien> can someone re-trigger https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=plplot&trigger=tcl8.6%2F8.6.13%2Bdfsg-2 (timeout before running the tests) and https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=openmsx&trigger=tcl8.6%2F8.6.13%2Bdfsg-2 (there's a "sleep 3" to wait for the app to start and I think that might have not been enough; there's no
[17:22] <adrien> apparent difference between failing and succeeding logs apart from two lines reversed)
[17:22] <enr0n> sil2100: The link to the base tarball in the iso tracker for (at least) ppc64el appears to be broken: http://iso.qa.ubuntu.com/qatracker/milestones/442/builds/271718/downloads
[17:36] <danilogondolfo> are these the base images? https://cdimage.ubuntu.com/ubuntu-base/jammy/daily/20230217.1/
[17:36] <danilogondolfo> looks like the links are missing a /jammy/
[17:53] <sil2100> Yeah, it's a bit of a manual process to get those updated
[18:11] <sil2100> Thank you for all the testing everyone!
[18:11] <sil2100> ...syncing mirrors in a minute!
[18:30] <luna_> Any ETA for the 22.04.2 LTS?
[18:35] <bdmurray> sometime today
[18:36] <luna_> ah the iso that is, bdmurray thanks
[18:36] <sil2100> It's being released as we speak
[18:36] <sil2100> Still some time needed though
[18:36] <luna_> sil2100: alright will wait until its on some mirror to download then thanks :)
[18:44] <luna_> won't disturb the building
[18:56] -queuebot:#ubuntu-release- New binary: libcupsfilters [amd64] (lunar-proposed/universe) [2.0~b4-0ubuntu1] (no packageset)
[18:56] -queuebot:#ubuntu-release- New binary: libcupsfilters [s390x] (lunar-proposed/universe) [2.0~b4-0ubuntu1] (no packageset)
[18:57] -queuebot:#ubuntu-release- New binary: libcupsfilters [arm64] (lunar-proposed/universe) [2.0~b4-0ubuntu1] (no packageset)
[18:57] -queuebot:#ubuntu-release- New binary: libcupsfilters [ppc64el] (lunar-proposed/universe) [2.0~b4-0ubuntu1] (no packageset)
[19:12] -queuebot:#ubuntu-release- New binary: mutter [s390x] (lunar-proposed/main) [44~beta-3ubuntu2] (desktop-core, desktop-extra)
[19:19] -queuebot:#ubuntu-release- New binary: mutter [ppc64el] (lunar-proposed/main) [44~beta-3ubuntu2] (desktop-core, desktop-extra)
[19:20] <bdmurray> arraybolt3: Have you tested bug 2008120 after the respin?
[19:20] -ubottu:#ubuntu-release- Bug 2008120 in ubiquity (Ubuntu) "Third-party drivers are silently left unsigned when installing Ubuntu Desktop on a system with Secure Boot, Broadcom WiFi" [Undecided, Confirmed] https://launchpad.net/bugs/2008120
[19:20] <arraybolt3> bdmurray: Yes, at the same time as the other Broadcom bug - it was still present.
[19:20] <bdmurray> While I see the same error message in the install log the module is loaded after rebooting
[19:20] <arraybolt3> Was there another respin after I last announced success?
[19:21] <arraybolt3> (I think that error in the install log is normal since of course the signed driver won't load until after the MOK is enrolled, and the MOK isn't enrolled until after the installation.)
[19:21] <arraybolt3> But it ought to work once the MOK is enrolled and the installed system is booted.
[19:22] <bdmurray> Okay, I'm saying it does work for me with 20230223 but I also have nvidia installed so maybe that has an affect.
[19:22]  * arraybolt3 checks my ISO date
[19:23] <arraybolt3> Yeah I have the same ISO.
[19:23] <arraybolt3> Interesting. I wonder if we're hitting a timing condition that my hardware is showing up?
[19:24] <bdmurray> Well I was able to recreate it yesterday but I don't recall if I used the nvidia hardware but I think I must have
[19:25] -queuebot:#ubuntu-release- New binary: mutter [arm64] (lunar-proposed/main) [44~beta-3ubuntu2] (desktop-core, desktop-extra)
[19:25]  * arraybolt3 checks something real quick
[19:26] <arraybolt3> Part of me is sure this laptop used to work with this in the past.
[19:27] <arraybolt3> OK that wasn't it. (checked for a newer version of DKMS in the archives)
[19:28] <arraybolt3> Meh, I say it's not worth chasing down right now. Did anyone test the reintroduced ZFS-on-root support?
[19:29] <arraybolt3> I was going to do that but elected to do LVM+encryption since it was more common and lessl ikely to cause problems.
[19:29] <arraybolt3> I can give it a spin real quick if no one else has.
[19:35] -queuebot:#ubuntu-release- New binary: mutter [armhf] (lunar-proposed/main) [44~beta-3ubuntu2] (desktop-core, desktop-extra)
[19:38] <arraybolt3> Nice, ZFS-on-root works.
[19:44] -queuebot:#ubuntu-release- New binary: mutter [amd64] (lunar-proposed/main) [44~beta-3ubuntu2] (desktop-core, desktop-extra)
[19:44] <bdmurray> arraybolt3: Oh, did you have no network at all when doing the install?
[19:44] <arraybolt3> bdmurray: True.
[19:45] <arraybolt3> The laptop had no Ethernet or WiFi available during installation.
[19:47] <arraybolt3> Should I try a test with Ethernet provided during installation? I have the needed hardware to do that.
[19:48] <luna_> 22.04.2 downloaded
[20:05] <bdmurray> I'm trying one without internet now
[20:18] <bdmurray> arraybolt3: it also worked for me w/o internet
[20:18] <arraybolt3> :shrug:
[20:18] <arraybolt3> Lemme zsync again just to make sure that I really have exactly your ISO.
[20:19] <arraybolt3> This fails every single time for me.
[20:20] <arraybolt3> zsync: used 4927586304 local, fetched 0      (yep same ISO)
[20:58] -queuebot:#ubuntu-release- New binary: mutter [riscv64] (lunar-proposed/main) [44~beta-3ubuntu2] (desktop-core, desktop-extra)
[21:25] -queuebot:#ubuntu-release- New binary: libcupsfilters [amd64] (lunar-proposed/universe) [2.0~b4-0ubuntu2] (no packageset)
[21:25] -queuebot:#ubuntu-release- New binary: libcupsfilters [s390x] (lunar-proposed/universe) [2.0~b4-0ubuntu2] (no packageset)
[21:25] -queuebot:#ubuntu-release- New binary: libcupsfilters [arm64] (lunar-proposed/universe) [2.0~b4-0ubuntu2] (no packageset)
[21:26] -queuebot:#ubuntu-release- New binary: libcupsfilters [ppc64el] (lunar-proposed/universe) [2.0~b4-0ubuntu2] (no packageset)
[21:31] <guiverc> I've not seen the 22.04.2 ML annoucement; sent?
[21:41] <bdmurray> Its in the moderation queue as I have an issue with part of it
[21:53] <guiverc> thanks bdmurray :)
[21:54]  * guiverc will post to fridge once found....
[21:58] -queuebot:#ubuntu-release- New binary: libcupsfilters [armhf] (lunar-proposed/universe) [2.0~b4-0ubuntu3] (no packageset)
[21:58] -queuebot:#ubuntu-release- New binary: libcupsfilters [s390x] (lunar-proposed/universe) [2.0~b4-0ubuntu3] (no packageset)
[21:58] -queuebot:#ubuntu-release- New binary: libcupsfilters [amd64] (lunar-proposed/universe) [2.0~b4-0ubuntu3] (no packageset)
[21:59] -queuebot:#ubuntu-release- New binary: libcupsfilters [ppc64el] (lunar-proposed/universe) [2.0~b4-0ubuntu3] (no packageset)
[22:02] -queuebot:#ubuntu-release- New binary: libcupsfilters [arm64] (lunar-proposed/universe) [2.0~b4-0ubuntu3] (no packageset)
[22:40] <ahasenack> who is going to do the FF announcement? How long until that happens?
[22:41] <ahasenack> I'm waiting for an update to a branch before I upload, but am pondering doing the update myself (oneliner) and uploading, isntead of waiting
[22:42] <arraybolt3> ahasenack: bdmurray has an issue with it and it's in the moderation queue last I heard.
[22:43] <arraybolt3> Oh, wait, FF announcement, not release announcement.
[22:43] <ahasenack> that's the jammy .2 email I think
[22:43] <arraybolt3> Sorry.
[22:43] <ahasenack> yeah
[22:43]  * arraybolt3 is tired and not thinking quite right
[22:45] <bdmurray> The FF announcement will happen in about 2 hours
[22:45] <bdmurray> ahasenack: ^
[22:46] <ahasenack> bdmurray: tnaks
[22:46] <ahasenack> thanks even
[23:34] -queuebot:#ubuntu-release- New binary: libcupsfilters [amd64] (lunar-proposed/universe) [2.0~b4-0ubuntu4] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: libcupsfilters [armhf] (lunar-proposed/universe) [2.0~b4-0ubuntu4] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: libcupsfilters [s390x] (lunar-proposed/universe) [2.0~b4-0ubuntu4] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: libcupsfilters [ppc64el] (lunar-proposed/universe) [2.0~b4-0ubuntu4] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: libcupsfilters [arm64] (lunar-proposed/universe) [2.0~b4-0ubuntu4] (no packageset)