[00:04] <sil2100> o/
[00:29] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Hirsute Final] has been updated (20210421)
[01:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Hirsute Final] has been updated (20210421)
[01:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Hirsute Final] has been updated (20210421)
[01:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Hirsute Final] has been updated (20210421)
[01:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Hirsute Final] has been updated (20210421)
[01:55] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Hirsute Final] has been updated (20210421.1)
[01:55] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Hirsute Final] has been updated (20210421.1)
[01:55] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unleashed [Hirsute Final] has been updated (20210421.1)
[01:55] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Hirsute Final] has been updated (20210421.1)
[06:03] -queuebot:#ubuntu-release- Unapproved: mosquitto (hirsute-proposed/universe) [2.0.10-3 => 2.0.10-4] (no packageset) (sync)
[06:04] -queuebot:#ubuntu-release- Unapproved: yaml-cpp (hirsute-proposed/main) [0.6.3-9ubuntu1 => 0.6.3-10] (ubuntu-desktop) (sync)
[06:04] -queuebot:#ubuntu-release- Unapproved: accepted mosquitto [sync] (hirsute-proposed) [2.0.10-4]
[06:38] -queuebot:#ubuntu-release- New sync: xf86-video-armsoc-endlessm (hirsute-proposed/primary) [1.4.1-0ubuntu4]
[07:17] <philroche> Morning all. I see chatter above about respins. Are they the respins to address the riscv64 issues? If so am I safe to kick off cloud image respins now?
[07:19] <philroche> sil2100: ^
[07:21] <sil2100> o/
[07:21] <sil2100> Hello!
[07:21] <sil2100> philroche: what's up? I think we have our final images now o/
[07:21] <philroche> > I see chatter above about respins. Are they the respins to address the riscv64 issues? If so am I safe to kick off cloud image respins now?
[07:22] <sil2100> Yes, I think it's all safe now from what I'm aware
[07:22] <philroche> Great. Kicking off now
[07:24] <sil2100> Thank you!
[07:25] -queuebot:#ubuntu-release- Unapproved: rejected libwacom [source] (focal-proposed) [1.3-2ubuntu3]
[07:28] <philroche> Cloud image base build with serial 20210422 now in progress. We do not have riscv64 Minimal images so that serial remains 20210420
[07:28] <sil2100> ACK o/
[07:32] <sil2100> Final block-all block put in place just now, images pre-published o/
[07:32] <sil2100> Building source isos in the background
[07:33] <ginggs> q2-feature-classifier was recently (11hrs ago) added to big_packages, but i'm not seeing --flavor m1.large in the retried autopkgtest logs. is there a delay before the new config is applied?
[07:54]  * sil2100 goes AFK for a bit
[07:54] <sil2100> ginggs: I deployed your changes in production on both 'workers' yesterday so I'd expect it to work
[07:55] <sil2100> AH
[07:55] <sil2100> eeek
[07:55] <sil2100> Ok, I think I know what I missed
[07:56] <sil2100> ginggs: ok, now it should be good, sorry about it
[07:56] <ginggs> sil2100: thanks!
[07:56] <sil2100> Now, back to AFK for a bit o/
[07:56] <ginggs> enjoy!
[08:08] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Hirsute Final] has been marked as ready
[08:33] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Hirsute Final] has been marked as ready
[08:34] <doko> what's the procedure for packages now in -proposed and not reaching the release pocket, but with destination hirsute-updates? re-upload with series -proposed?
[08:40] -queuebot:#ubuntu-release- Unapproved: libdrm (hirsute-proposed/main) [2.4.104-1build1 => 2.4.105-1ubuntu0.1] (core, i386-whitelist, xorg)
[08:44] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Hirsute Final] has been marked as ready
[08:44] <Laney> doko: when we initialise the next series we can leave things in -proposed if they should be handled by the sru team
[08:44] <Laney> (but they probably want to see bugs attached)
[08:45] <doko> ok, I'll ask the SRU team before re-uploading
[08:57] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Hirsute Final] has been marked as ready
[09:01] <GunnarHj> Hi sil2100! Please see https://bazaar.launchpad.net/~ubiquity-slideshow/ubiquity-slideshow-ubuntu/html/revision/896
[09:01] <GunnarHj> Last update was 2+ years ago!
[09:01] <GunnarHj> I think there should be a secion "Release minus 28 days" (DocumentationStringFreeze) on the ReleaseProcess page with an item to check that the translation templates in ubiquity and ubiquity-slideshow-ubuntu (maybe others too) are up to date.
[09:05] -queuebot:#ubuntu-release- New sync: openjdk-16 (focal-proposed/primary) [16.0.1+9-1~20.04]
[09:06] -queuebot:#ubuntu-release- New sync: openjdk-16 (groovy-proposed/primary) [16.0.1+9-1~20.10]
[09:12] -queuebot:#ubuntu-release- New: rejected openjdk-16 [sync] (focal-proposed) [16+36-3~20.04]
[09:12] -queuebot:#ubuntu-release- New: accepted openjdk-16 [sync] (groovy-proposed) [16+36-3~20.10]
[09:14] <doko> ugh, I meant to reject the groovy one: ^^^ removing it
[09:27] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Hirsute Final] has been marked as ready
[09:55] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Hirsute Final] has been marked as ready
[10:08] <sil2100> waveform: hey! Can you do a quick spin of the raspi desktop images just-in-case?
[10:11] <xnox> bdmurray:  i am not sure if that's the right formatting, but proposing riscv64 manual tests https://code.launchpad.net/~xnox/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/401604
[10:12] <RikMills> sil2100: we have nextcloud-desktop client segfaulting on startup. seems from a quick PPA build and some upstream issues that building without LTO fixes that
[10:13] <RikMills> how are we handling such things SRU'wise today?
[10:13] <RikMills> LP: #1923053
[10:13] <waveform> @sil2100 absolutely!
[10:13] <ubot3> Launchpad bug 1923053 in nextcloud-desktop (Ubuntu) "nextcloud crashed with SIGSEGV." [High, Confirmed] https://launchpad.net/bugs/1923053
[10:15] <doko> please unblock openjdk-8/8u292-b10-0ubuntu1, recent security release
[10:17] <ginggs> sil2100: whatever you did worked :) q2-feature-classifier passed now
[10:19] <Laney> RikMills: SRUing
[10:28] <xnox> sil2100:  ^^^^^
[10:33] -queuebot:#ubuntu-release- Unapproved: mosquitto (hirsute-proposed/universe) [2.0.10-4 => 2.0.10-4ubuntu1] (no packageset)
[10:33] <mdeslaur> What happened to xenial autopkgtests?
[10:40] <juliank> mdeslaur: what issue are you seeing?
[10:40] -queuebot:#ubuntu-release- Unapproved: rejected mosquitto [source] (hirsute-proposed) [2.0.10-4ubuntu1]
[10:44] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox-hwe [source] (hirsute-proposed) [6.1.20-dfsg-1ubuntu1.21.04.1]
[10:44] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox [sync] (hirsute-proposed) [6.1.20-dfsg-1]
[10:45] -queuebot:#ubuntu-release- Unapproved: rejected yaml-cpp [sync] (hirsute-proposed) [0.6.3-10]
[10:49] <Laney> cpaelzer: hey can you expand a bit on the 0-dayness for libvirt/qemu, why they should be 0 day and not regular srus?
[10:49] <Laney> just lacking the context and it's not clear to me from the bug, sorry probably my comprehension failing
[10:49] <cpaelzer> hiho Laney
[10:49] <Laney> heya
[10:50] <cpaelzer> yeah in this case it is hard to differentiate - let me try to make clear and you ask on whatever is left
[10:50] <cpaelzer> those SRUs and bugs go on for a while already, the reporters are two very awesome and active examples of our community
[10:50] <cpaelzer> furthermore the code is - by now - well tested in various environments and such
[10:51] <cpaelzer> I'm NOT insisting on this being a 0-day SRU - instead all I wanted to avoid (and sorry if that was misleading) was to "1. open II release 2. the usual initial archive frenzy breaking things, 3. then re-veryfying everything again 4. then SRU"
[10:52] <cpaelzer> so all I'm after is the delay, not so much if it is available at 21.04 release or later
[10:52] <cpaelzer> if it is "in" before the archive copy/opening and of II happens that is fine for me
[10:52] <doko> gaughen_: it's too early for the release party ;p
[10:52] <cpaelzer> and even that
[10:53] <cpaelzer> if you have reasonable reasons against that "all that it costs" is delay (for hte users) and extra work (for retetsts and rebases) for me - it isn't "breaking the case"
[10:53] <cpaelzer> Laney: does that make any sense to your release-focussed eyes?
[10:54] <cpaelzer> It also is a bit about the implications "even the new 21.04 doesn't support the latest EPYC-Milan chips" sounds not so nice - but with these fixes we do :-)
[10:54] <cpaelzer> but I didn't want to bring that to the SRU-template as this is probably too non-technical
[10:55] <cpaelzer> and the upstream changes came in late (in relation to the chip availability) - we were not stalling on this in any way :-)
[10:57] <mdeslaur> juliank: I don't see xenial listed in our PPA autopkgtests anymore: https://people.canonical.com/~platform/security-britney/current/
[10:57] <juliank> mdeslaur: oh that's a question for sil2100, I don't do security autopkgtest
[10:57] <mdeslaur> sil2100: ^?
[10:59] <sil2100> Oh?
[10:59] <sil2100> Oh
[11:00] <sil2100> I think distro-info-data is at fault here
[11:00] <sil2100> Let me hack that in
[11:00] <mdeslaur> oh cool, thanks sil2100
[11:00] <sil2100> (since `distro-info --supported` now does no longer include xenial...)
[11:01] <mdeslaur> yeah, makes sense
[11:02]  * mdeslaur cries at having to support xenial for a few years still
[11:03] <sil2100> Ok, next run should have xenial back!
[11:04] <mdeslaur> thanks sil2100! much appreciated!
[11:07] <sil2100> cpaelzer: hey! re: the qemu and libvirt SRUs - I'd like to take them in as regular SRUs but without the 7-day aging period - would that sound okay?
[11:07] <sil2100> mdeslaur: yw!
[11:17] <cpaelzer> sil2100: yeah that would work fine for me
[11:17] <cpaelzer> sil2100: are the version numbers ok then, or would you want the very same upload but with ubuntuX.Y versions ?
[11:23] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Hirsute Final] has been marked as ready
[11:35] <sil2100> cpaelzer: they're fine, this will be forward-copied to HH+1
[11:39] <cpaelzer> perfect sil2100, that is exactly what I wanted then
[11:39] <cpaelzer> least amount of trouble for you, but before the HH+1 opening hiccup
[11:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Hirsute Final] has been marked as ready
[11:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Hirsute Final] has been marked as ready
[11:49] <kanashiro> sil2100, a couple of days ago you accepted the golang-github-containerd-containerd-dev binary package from the Bionic and Focal NEW queue. I just checked and it did not land in -updates yet. Is there any action needed to make it land?
[12:16] <sil2100> kanashiro: hey! It didn't? What do you mean?
[12:19] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Hirsute Final] has been marked as ready
[12:20] <kanashiro> sil2100, I can't install it in a regular lxd container running Focal and Bionic
[12:29] -queuebot:#ubuntu-release- Unapproved: distro-info-data (bionic-proposed/main) [0.37ubuntu0.9 => 0.37ubuntu0.10] (core)
[12:29] -queuebot:#ubuntu-release- Unapproved: distro-info-data (groovy-proposed/main) [0.44ubuntu1.3 => 0.44ubuntu1.4] (core, i386-whitelist)
[12:29] -queuebot:#ubuntu-release- Unapproved: distro-info-data (focal-proposed/main) [0.43ubuntu1.4 => 0.43ubuntu1.5] (core, i386-whitelist)
[12:30] -queuebot:#ubuntu-release- Unapproved: distro-info-data (hirsute-proposed/main) [0.46 => 0.46ubuntu1] (core, i386-whitelist)
[12:30] <sil2100> kanashiro: interesting!
[12:32] <kanashiro> sil2100, indeed! I was wondering if an AA would need to perform any extra action
[12:34] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (hirsute-proposed) [0.46ubuntu1]
[12:34] -queuebot:#ubuntu-release- Unapproved: accepted nautilus [source] (hirsute-proposed) [1:3.38.2-1ubuntu2]
[12:37] <sil2100> kanashiro: I'll look into that in a moment after I'm done with release-related tasks, but one thing I'm suspecting is that the binaries didn't get copied from -proposed to -updates as the -proposed binaries maybe were not approved before the copy was made?
[12:37] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-input-libinput [source] (hirsute-proposed) [0.30.0-1ubuntu1]
[12:37] <sil2100> I mean, I think there might have been an ordering issue, with the NEW binaries approved too late
[12:37] <sil2100> Or something
[12:37] <sil2100> I'll figure it out
[12:39] <kanashiro> sil2100, ah okay, I think you are right. The SRU was accepted before I asked you to check out the NEW queue
[12:39] <kanashiro> sil2100, anyway, thanks!
[12:50] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (groovy-proposed) [0.44ubuntu1.4]
[12:55] <sil2100> Laney: eeek, actually there's a 'typo' in the changelogs!
[12:55] <sil2100> Let me fix those, too bad I only now noticed
[12:55] <sil2100> No biggie
[12:56]  * ogra waits for "respining all images for fixed comma in changelog" 😄
[13:00] <rbalint> sil2100, could you please accept google-guest-agent for Hirsute to let CPC start the normal SRU verification?
[13:01] -queuebot:#ubuntu-release- Unapproved: distro-info-data (focal-proposed/main) [0.43ubuntu1.4 => 0.43ubuntu1.5] (core, i386-whitelist)
[13:02] <sil2100> Will do in a moment o/
[13:03] -queuebot:#ubuntu-release- Unapproved: distro-info-data (hirsute-proposed/main) [0.46ubuntu1 => 0.46ubuntu2] (core, i386-whitelist)
[13:04] -queuebot:#ubuntu-release- Unapproved: distro-info-data (bionic-proposed/main) [0.37ubuntu0.9 => 0.37ubuntu0.10] (core)
[13:05] -queuebot:#ubuntu-release- Unapproved: rejected distro-info-data [source] (bionic-proposed) [0.37ubuntu0.10]
[13:05] -queuebot:#ubuntu-release- Unapproved: rejected distro-info-data [source] (focal-proposed) [0.43ubuntu1.5]
[13:10] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (bionic-proposed) [0.37ubuntu0.10]
[13:11] -queuebot:#ubuntu-release- Unapproved: distro-info-data (groovy-proposed/main) [0.44ubuntu1.3 => 0.44ubuntu1.5] (core, i386-whitelist)
[13:19] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (hirsute-proposed) [0.46ubuntu2]
[13:19] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (groovy-proposed) [0.44ubuntu1.5]
[13:22] -queuebot:#ubuntu-release- Unapproved: accepted netplan.io [source] (hirsute-proposed) [0.102-0ubuntu3]
[13:27] <ddstreet> Laney since distro-info --devel is broken starting today until that upload is released ^, is it going to get fast-tracked to sru -updates for all releases?
[13:31] <sil2100> Yes
[13:31] <sil2100> We always fast-track it, no aging, just verification and release
[13:32] <ddstreet> sil2100 cool...maybe would be good to release it the day before distro-info breaks next time :)
[13:33] <sil2100> We'd need a name for that to happen ;)
[13:34] <sil2100> We're still lucky we got it as early as today!
[13:35] <ddstreet> ouch, well maybe a redesign of distro-info should happen so it doesn't break each release day(s)
[13:36] <ddstreet> no update for distro-info in x?
[13:38] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (hirsute-proposed) [21.1-19-gbad84ad4-0ubuntu3]
[13:40] <sil2100> It's not accepted yet, but in the queue o/
[13:41] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (xenial-proposed) [0.28ubuntu0.17]
[13:41] <ddstreet> sil2100 should i verify the bug so you can release? the distro-info breakage is actually stopping some of my work because my tooling uses it
[13:42] <sil2100> plars, waveform: hey! You think we can mark rpi desktop as green?
[13:42] <ddstreet> not sure if someone else was currently verifying distro-info bug
[13:42] <sil2100> ddstreet: sure, verification will always help!
[13:43] <plars> sil2100: I've mostly been focused on server, I know that bdmurray did some testing on it. I can spin it up on my 400 real quick if you want
[13:43] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Hirsute Final] has been marked as ready
[13:44] <sil2100> plars: I don't want to distract you from server, that's fine - I see it's green on the isotracker so I guess I can mark it 'ready'
[13:44] <sil2100> Just will wait for a final just-in-case confirmation from waveform :)
[13:45] <juliank> sil2100: Please carefully check that software-properties is not broken by new distro-info-data; python-apt now gets fed releases from there and stuff might be broken
[13:46] <juliank> hirsute we need to be a bit more cautious as it's the first time python-apt uses distro-info-data
[13:47] -queuebot:#ubuntu-release- Unapproved: heat-dashboard (hirsute-proposed/main) [5.0.0-0ubuntu1 => 5.0.0-0ubuntu2] (openstack)
[13:48] <juliank> Not that hirsute users will start to get impish sources.list updates when they add -proposed or disable -updates and reenable it
[13:49] <sil2100> juliank: but that's for hirsute, right?
[13:50] <juliank> sil2100: right
[13:50] <juliank> sil2100: I'm adding a bug comment
[13:50] <xnox> ddstreet:  it's normal that distro-info does nto work on release days.
[13:50] <xnox> ddstreet:  even if we have dates ahead of time, i think it's not that good on release days either.
[13:51] <xnox> cause next release is not open yet, and lots of things from next release are not there. Nor are stable things in stable.
[13:51] <ddstreet> that's not very good
[13:52] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Hirsute Final] has been marked as ready
[13:53] <juliank> ooh nice, dpkg 1.20.9 made it into release pocket
[13:53] <juliank> This is *good*
[13:53] <juliank> apt 2.3.0 in impish requires dpkg >= 1.20.8
[13:53] <juliank> well, 2.3.2 it will be
[13:56] <bittin> is impish 21.10 ?
[14:06] -queuebot:#ubuntu-release- Unapproved: accepted google-guest-agent [source] (hirsute-proposed) [20210414.00-0ubuntu1]
[14:07] <bdmurray> bittin: https://launchpadlibrarian.net/534867266/distro-info-data_0.46_0.46ubuntu1.diff.gz
[14:08] <bittin> ubottu: bdmurray: ah cool thanks
[14:14] <ddstreet> sil2100 lp:#1925484 verified for x/b/f/g feel free to release plz
[14:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Hirsute Final] has been marked as ready
[14:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Hirsute Final] has been marked as ready
[14:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Hirsute Final] has been marked as ready
[14:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Hirsute Final] has been marked as ready
[14:15] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Hirsute Final] has been marked as ready
[14:15] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unleashed [Hirsute Final] has been marked as ready
[14:15] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Hirsute Final] has been marked as ready
[14:18] <juliank> ddstreet, sil2100 verified hirsute too
[14:18] <juliank> including software-properties-gtk toggling
[14:23] <sil2100> \o/
[14:23] <slyon> Congrats! o/
[14:23] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Hirsute Final] has been marked as ready
[14:24] <sil2100> Not yet released tho!
[14:24] <sil2100> (almost there)
[14:25] -queuebot:#ubuntu-release- Unapproved: nextcloud-desktop (hirsute-proposed/universe) [3.1.1-1ubuntu1 => 3.1.1-1ubuntu1.1] (no packageset)
[14:29] <juliank> sil2100: well at least the releae announcement on ubuntu.com is out :D
[14:33] <RikMills> I also saw that tweeted by Planet Ubuntu
[14:34] <Eickmeyer> Lots of line jumping on release day.
[14:39] <Laney> itchy fingers
[14:52] <ogra> tappy feet
[14:53] <tumbleweed> Laney: thanks for doing the distro-infos
[14:54] <Laney> np
[14:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Hirsute Final] has been marked as ready
[14:54] <Laney> tumbleweed: I was going to ping you to fwd it
[14:55] <Laney> probably too lazy to do a MR :P
[14:55] <tumbleweed> Laney: already done :)
[14:57] <Laney> nice
[15:01] -queuebot:#ubuntu-release- Unapproved: openjdk-13 (groovy-proposed/universe) [13.0.4+8-1 => 13.0.7+5-0ubuntu1~20.10] (i386-whitelist) (sync)
[15:01] -queuebot:#ubuntu-release- Unapproved: openjdk-13 (focal-proposed/universe) [13.0.4+8-1~20.04 => 13.0.7+5-0ubuntu1~20.04] (i386-whitelist) (sync)
[15:02] -queuebot:#ubuntu-release- Unapproved: openjdk-15 (groovy-proposed/universe) [15+36-1 => 15.0.3+3-1~20.10] (i386-whitelist) (sync)
[15:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Hirsute Final] has been marked as ready
[15:11] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Hirsute Final] has been marked as ready
[15:25] <rbalint> ubuntu-archive could you please promote libzstd in xenial to main? it blocks dpkg
[15:40] <philroche> sil2100: CPC is ready for launch :)
[15:41] <doko> rbalint: did you talk with the security team? sarnold, sbeattie?
[15:44] <rbalint> doko, no, let me extend the MIR bug
[15:48] <rbalint> doko, also contacted the security team internally, too LP: #1755310
[15:48] <ubot3> Launchpad bug 1755310 in libzstd (Ubuntu Xenial) "MIR libzstd" [Undecided, New] https://launchpad.net/bugs/1755310
[15:51] <doko> rbalint: just want to make them aware of that
[15:54] <sil2100> philroche: \o/
[15:54] <sil2100> philroche: I think you can go live now! Since we are just validating the published images
[15:55] <philroche> sil2100: ack. CPC will now begin promotion to release of 20210420 serial for Minimal images and 20210422 serial for Base images
[15:57] <sbeattie> rbalint: sorry, what is the context here?
[15:59] <rbalint> sbeattie, https://bugs.launchpad.net/ubuntu/+source/libzstd/+bug/1755310/comments/3
[15:59] <ubot3> Launchpad bug 1755310 in libzstd (Ubuntu Xenial) "MIR libzstd" [Undecided, New]
[16:07] <sbeattie> rbalint: that doesn't give me any context as to why this is needed, except that dpkg for some reason has grown a dependency on it.
[16:07] <bittin> https://www.mynaparrot.com/en/join?meeting=65EA1A66-8D9B-458A-A9F8-A1BB2271D581 password: hirsute for people that wants to video chat
[16:10] <rbalint> sbeattie, ok so the why is that to enable launchpad to publish zstd compressed packages xenial's dpkg needs decompression support because launchpad runs xenial
[16:12] <rbalint> sbeattie, also xenial esm users may also maintain package archives where dpkg's zstd decompression may be needed
[16:17] <philroche> For our Chinese friends - for the first time ever....aws-cn was the first AWS partition to receive Hirsute release AMIs
[16:21] <cjwatson> ESM seems like a pretty niche use case, but having Launchpad use a supported version of dpkg is reasonably important
[16:21] <cjwatson> (niche because most of the OS doesn't use zstd compression there.  yes, of course one theoretically could)
[16:23] <cjwatson> sbeattie: https://docs.google.com/document/d/1v9y6OGm5HsxPdGgb9ZrFMz5tEN21fMpdwuL9yIp8bjY
[16:23] <cjwatson> (seems to be Canonical-internal, sorry, not my doc)
[16:33]  * sbeattie knows how it is
[16:33] <sbeattie> reading now
[16:45] <bittin> https://www.twitch.tv/communiteatime
[16:48] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (xenial-proposed) [3.9.1-1ubuntu0.16.04.2]
[17:00] <ogra> bittin, please keep it in #ubuntu-release-party ... people do actual work in here
[17:01] <sbeattie> rbalint, doko: okay, acked moving libzstd into main for xenial: https://bugs.launchpad.net/ubuntu/+source/libzstd/+bug/1755310/comments/4
[17:01] <ubot3> Launchpad bug 1755310 in libzstd (Ubuntu Xenial) "MIR libzstd" [Undecided, New]
[17:06] <bittin> ogra: alright
[17:06] <ogra> 👋/
[17:06] <ogra> yay
[17:14] <Laney> smooooooooooooth
[17:14] <xnox> sil2100:  did you not add emoji in the end? or did it not come through? (cause email headers have to be 7bit clean normally)
[17:14] <xnox> the one in the x-ubuntu header
[17:18] <Laney> the most elite emoji is an invisible one
[17:18] <cjwatson> 7-bit clean> that's what RFC2047 is for
[17:18] <bittin> thanks for the release, cya next time :)
[17:18] <bittin> and keep up the good work
[17:19] <cjwatson> good choice of X-Ubuntu, I thought
[17:19] <xnox> cjwatson:  oooh nice.
[17:19] <xnox> (the rfc, did not know that it exists)
[17:21] <xnox> cjwatson:  it started with "you will be missed" but then it was deemed not good enough.
[17:21] <xnox> cjwatson:  and it was mean to be "... missed  🦄"
[17:21] <xnox> for me that didn't come through
[17:28]  * ogra raises his beer 
[17:29] <ogra> to infinity !
[17:30] <mdeslaur> sil2100: I still don't see xenial showing up...how long is it supposed to take?
[17:30] <mdeslaur> sil2100: (oh, no rush)
[17:49] <juliank> The torrent does not work
[17:49] <juliank> 04/22 19:48:40 [ERROR] GID#708191bcb787e6da - Tracker request https://torrent.ubuntu.com/announce?info_hash=d%A9%80%AB%E6%E4H%22k%B90%BA%06%15%92%E4L7%81%A1&peer_id=A2-1-35-0-%B0iA%D1%2C%3A%FB4%0F%DC&uploaded=0&downloaded=0&left=2809825280&compact=1&key=A%D1%2C%3A%FB4%0F%DC&numwant=50&no_peer_id=1&port=6915&event=started&supportcrypto=1 failed
[17:49] <juliank> Exception: [DefaultBtAnnounce.cc:303] errorCode=1 Tracker returned failure reason: Requested download is not authorized for use with this tracker.
[17:49] <juliank> Does something need to be setup on the tracker still?
[17:54] <dbristow> My torrents are seeding fine.
[17:54] <dbristow> I got mine from cdimage.ubuntu.com
[17:54] <juliank> dbristow: there's only server on cdimage
[17:55] <juliank> talking about the official download for amd64 dekstop: https://releases.ubuntu.com/hirsute/ubuntu-21.04-desktop-amd64.iso.torrent
[17:55] <dbristow> juliank: ftp://cdimage.ubuntu.com/releases/21.04
[17:55] <juliank> I am seeding at 600 kB/s found images via dht
[17:56] <dbristow> juliank: My torrents were in that directory
[17:56] <juliank> good for you
[17:56] <dbristow> "Seeding to 15 of 51 connections"
[17:57] <dbristow> connected peers, that is
[17:58] <juliank> I have 14 of 41 peers
[17:58] <ogra> dbristow, yre you sure you dont seed arm64 ?
[17:58] <juliank> but that's all irrelevant
[17:58] <ogra> that dir doesnt have amd64 usually
[17:58] <juliank> ogra: So, via ftp releases.ubuntu.com offers other stuff than via http
[17:58] <dbristow> ogra: Trust me, the amd64 is there
[17:58] <juliank> dbristow: it's 2020, don't use ftp
[17:58] <dbristow> I'm not talking /cdimage/releases
[17:59] <dbristow> juliank: I prefer ftp when it's available, you can see symlinks.
[17:59] <juliank> Why do we offer ftp, this is confusing to users
[17:59] <ogra> yeah
[17:59] <ogra> and the browsers drop support for it
[17:59] <ogra> (i actually though firefox did already)
[17:59] <juliank> ogra: rsync and ftp /releases/21.04 is different from http
[17:59] <juliank> ogra: http has /releases/21.04/release
[18:00] <ogra> yes, i know
[18:00] <juliank> ogra: and ftp only offers amd64 desktop + server
[18:00] <juliank> ogra: So this is super confusing :D
[18:00] <ogra> yeah
[18:00] <ogra> not sure if ftp is still used for mirroring though...
[18:00] <juliank> cdimage.ubuntu.com::releases/ <=> http://releases.ubuntu.com/
[18:00] <juliank> cdimage.ubuntu.com::cdimage/ <=> http://cdimage.ubuntu.com/
[18:01] <juliank> ?
[18:01] <juliank> yup
[18:02] <mgedmin> https://ubuntu.com/download/alternative-downloads says the torrent is at https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso.torrent
[18:02] <juliank> yes
[18:03] <juliank> we know where the torrent is
[18:03] <mgedmin> but I get the same "Requested download is not authorized for use with this tracker" error
[18:04] <dbristow> Someone needs to kick the torrent server
[18:06] <juliank> dbristow: Working on finding the responsible people :D
[18:16] <falcojr> sil2100: cloud-init has an SRU for X, B, F and G per https://bugs.launchpad.net/cloud-init/+bug/1922739 and https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1899299 . If there is time today to review that SRU, testing is complete
[18:16] <ubot3> Launchpad bug 1922739 in cloud-init (Ubuntu Hirsute) "AttributeError: 'DataSourceNoCloud' object has no attribute 'vendordata2_raw'" [Undecided, Confirmed]
[18:16] <ubot3> Launchpad bug 1899299 in cloud-init (Ubuntu Hirsute) "do-release-upgrade from Trusty to Xenial breaks cloud-init init-local  on reboot" [Undecided, Fix Committed]
[18:17] <bdmurray> falcojr: Has it been 7+ days in -proposed?
[18:18] <falcojr> bdmurray: whoops...no it hasn't
[18:28] <bdmurray> falcojr: Is it important enough to release early?
[18:35] <bdmurray> coreycb: if you want to quickly verify bug 1925501 I'd be happy to release it
[18:35] <ubot3> Bug 1925501 in Ubuntu Cloud Archive wallaby "[SRU] heat-dashboard-common fails to install on hirsute (wallaby)" [High, Triaged] https://launchpad.net/bugs/1925501
[18:36] <coreycb> bdmurray: oh sure that'd be great. I'll report back.
[18:36] -queuebot:#ubuntu-release- Unapproved: accepted heat-dashboard [source] (hirsute-proposed) [5.0.0-0ubuntu2]
[18:39] <falcojr> bdmurray: no, I don't believe so
[18:44] <mgedmin> how come https://releases.ubuntu.com/21.04/ shows that SHA256SUMS.gpg has an older timestamp than SHA256SUMS itself?
[18:44] <mgedmin> (this explains the BAD signature from "Ubuntu CD Image Automatic Signing Key (2012) <cdimage@ubuntu.com>" I get from gpgv, I suppose)
[18:55] <vorlon> Laney: ^^ this is the second time we've had a bad .gpg for a SHA256SUMS reported after release, you didn't do any manual manipulation of the SHA256SUMS file, did you?
[18:55] <vorlon> mgedmin: I've re-signed and it should be mirroring now
[18:56] -queuebot:#ubuntu-release- Unapproved: update-notifier (xenial-proposed/main) [3.168.13 => 3.168.14] (ubuntu-desktop, ubuntu-server)
[19:01] <mgedmin> verifies fine now!
[19:04] <vorlon> sil2100, Laney: when looking at SHA256SUMS to check if there were any other stale signatures, I noticed the beta milestone images have not yet been archived off.  https://discourse.ubuntu.com/t/hirsute-hippo-21-04-release-status-tracking/21700/2 says this task is "assigned and being worked on" but the legend here doesn't give any way to see who it's assigned to? :)
[19:05] <juliank> vorlon: it also has a checkmark on ":heavy_check_mark: Check torrents for proper functionality." and they don't work correctly - the tracker is rejecting them
[19:05] <juliank> what's going on? argh
[19:06] <bdmurray> juliank: If you have a better / more specific way to test them could you write it down in https://wiki.ubuntu.com/ReleaseProcess?
[19:07] <juliank> bdmurray: open them in a torrent client and check that they can download?
[19:07] <juliank> and don't produce error messages about tracker not working?
[19:08] <bdmurray> juliank: they were checked with transmission
[19:09] <juliank> bdmurray: that shows the error when clicking on properties->tracker
[19:09] <juliank> also tons of delay at start in trying to find pee5rs
[19:09] <kc2bez[m]> juliank: I am having the same issue here.
[19:10] <juliank> kc2bez[m]: yes, surely, the tracker has not been told about the torrents yet
[19:13] <juliank> bdmurray: I added details, but it also seems to miss a step to actually poke the torrent tracker
[19:13] <juliank> bdmurray: maybe it (is supposed to) works automatically, I don't know
[19:14] <bdmurray> juliank: okay, thanks
[19:15] <juliank> can someone commit to following up on that and getting it fixed? I went EOD hours ago really, and I don't know who's in charge of it
[19:16] <bdmurray> juliank: vorlon and I will sort it
[19:16] <juliank> bdmurray: ack, thanks!
[19:24] <cjwatson> My guess is that releases-sync on caranda is broken
[19:24] <cjwatson> Since https://torrent.ubuntu.com/simple/hirsute/desktop/ only lists beta
[19:25] <cjwatson> It should hopefully leave logs somewhere on caranda where IS can read the,m
[19:37] <sil2100> vorlon: it's on meee
[19:37] <sil2100> I'll finish it up soonish
[19:50] -queuebot:#ubuntu-release- Unapproved: libwacom (focal-proposed/main) [1.3-2ubuntu2 => 1.3-2ubuntu3] (desktop-core, i386-whitelist)
[20:15] <Laney> vorlon: No I didn't, if you'd like to add a step in there to verify the checksums though then it'll get done the next time
[20:16] <vorlon> Laney: well I'd like to figure out the bug that caused them to be stale
[20:17] <vorlon> -rw-rw-r-- 1 cdimage cdimage 198 Apr 22 15:22 SHA256SUMS
[20:17] <vorlon> -rw-rw-r-- 2 cdimage cdimage 833 Apr 22 14:44 SHA256SUMS.gpg
[20:18] <Laney> Sure, but checking them seems like a sensible thing to do anyway.
[20:20] <vorlon> what's particularly curious here is that the 14:44 timestamp is close to the timestamp for all the flavors, but the SHA256SUMS file for Ubuntu was much later
[20:20] <vorlon> so who was doing what at 15:22 :)
[20:22] <Laney> I mean I don't wanna blame sil2100 but that sure matches the timestamp on the old-releases archival
[20:22] <Laney> so I guess verifying would have worked ...
[20:22] <vorlon> okj
[20:27] <Laney> https://discourse.ubuntu.com/t/hirsute-hippo-21-04-release-status-tracking/21700 follow up actions
[20:27] <Laney> add any others, we'll have a retrospective next week
[20:54] <vorlon> torrents fixed now
[20:57] <juliank> yay
[20:58] <Laney> nice
[20:59] <juliank> I've seed 2.1 times :D
[20:59] <juliank> *ed
[20:59] <Laney> I had a ratio of like 5.4 before I deleted the iso
[21:00] <Laney> but only the nice DHT people I guess :p
[21:01] <juliank> yeah
[21:10] -queuebot:#ubuntu-release- Unapproved: accepted gwenview [source] (hirsute-proposed) [4:20.12.3-1ubuntu0.1]
[21:11] -queuebot:#ubuntu-release- Unapproved: tmux (focal-proposed/main) [3.0a-2ubuntu0.2 => 3.0a-2ubuntu0.3] (ubuntu-server)
[21:12] -queuebot:#ubuntu-release- Unapproved: rejected update-manager [source] (hirsute-proposed) [1:21.04.9]
[21:27] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (hirsute-proposed) [7.0.0-2ubuntu2]
[21:32] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (hirsute-proposed) [1:5.2+dfsg-9ubuntu3]
[21:36] -queuebot:#ubuntu-release- Unapproved: accepted gjs [source] (hirsute-proposed) [1.67.2-2ubuntu2]
[21:53] -queuebot:#ubuntu-release- Unapproved: accepted nextcloud-desktop [source] (hirsute-proposed) [3.1.1-1ubuntu1.1]
[22:10] -queuebot:#ubuntu-release- Unapproved: landscape-client (hirsute-proposed/main) [19.12-0ubuntu9 => 19.12-0ubuntu9.1] (ubuntu-server)
[22:18] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (hirsute-proposed) [19.12-0ubuntu9.1]
[22:30] -queuebot:#ubuntu-release- Unapproved: accepted tmux [source] (focal-proposed) [3.0a-2ubuntu0.3]
[22:56] <sergiodj> bdmurray: thanks for the amazingly quick review & acceptance of the tmux SRU :)