[09:09] <bdmurray> vorlon: the packages were added to the blacklist because they were not, at the time, getting autocleaned up and would run for 24+ hours. So they were added to free up testing resources. I plan to reevaluate and likely remove them at the start of KK.
[09:51] -queuebot:#ubuntu-release- Unapproved: node-marked (jammy-proposed/universe) [4.0.12+ds+~4.0.1-2ubuntu1 => 4.0.12+ds+~4.0.1-2ubuntu2] (lubuntu)
[09:54] <Wimpy> vorlon: The Ubuntu MATE images have been size reduced as much as possible. Where can I configure the new target size?
[09:56] <bdmurray> Wimpy: Here's an example https://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/revision/2021
[09:56] <Wimpy> bdmurray: Thanks. I'll take a look.
[10:04] <bdmurray> sil2100: Could you have a look at https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/417832 ?
[10:11] <sil2100> bdmurray: let me take a look in a moment
[10:22] -queuebot:#ubuntu-release- Unapproved: accepted node-marked [source] (jammy-proposed) [4.0.12+ds+~4.0.1-2ubuntu2]
[10:23] -queuebot:#ubuntu-release- Unapproved: accepted ifupdown [source] (jammy-proposed) [0.8.36+nmu1ubuntu3]
[10:23] <bdmurray> vorlon: see the apport focal test on armhf runing for 102h as an example
[10:30] <sil2100> bdmurray, vorlon: base-files in teh queue
[10:30] -queuebot:#ubuntu-release- Unapproved: base-files (jammy-proposed/main) [12ubuntu3 => 12ubuntu4] (core, i386-whitelist)
[10:37] <bdmurray> Is there still an issue logging in with wiki.ubuntu.com?
[12:51] -queuebot:#ubuntu-release- Unapproved: flash-kernel (jammy-proposed/main) [3.104ubuntu8 => 3.104ubuntu9] (core)
[13:03] -queuebot:#ubuntu-release- Unapproved: freeradius (focal-proposed/main) [3.0.20+dfsg-3build1 => 3.0.20+dfsg-3ubuntu0.1] (ubuntu-desktop, ubuntu-server)
[13:29] <xnox> release team have watched the videos of swimming jelly fish and we approve of the update shape
[13:52] -queuebot:#ubuntu-release- Unapproved: accepted flash-kernel [source] (jammy-proposed) [3.104ubuntu9]
[14:05] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (jammy-proposed) [12ubuntu4]
[14:19] <RikMills> \o/
[14:53] <xnox> ubuntu-release LP: #1968954 upload is 0-day sru of security fixes, aiming to migrate that kernel after the jammy release.
[14:53] <ubottu> Launchpad bug 1968954 in Kernel SRU Workflow "jammy/linux: 5.15.0-27.28 -proposed tracker" [Medium, In Progress] https://launchpad.net/bugs/1968954
[15:03] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-release-upgrader [source] (focal-proposed) [1:20.04.38]
[15:14] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (focal-proposed/main) [1:20.04.37 => 1:20.04.38] (core)
[15:21] <vorlon> bdmurray: blacklist> ok great, thanks
[15:22] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (focal-proposed) [1:20.04.38]
[16:37] <ahasenack> hi, how can I track binary package movements between main and universe? Something like the "publishing history" page, but for a binary package, not source
[16:37] <ahasenack> https://launchpad.net/ubuntu/impish/+package/squid-openssl being the package in question
[16:39] <ahasenack> https://launchpad.net/ubuntu/jammy/+package/squid-openssl is a better summary: 4.13 was in main, and the next one, 5.2, is in universe
[16:44] <vorlon> ahasenack: the undiscoverable https://launchpad.net/ubuntu/jammy/amd64/squid-openssl
[16:44] <ahasenack> thanks!
[18:34] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Jammy Final] (20220418) has been added
[18:35] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Jammy Final] (20220418) has been added
[18:40] <ahasenack> what is this "Extra seed" that shows up in this rdepends report? https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/squid/squid-openssl
[18:41] <vorlon> ahasenack: https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/extra
[18:41] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (jammy-proposed/main) [1:22.04.9 => 1:22.04.10] (core)
[18:42] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Jammy Final] (20220418) has been added
[18:44] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Jammy Final] (20220418.1) has been added
[18:44] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (jammy-proposed) [1:22.04.10]
[18:44] <sergiodj> vorlon: since we're talking about squid-openssl, it's not clear to me why it was demoted from main to universe.  do you happen to remember/know?
[18:44] <vorlon> ahasenack: I don't recall the details on how that's defined, but it's something that's synthesized by germinate rather than an explicit seed and we don't pull those things into main
[18:45] <ahasenack> vorlon: like a catch-all for universe?
[18:45] <sergiodj> maybe because there's no package depending on it & it's not in any seed?
[18:45] <vorlon> sergiodj: precisely that
[18:45] <ahasenack> sergiodj: I'm thinking that's it, and it was just a timing issue that it remained in main in impish
[18:45] <ahasenack> or a freeze
[18:45] <sergiodj> OK then, our guess was right then
[18:45] <vorlon> ahasenack: no; in this case, it's "extra" because it's a binary built from a source in main
[18:45] <sergiodj> ahasenack: yeah
[18:46] <vorlon> eh, who demoted probert-network?
[18:47] <vorlon> doko: probert-network must not be demoted.  This is a bug in the component-mismatches report.
[18:49] <sergiodj> cross-posting here: with that in mind, and knowing that upstream is still working on the patches to support openssl 3, I think a good plan ahead is to wait until upstream finishes working on the PR, backport its missing bits to squid on Jammy, and then work on getting squid-openssl into main
[18:51] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Jammy Final] (20220418.1) has been added
[18:56] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Jammy Final] (20220418.1) has been added
[18:58] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Jammy Final] (20220418.1) has been added
[19:01] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy Final] (20220418.1) has been added
[19:01] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Jammy Final] (20220418) has been added
[19:16] <Bashing-om> UWN: Pulling "WIP" - Log checked and no further edits are known - Time to push 20:00 UTC.
[19:26] <mwhudson> vorlon: it comes with glibc upstream now and that's what they called it, i don't know why
[19:52] <jbicha> I'm mystified how gnome-sound-recorder 42 managed to make it into jammy despite apparently being deleted from proposed LP: #1967629
[19:52] <ubottu> Launchpad bug 1967629 in gnome-sound-recorder (Ubuntu) "gnome-sound-recorder 42 is not wanted for jammy" [Undecided, Fix Released] https://launchpad.net/bugs/1967629
[19:53] <jbicha> I think I'll just let it stay there though
[19:59] -queuebot:#ubuntu-release- Unapproved: vim (jammy-proposed/main) [2:8.2.3995-1ubuntu1 => 2:8.2.3995-1ubuntu2] (core, i386-whitelist)
[20:02] -queuebot:#ubuntu-release- Unapproved: accepted vim [source] (jammy-proposed) [2:8.2.3995-1ubuntu2]
[20:04] <vorlon> mwhudson: ok; I guess this is consistent with what I see on focal when generating e.g. en_US.UTF-8, which glibc canonicalizes as en_US.utf8
[20:05] <vorlon> sergiodj: can we just make it 'squid' instead of 'squid-openssl' at that point?
[20:05] <vorlon> sergiodj: having two builds of squid against different TLS implementations is >_<
[20:05] <vorlon> (I've looked at the history and understand why the choice was made in this case, but eh)
[20:05] <sergiodj> vorlon: yes, part of the plan (which I didn't post here) is to contact the Debian maintainer and talk to him about having a squid-gnutls and squid (which will then be linked against openssl)
[20:06] <sergiodj> assuming that he still wants to keep the gnutls version around, of course
[20:06] <sergiodj> otherwise, I'm fine with just one binary linked against openssl
[20:07] <vorlon> jbicha: https://launchpad.net/ubuntu/+source/gnome-sound-recorder/+publishinghistory doesn't show that laney's removal took effect, I'm not sure why
[20:08] <vorlon> jbicha: looks like the actual removal failed somehow(?), and then laney closed the bug with the block-proposed tag, which let it migrate :/
[20:08] <jbicha> the removal shows in https://launchpad.net/ubuntu/jammy/amd64/gnome-sound-recorder
[20:09] <vorlon> cute
[20:09] <jbicha> like I said, it's ok to be there now. But strange enough for me to mention it
[20:09] <vorlon> whereas laney's removal command shows the source being removed, not just the binaries; but the launchpad history doesn't reflect this
[20:09] <vorlon> cjwatson, wgrant: ^^ this may be of interest?
[20:11] <jbicha> it takes a bit of time for a removal to fully take effect, right? maybe britney did the promotion because there was no longer a blocker bug?
[20:11] <vorlon> yes but that doesn't explain why the launchpad history doesn't reflect the removal from -proposed
[20:23] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Jammy Final] (20220418) has been added
[20:23] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Jammy Final] (20220418) has been added
[20:23] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Jammy Final] (20220418) has been added
[20:23] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Jammy Final] (20220418) has been added
[20:23] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Jammy Final] (20220418) has been added
[20:23] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Jammy Final] (20220418) has been added
[20:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Jammy Final] (20220418.1) has been added
[20:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Jammy Final] (20220418.1) has been added
[20:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Jammy Final] (20220418.1) has been added
[20:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Jammy Final] (20220418.1) has been added
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Jammy Final] (20220418.1) has been added
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Jammy Final] (20220418.1) has been added
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unleashed [Jammy Final] (20220418.1) has been added
[21:24] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Jammy Final] (20220418.1) has been added
[21:52] <mfo> hey o/ please remove the 2 klibc uploads from bionic's upload queue (the recent security update will require a different version number).  Thanks!
[22:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Jammy Final] has been updated (20220418.2)
[22:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Jammy Final] has been updated (20220418.2)
[22:49] -queuebot:#ubuntu-release- Unapproved: rejected klibc [source] (bionic-proposed) [2.0.4-9ubuntu2.18.04.1]
[22:50] -queuebot:#ubuntu-release- Unapproved: rejected klibc [source] (bionic-proposed) [2.0.4-9ubuntu2.18.04.1]
=== eitteabs is now known as sbeattie
[23:19] <vorlon> doko: fwiw digging into it, the probert-network binary package maybe isn't actually used (I saw it in a failed server image build log but it turns out it was the wrong image build), so can be demoted
[23:58] <vorlon> coreycb: when you opened a vmware-nsx task on LP: #1891238 and marked it 'triaged', was that an indication that you wanted this package also removed from the release?
[23:58] <ubottu> Launchpad bug 1891238 in vmware-nsx (Ubuntu) "[RM] neutron-fwaas" [High, Triaged] https://launchpad.net/bugs/1891238