[00:12] -queuebot:#ubuntu-release- New binary: martchus-qtforkawesome [arm64] (lunar-proposed/universe) [0.1.0-1] (no packageset)
[00:12] -queuebot:#ubuntu-release- New binary: martchus-qtforkawesome [armhf] (lunar-proposed/universe) [0.1.0-1] (no packageset)
[00:14] -queuebot:#ubuntu-release- Unapproved: accepted grub2-unsigned [sync] (focal-proposed) [2.04-1ubuntu47.5]
[00:18] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (focal-proposed) [2.04-1ubuntu26.16]
[00:39] <blackboxsw> vorlon: manual verification done on https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1999159
[00:39] -ubottu:#ubuntu-release- Launchpad bug 1999159 in cloud-init (Ubuntu) "cloud-init restarts during package upgrade when it shouldn't, regenerating SSH host keys on Azure Focal" [High, In Progress]
[00:54] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (focal-proposed) [1.173.4]
[00:54] <vorlon> blackboxsw: do you want it released immediately?
[01:13] <blackboxsw> vorlon it's getting late. I'm guessing we wait until Monday on this. I had hoped to get this in before the weekend in case people are performing upgrades on the weekend for 22.4.2, but this symptom has been out there since Sept. so maybe it's a smaller potential pool of exposure than I thought.
[01:20] <blackboxsw> vorlon: given that cloud-images only have -security pocket configured for unattended upgrades, the exposure here are people that are scheduling upgrades during downtime before rolling out services. So, I'm actually thinkings we don't need to expedite today. but sooner rather than later would be helpful
[01:47] -queuebot:#ubuntu-release- New binary: martchus-qtforkawesome [riscv64] (lunar-proposed/universe) [0.1.0-1] (no packageset)
[07:31] <vorlon> blackboxsw: ok. I am not around on Monday to do the SRU release fyi
[07:54] <LocutusOfBorg> hello, something looks not working on britney side?
[07:54] <LocutusOfBorg> I: [2022-12-09T07:17:30+0000] -  finish: [gap,gap-float,gap-guava,gap-io,-libgap7/amd64,-libgap7/arm64]
[07:54] <LocutusOfBorg> but gap didn't migrate
[07:54] <LocutusOfBorg> vorlon, ^^
[07:55] <LocutusOfBorg> also, since you are on i386 foo list
[07:55] <LocutusOfBorg> missing build on i386: libgav1-1, libgav1-bin, libgav1-dev (from 0.18.0-1)
[07:55] <LocutusOfBorg> meh
[07:56] <vorlon> LocutusOfBorg: why do you expect it to have migrated? the output I see is:
[07:56] <vorlon>  finish: [gap,gap-float,gap-guava,gap-io,-libgap7/amd64,-libgap7/arm64]
[07:56] <vorlon> endloop: 5+0: a-0:a-0:a-0:i-1:p-0:r-3:s-1
[07:56] <vorlon>     now: 11+0: a-5:a-1:a-0:i-1:p-0:r-3:s-1
[07:56] <vorlon> that says it tried the hint and uninstallability increased
[07:56] <vorlon>     * amd64: python3-sage, python3-sagetex, sagemath, sagemath-jupyter, sagetex
[07:56] <vorlon>     * arm64: python3-sage
[07:56] <LocutusOfBorg> so, I still fail to parse that output
[07:56] <LocutusOfBorg> after only 20 years or so
[07:56] <LocutusOfBorg> nice
[07:58] <vorlon> looking at libgav1, clearly lunar doesn't think it's supposed to be built
[08:02] <vorlon> ok it's no longer needed, binaries removed (along with various others that are detected)
[08:12] <LocutusOfBorg> vorlon, I issued a sagemath rebuild, but I really don't think it is compatible with newer sphinx newer gap, newer gcc and so on
[08:12] <LocutusOfBorg> ∙ ∙ Updating sagemath would introduce bugs in testing: #1013399, #1020576, #1022254, #1022278
[08:12] <LocutusOfBorg> can't we just kick them out from release to proposed
[08:12] <LocutusOfBorg> ?
[14:03] <jchittum> blackboxsw & vorlon : I agree that automated upgrades of cloud-init will be low, but it's a very high profile user base, with a possibly wide blast, showing a possible security issue (it's _not_ a security issue, but it'll _look_ like one to a user, right? it'll look like a MITM).
[14:03] <jchittum> regarding the cloud-init bug from yesterday (wish i had threading)
[14:04] <bdrung> tjaalton, can you accept the tzdata update (LP: #1998321). it's seven days old
[14:04] -ubottu:#ubuntu-release- Launchpad bug 1998321 in tzdata (Ubuntu Kinetic) "tzdata 2022g release" [Undecided, Fix Committed] https://launchpad.net/bugs/1998321
[14:05] <jchittum> Considering we've had a few oopses on our Azure pushes lately, we should probably move more quickly, and make sure the various Azure support groups are aware of manual checks and timelines
[14:07] <rbasak> bdrung: we don't like releasing on Fridays!
[14:07] <rbasak> It sounds like cloud-init may on balance need an exception to that, but I'l leave it to vorlon. We'll want an AA around over the weekend in that case.
[14:10] <bdrung> rbasak, sadly this tzdata update contains short of notice changes
[14:16] <rbasak> Maybe it's OK if someone is going to hang around for cloud-init anyway :)
[14:21] -queuebot:#ubuntu-release- Unapproved: ca-certificates-java (jammy-proposed/main) [20190909 => 20190909ubuntu1] (core, i386-whitelist)
[14:22] <jchittum> once i see blackboxsw back online, we can have a chat on timing and what we think possible blast is. I might get someone from Azure Linux Systems Group on the horn too and get their opinion. My worry is if someone does do a Friday upgrade (heh) they'll end up in a weird situation till a Monday release. But if the LSG team is aware, and we think it's a low probability of manual upgrade, and we have workaround steps...
[14:22] <jchittum> then Monday is preferable.
[14:23] <jchittum> cloud-init work-around, in a manual scenario, is setting up a serial connection and checking cloud-init logs for verification
[14:29] <tjaalton> bdrung: no release on a friday I'm afraid
[14:31] <bdrung> then please on monday
[15:30] <seb128> sil2100, hey. checking the build log of the desktop iso today https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/lunar/ubuntu it's still mentioning canary-ship-live is that expected?
[15:53] -queuebot:#ubuntu-release- Unapproved: edk2 (focal-proposed/main) [0~20191122.bd85bf54-2ubuntu3.3 => 0~20191122.bd85bf54-2ubuntu3.4] (no packageset)
[15:53] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (kinetic-proposed/main) [2.791 => 2.791.1] (desktop-core, i386-whitelist)
[16:11] <bdmurray> bdrung: Is the ICU update as important as the main tzdata update?
[16:11] <bdrung> bdmurray, for PHP users, yes
[16:20] -queuebot:#ubuntu-release- Unapproved: grub2-unsigned (lunar-proposed/main) [2.06-2ubuntu15 => 2.06-2ubuntu16] (core, i386-whitelist)
[16:37] -queuebot:#ubuntu-release- Unapproved: grub2-unsigned (lunar-proposed/main) [2.06-2ubuntu16 => 2.06-2ubuntu16] (core, i386-whitelist)
[16:41] <juliank> sil2100, vorlon: ^ fresh lunar grub binaries to approve :)
[17:10] <bdmurray> vorlon: init-system-helpers is missing an i386 build because it depends on fakechroot which is missing and i386 build because it gained a new dep on gnu-which for which we don't have an i386 build
[17:24] <vorlon> jchittum, blackboxsw, rbasak: I was asking about immediate release yesterday precisely because I am EOY tomorrow and not committed to being around over the weekend, or next week
[17:26] <blackboxsw> +1 on this vorlon(same) Had  a chat with jchittum and we can document how it understand this race if affects a system and get it to MSFT folks in the event that they get any support tickets on this. We think it's unlikely to hit the majority of vms due to the fact that is a pkg upgrade issue which is typically only handled in upgrade windows.
[17:26] <blackboxsw> we'll look to Monday likely and chat with sil-2100 then
[23:20] -queuebot:#ubuntu-release- New binary: nebula [amd64] (lunar-proposed/universe) [1.6.1+dfsg-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: nebula [ppc64el] (lunar-proposed/universe) [1.6.1+dfsg-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: nebula [arm64] (lunar-proposed/universe) [1.6.1+dfsg-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: nebula [s390x] (lunar-proposed/universe) [1.6.1+dfsg-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: nebula [armhf] (lunar-proposed/universe) [1.6.1+dfsg-1] (no packageset)