[00:04] -queuebot:#ubuntu-release- New: accepted golang-github-crowdsecurity-go-cs-bouncer [amd64] (mantic-proposed) [0.0.2-2]
[00:21] <jbicha> my understanding was that once kinetic is EOL, upgrades from jammy go to lunar without going through kinetic
[00:22] <jbicha> this is important because we do push new major versions of software to LTS sometimes and we wouldn't be able to push those updates to obsolete interim releases
[01:20] <RAOF> It's surprisingly hard to find what the expected support behaviour is.
[01:22] <vorlon> RAOF: what jbicha said; once kinetic is EOL the upgrade path is jammy->lunar
[01:23] <vorlon> RAOF: won't the upgrade also have -updates disabled> uh good point
[01:24] <vorlon> RAOF: so yeah, probably not worth SRUing
[01:25] <RAOF> Ok. I have learned a thing, and am now less confused ?
[01:26] <vorlon> RAOF: I did see that debootstrap for focal and jammy are still in unapproved; without them I can't really verify that mk-sbuild doesn't regress
[01:26] <RAOF> Huh. I thought they'd already been accepted?
[01:27] <vorlon> only the previous versions that were verification-failed
[01:27] <RAOF> Ah, right. And the new versions add the Breaks. Let me just get those done.
[01:28] -queuebot:#ubuntu-release- Unapproved: accepted debootstrap [source] (focal-proposed) [1.0.118ubuntu1.10]
[01:29] -queuebot:#ubuntu-release- Unapproved: accepted debootstrap [source] (jammy-proposed) [1.0.126+nmu1ubuntu0.4]
[01:31] <RAOF> And the kinetic upload also exists, adding the Breaks, and can be rejected with the same reasoning as the lunar one, I believe?
[01:33] <RAOF> (A supported upgrade from Jammy will have ensured all packages are up to date, pulling in the necessary fix, and an upgrade from Jammy-without-updates won't see either package)
[01:37] <vorlon> RAOF: yeah kinetic and lunar are both in the same situation
[01:39] -queuebot:#ubuntu-release- Unapproved: rejected debootstrap [source] (kinetic-proposed) [1.0.127ubuntu1.3]
=== chris14_ is now known as chris14
[02:40] -queuebot:#ubuntu-release- New binary: crowdsec-custom-bouncer [amd64] (mantic-proposed/universe) [0.0.15-3] (no packageset)
[02:40] -queuebot:#ubuntu-release- New binary: crowdsec-firewall-bouncer [amd64] (mantic-proposed/universe) [0.0.25-3] (no packageset)
[02:41] -queuebot:#ubuntu-release- New binary: crowdsec-custom-bouncer [arm64] (mantic-proposed/universe) [0.0.15-3] (no packageset)
[02:41] -queuebot:#ubuntu-release- New binary: crowdsec-custom-bouncer [s390x] (mantic-proposed/universe) [0.0.15-3] (no packageset)
[02:41] -queuebot:#ubuntu-release- New binary: crowdsec-custom-bouncer [armhf] (mantic-proposed/universe) [0.0.15-3] (no packageset)
[02:41] -queuebot:#ubuntu-release- New binary: crowdsec-firewall-bouncer [ppc64el] (mantic-proposed/universe) [0.0.25-3] (no packageset)
[02:41] -queuebot:#ubuntu-release- New binary: crowdsec-custom-bouncer [ppc64el] (mantic-proposed/universe) [0.0.15-3] (no packageset)
[02:44] -queuebot:#ubuntu-release- New binary: crowdsec-firewall-bouncer [arm64] (mantic-proposed/universe) [0.0.25-3] (no packageset)
[02:45] -queuebot:#ubuntu-release- New: accepted crowdsec-custom-bouncer [armhf] (mantic-proposed) [0.0.15-3]
[02:45] -queuebot:#ubuntu-release- New: accepted crowdsec-custom-bouncer [s390x] (mantic-proposed) [0.0.15-3]
[02:45] -queuebot:#ubuntu-release- New: accepted crowdsec-custom-bouncer [ppc64el] (mantic-proposed) [0.0.15-3]
[02:45] -queuebot:#ubuntu-release- New: accepted crowdsec-firewall-bouncer [arm64] (mantic-proposed) [0.0.25-3]
[02:45] -queuebot:#ubuntu-release- New: accepted crowdsec-custom-bouncer [amd64] (mantic-proposed) [0.0.15-3]
[02:45] -queuebot:#ubuntu-release- New: accepted crowdsec-firewall-bouncer [amd64] (mantic-proposed) [0.0.25-3]
[02:45] -queuebot:#ubuntu-release- New: accepted crowdsec-custom-bouncer [arm64] (mantic-proposed) [0.0.15-3]
[02:45] -queuebot:#ubuntu-release- New: accepted crowdsec-firewall-bouncer [ppc64el] (mantic-proposed) [0.0.25-3]
[10:03] -queuebot:#ubuntu-release- Unapproved: flash-kernel (kinetic-proposed/main) [3.106ubuntu8.1 => 3.106ubuntu8.2] (core)
[11:03] -queuebot:#ubuntu-release- Packageset: Added backport-iwlwifi-dkms to kernel-dkms in jammy
[11:03] -queuebot:#ubuntu-release- Packageset: Added backport-iwlwifi-dkms to kernel-dkms in kinetic
[11:03] -queuebot:#ubuntu-release- Packageset: Added backport-iwlwifi-dkms to kernel-dkms in lunar
[11:03] -queuebot:#ubuntu-release- Packageset: Added backport-iwlwifi-dkms to kernel-dkms in mantic
[11:07] -queuebot:#ubuntu-release- Unapproved: backport-iwlwifi-dkms (jammy-proposed/universe) [9858-0ubuntu3.2 => 9858-0ubuntu3.3] (kernel-dkms)
[11:25] -queuebot:#ubuntu-release- Unapproved: dahdi-linux (jammy-proposed/universe) [1:2.11.1~dfsg-1ubuntu12~22.04.1 => 1:2.11.1~dfsg-1ubuntu12~22.04.2] (kernel-dkms)
[11:38] -queuebot:#ubuntu-release- Unapproved: accepted dahdi-linux [source] (jammy-proposed) [1:2.11.1~dfsg-1ubuntu12~22.04.2]
[11:40] -queuebot:#ubuntu-release- Unapproved: accepted backport-iwlwifi-dkms [source] (jammy-proposed) [9858-0ubuntu3.3]
[11:43] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (jammy-proposed) [20220329.git681281e4-0ubuntu3.14]
[11:51] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (kinetic-proposed) [20220923.gitf09bebf3-0ubuntu1.7]
[11:52] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (lunar-proposed) [20230323.gitbcdcfbcf-0ubuntu1.2]
[12:51] <fabiomirmar> Hello SRU Team, I have an important customer that is waiting for the release of LP#2019751 and LP#2020641. Can someone take a look at these bugs for me and make sure they are good to be released to -updates? They are both have verification-done tags and are close to being 7 days in -proposed, but just want to make sure all is good to get this released soon...
[12:51] -ubottu:#ubuntu-release- Launchpad bug 2019751 in gnome-shell (Ubuntu) "Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation" [High, In Progress] https://launchpad.net/bugs/2019751
[12:51] -ubottu:#ubuntu-release- Launchpad bug 2020641 in gdm3 (Ubuntu Jammy) "Installing or removing apps through snap-store launches another gdm session" [High, Fix Committed] https://launchpad.net/bugs/2020641
[12:56] -queuebot:#ubuntu-release- Unapproved: ddcci-driver-linux (jammy-proposed/universe) [0.4.1-3ubuntu1 => 0.4.1-3ubuntu2] (kernel-dkms)
[13:05] <rbasak> fabiomirmar: https://launchpad.net/bugs/1979096 needs verifying please. Otherwise the Jammy release will get blocked on the Lunar release by default.
[13:05] -ubottu:#ubuntu-release- Launchpad bug 1979096 in gnome-shell (Ubuntu) "gnome-shell search can't launch apps if dock auto-hide is enabled" [Medium, Triaged]
[13:06] <rbasak> fabiomirmar: same for https://launchpad.net/bugs/2020641
[13:06] -ubottu:#ubuntu-release- Launchpad bug 2020641 in gdm3 (Ubuntu Jammy) "Installing or removing apps through snap-store launches another gdm session" [High, Fix Committed]
[13:08] <fabiomirmar> rbasak: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641 was changed to won't fix in lunar
[13:08] -ubottu:#ubuntu-release- Launchpad bug 2020641 in gdm3 (Ubuntu Jammy) "Installing or removing apps through snap-store launches another gdm session" [High, Fix Committed]
[13:09] <fabiomirmar> rbasak, I'll verify 1979096 for lunar now
[13:09] <rbasak> fabiomirmar: it was, but not by an SRU team member. So somebody from the SRU team will have to review and ack it, and because it's already accepted on the assumption that it will be verified, it shows up in the report as not ready so you'll need to negotiate that individually with an SRU team member - they won't know to look otherwise.
[13:09] <rbasak> fabiomirmar: also blocking is https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/comments/15
[13:09] -ubottu:#ubuntu-release- Launchpad bug 2020641 in gdm3 (Ubuntu Jammy) "Installing or removing apps through snap-store launches another gdm session" [High, Fix Committed]
[13:09] <jbicha> fabiomirmar: I verified the fix for bug 1979096 on Lunar now
[13:10] -ubottu:#ubuntu-release- Bug 1979096 in gnome-shell (Ubuntu) "gnome-shell search can't launch apps if dock auto-hide is enabled" [Medium, Triaged] https://launchpad.net/bugs/1979096
[13:10] <rbasak> fabiomirmar: on the retrospective Won't Fix for Lunar, that...isn't a recipe for getting an SRU landed in a hurry, shall we say :-/
[13:11] <rbasak> Also that'll just keep the package hanging around in lunar-proposed :-/
[13:11] <fabiomirmar> jbicha, thank you!
[13:13] <jbicha> rbasak: could you remove the gdm3 update from -proposed? from the discussion it looks like the SRU is unverifiable there
[13:13] <jbicha> *from lunar-proposed
[13:13] <fabiomirmar> rbasak, so, for https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/comments/15, I discussed it with ghadi (who submitted the SRU), and the issue is https://pastebin.ubuntu.com/p/pm4N5xNs4G/ , so it's unrelated to his changes... basically it can't do the systemd filesystem check because it is already being accessed by initramfs... so not sure what to do there...
[13:13] -ubottu:#ubuntu-release- Launchpad bug 2020641 in gdm3 (Ubuntu Jammy) "Installing or removing apps through snap-store launches another gdm session" [High, Fix Committed]
[13:14] <rbasak> Sorry, I can't - that's an AA-only action. But also, whether or not it's acceptable to not require this fix in Lunar is a separate SRU team decision that requires review and I'm doing non-SRU work today.
[13:15] <rbasak> I was just trying to help things along but looks like this SRU has a deeper, more complex process issue that I don't have time for right now, sorry.
[13:18] <fabiomirmar> No problem, thanks for looking rbasak ... whoever from the sru team can take a look at it and ping me, it would be much appreciated...
[13:28] -queuebot:#ubuntu-release- Unapproved: dm-writeboost (jammy-proposed/universe) [2.2.13-1ubuntu2 => 2.2.13-1ubuntu3] (kernel-dkms)
[14:22] -queuebot:#ubuntu-release- Unapproved: evdi (jammy-proposed/universe) [1.12.0+dfsg-0ubuntu2~22.04.1 => 1.12.0+dfsg-0ubuntu2~22.04.2] (kernel-dkms)
[14:30] -queuebot:#ubuntu-release- Unapproved: mysql-8.0 (lunar-proposed/main) [8.0.33-0ubuntu0.23.04.2 => 8.0.33-0ubuntu0.23.04.3] (core, i386-whitelist, ubuntu-server)
[14:35] -queuebot:#ubuntu-release- Unapproved: iptables-netflow (jammy-proposed/universe) [2.6-2ubuntu1 => 2.6-2ubuntu2] (kernel-dkms)
[14:53] -queuebot:#ubuntu-release- Unapproved: libreoffice (lunar-proposed/main) [4:7.5.3-0ubuntu0.23.04.1 => 4:7.5.4-0ubuntu0.23.04.1] (ubuntu-desktop)
[15:21] <blackboxsw> sil2100 or other SRU vanguards. I think we may have primary and secondary out for today. would anyone be able to perform an SRU unapproved upload review for cloud-init?
[15:24] -queuebot:#ubuntu-release- Unapproved: appstream-glib (jammy-proposed/universe) [0.7.18-2 => 0.7.18-2ubuntu1] (i386-whitelist, ubuntu-budgie, xubuntu)
[15:34] <jbicha> ahasenack: hi, the appstream-glib SRU for jammy is a high priority for people who use Flatpak ^
[15:35] <ahasenack> jbicha: hi, sorry but I'm off today, national holiday
[15:36] <ahasenack> (and tomorrow)
[15:36] <jbicha> cool, enjoy your weekend :)
[15:36] <ahasenack> thx
[15:37] <jbicha> let's see if anyone else from the SRU team has some time to review
[18:34] -queuebot:#ubuntu-release- Unapproved: accepted appstream-glib [source] (jammy-proposed) [0.7.18-2ubuntu1]
[19:45] <vorlon> hmm why is https://ubuntu-archive-team.ubuntu.com/pending-sru.html so far out of date
[19:59] <jbicha> vorlon: yes, it seems to lag by several hours
[20:00] <vorlon> jbicha: it should never be more than 4 hours out of date.  Either the report generation is dying, or it's overrunning the timeout configured for the job
[20:01] <vorlon> (the job is triggered twice an hour, it's run with a 'timeout 3h' wrapper, so the fact that it's now 20 hours out of date means something's gone wrong)
[20:01] -queuebot:#ubuntu-release- Unapproved: appstream-glib (focal-proposed/main) [0.7.16-1ubuntu1 => 0.7.16-1ubuntu2] (i386-whitelist, ubuntu-desktop)
[20:04] <jbicha> bdmurray: I also prepared the appstream-glib fix for focal. Same patches as jammy
[20:38] <vorlon> ubuntu-+   32504  0.0  0.0   2608   596 ?        S    17:40   0:00  |           \_ /bin/sh -c LC_ALL=C http_proxy= https_proxy= no_proxy= timeout 3h ~/ubuntu-archive-tools/sru-report > ~/public_html/pending-sru.html.new
[20:38] <vorlon> yeah hitting the timeout in 2 minutes
[20:41] <vorlon> rerunning it manually without a timeout to see how long it takes; not sure I'll have time today to try to debug the slowness