[04:34] -queuebot:#ubuntu-release- Unapproved: paperwork (impish-proposed/universe) [2.0.2-3 => 2.0.3-2] (no packageset) (sync)
[04:35] -queuebot:#ubuntu-release- Unapproved: accepted paperwork [sync] (impish-proposed) [2.0.3-2]
[08:08] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Impish Final] has been marked as ready
[08:10] <sil2100> \o/
[08:28] <sil2100> xypron: hey! Could you be able to run the ubuntu-base test-case for riscv for impish?
[08:28] <sil2100> i.e. http://iso.qa.ubuntu.com/qatracker/milestones/428/builds/238195/testcases/1318/results
[08:31] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Impish Final] has been marked as ready
[08:57] <xypron> sil2100: yes.
[08:59] <sil2100> Thank you!
[09:10] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Impish Final] has been marked as ready
[09:13] <xypron> sil2100: test was successful on QEMU but failed on Unmatched board. Which package should be used for reporting the bug?
[09:14] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Impish Final] has been marked as ready
[09:17] <sil2100> xypron: ouch, can you submit a bug for ubuntu-cdimage for now? We'll figure out where to put it afterwards
[09:22] <LocutusOfBorg> !isitout
[09:22] <LocutusOfBorg> :)
[09:25] <xypron> sil2100: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1947136
[09:42] -queuebot:#ubuntu-release- Unapproved: open-vm-tools (hirsute-proposed/main) [2:11.3.0-2ubuntu0~ubuntu21.04.1 => 2:11.3.0-2ubuntu0~ubuntu21.04.2] (ubuntu-cloud, ubuntu-desktop, ubuntu-server)
[09:43] -queuebot:#ubuntu-release- Unapproved: open-vm-tools (focal-proposed/main) [2:11.3.0-2ubuntu0~ubuntu20.04.1 => 2:11.3.0-2ubuntu0~ubuntu20.04.2] (edubuntu, ubuntu-cloud, ubuntu-desktop, ubuntu-server)
[09:45] <sil2100> xypron: thanks o/
[09:45] <sil2100> paride: hey! How's server looking? You feel like it can be marked ready?
[09:53] <paride> sil2100, I'll try another couple of things and then proceed marking as ready
[09:58] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Impish Final] has been marked as ready
[09:58] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Impish Final] has been marked as ready
[09:58] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Impish Final] has been marked as ready
[09:58] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Impish Final] has been marked as ready
[10:26] <sil2100> paride: thanks!
[10:27] <sil2100> I see a few minor bits still waiting for testing, so I guess I'll start the actual release after lunch
[10:36] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Impish Final] has been marked as ready
[10:46] <sil2100> Ok, I'll go now AFK to fetch lunch, since we're anyway waiting for some pi testing to finish
[10:46] <sil2100> But I started off some of the releasey bits already
[10:48] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Impish Final] has been marked as ready
[11:08] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Impish Final] has been marked as ready
[11:15] -queuebot:#ubuntu-release- Unapproved: osinfo-db (impish-proposed/universe) [0.20210903-1 => 0.20211013-1] (no packageset) (sync)
[11:16] -queuebot:#ubuntu-release- Unapproved: accepted osinfo-db [sync] (impish-proposed) [0.20211013-1]
[11:21] -queuebot:#ubuntu-release- Unapproved: libreoffice (impish-proposed/main) [1:7.2.1-0ubuntu3 => 1:7.2.2-0ubuntu0.21.10.1] (ubuntu-desktop)
[12:34] <sil2100> Okay, disabling cdimage mirrors temporarily o/
[12:35] -queuebot:#ubuntu-release- Unapproved: calligra (impish-proposed/universe) [1:3.2.1+dfsg-2ubuntu8 => 1:3.2.1+dfsg-2ubuntu9] (kubuntu)
[12:39] -queuebot:#ubuntu-release- Unapproved: cdbs (impish-proposed/universe) [0.4.163ubuntu1 => 0.4.163ubuntu2] (i386-whitelist)
[12:40] -queuebot:#ubuntu-release- Unapproved: accepted cdbs [source] (impish-proposed) [0.4.163ubuntu2]
[12:43] <slyon> ugh. I missed that calligra is part of the kubuntu supported seed. This is a non-critical FTBFS fix. Can go into JJ (changelog contains 'devel' already, so it should fit both)
[13:04] <sil2100> ...slowly publishing the images, but mirrors should be still disabled
[13:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Impish Final] has been marked as ready
[13:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Impish Final] has been marked as ready
[13:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Impish Final] has been marked as ready
[13:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Impish Final] has been marked as ready
[13:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Impish Final] has been marked as ready
[13:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Impish Final] has been marked as ready
[13:12] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Impish Final] has been marked as ready
[13:12] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unleashed [Impish Final] has been marked as ready
[13:12] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Impish Final] has been marked as ready
[13:49] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Impish Final] has been marked as ready
[13:49] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Impish Final] has been marked as ready
[13:51] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.23 => 2.02-2ubuntu8.24] (core)
[14:02] <sil2100> Ok, looking good!
[14:06] <sil2100> jibel, didrocks: hey! You can go ahead with the WSL images in the nearest hours o/
[14:09] <falcojr> sil2100: cloud-init has an SRU for B, F, and H per https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1938299 . This is a hotfix for a critical issue on GCE. It entered proposed on the 8th. We have confirmation from our testing and from GCE that issue is fixed. Can we forego the rest of the aging and release it ASAP?
[14:10] <jibel> sil2100, great, thanks!
[14:10] <didrocks> sil2100: excellent, thanks!
[14:12] <sil2100> Ok, mirrors syncing, but it will all still take a while to migrate, we also need some mirror probing to do
[14:16] <bdmurray> falcojr: I'll have a look at that
[14:36] <falcojr> thanks!
[14:50] -queuebot:#ubuntu-release- Unapproved: checkinstall (impish-proposed/universe) [1.6.2+git20170426.d24a630-2ubuntu1 => 1.6.2+git20170426.d24a630-2ubuntu2] (no packageset)
[14:50] <Wimpy> Thanks sil2100 and bdmurray and the rest of the release team.
[14:51] -queuebot:#ubuntu-release- Unapproved: accepted checkinstall [source] (impish-proposed) [1.6.2+git20170426.d24a630-2ubuntu2]
[14:53] <madhens> Seriously, thanks to the release team, especially sil2100 and bdmurray, and everyone who helped with yet another release!
[14:54]  * ogra is surprised madhens is not in #ubuntu-release-party 🙂
[14:55] <sil2100> \o/ soon it will be time to party! Actually we could already party now, but I'd prefer us to first have a live webpage
[14:57] <sil2100> But for that I want more mirrors to pick up
[15:01] <sil2100> Anyway, big thank you to the whole community for all the awesome work on this release o/
[15:06] <slyon> thank you sil2100, bdmurray!
[15:32] -queuebot:#ubuntu-release- Unapproved: gsmlib (impish-proposed/universe) [1.10+20120414.gita5e5ae9a-0.3ubuntu1 => 1.10+20120414.gita5e5ae9a-0.5] (no packageset) (sync)
[15:33] -queuebot:#ubuntu-release- Unapproved: accepted gsmlib [sync] (impish-proposed) [1.10+20120414.gita5e5ae9a-0.5]
[16:16] <blackboxsw> Congrats all on the excellent work release team and heavy lifting with Impish! Many thanks for this success.
[16:22] <blackboxsw> bdmurray: I'm not certain if you were planning on ubuntu-advantage-tools SRU review into X, B F and H  or if we needed to ping "the vanguard" for today https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942929
[16:24] <blackboxsw> strike that comment. sorry ^
[16:33] -queuebot:#ubuntu-release- Unapproved: python-jmespath (bionic-proposed/main) [0.9.3-1ubuntu1 => 0.9.3-1ubuntu1.1] (ubuntu-server)
[16:33] -queuebot:#ubuntu-release- Unapproved: python-jmespath (focal-proposed/main) [0.9.4-2 => 0.9.4-2ubuntu1] (ubuntu-server)
[16:55] <sil2100> hmmm
[16:55] <sil2100> I wanted to update the topic, but I've been told I'm not the channel operator!
[16:55] <laney> op yourself!
[16:55] <sil2100> ...can I? Lemme try
[16:56] <sil2100> Ooo
[16:56] <sil2100> laney: thanks, didn't know/forgot that I can actually do that
[16:56] <sil2100> ;)
[16:56] <ogra> YAY !
[16:58] <ginggs> \o/
[16:58] <tumbleweed> :)
[17:02] <sil2100> bdmurray: do you have moderation powers over ubuntu-announce?
[17:02] <bdmurray> sil2100: yes, I do
[17:04] <bdmurray> accepted
[17:06] <sil2100> bdmurray: hmm, can you post the Launchpad announcement? do you have the powers?
[17:06] <sil2100> Per https://launchpad.net/ubuntu/+announce
[17:06] <bdmurray> sil2100: No, that's techboard only
[17:06] <fheimes> so thx a ton to everyone involved in this shiny new release! (y)  (https://lists.ubuntu.com/archives/ubuntu-announce/2021-October/thread.html)
[17:11] <sil2100> \o/ Huge thanks to bdmurray for all the heavy lifting during the release!
[17:11] <sil2100> And vorlon too!
[17:11] <ricotz> \o/
[17:14] <bdmurray> sil2100: thanks to you too!
[17:22] <oSoMoN> Thanks and kudos to the release team!
[17:34] <kc2bez> Thanks to the release team!
[18:20] <ddstreet> bdmurray please feel free to correct the page if i'm misrepresented you in this change: https://wiki.ubuntu.com/StableReleaseUpdates?action=diff&rev1=349&rev2=350
[18:52] <vorlon> blackboxsw: uat> it's unusual for log files to be initialized from maintainer scripts.  If this log file gets removed, do the tools recreate them with the right permissions?
[18:58] <blackboxsw> vorlon: yes https://github.com/canonical/ubuntu-advantage-client/blob/main/uaclient/cli.py#L1391 the setup_logging function there ensures the file is created with proper root read-only perms
[18:59] <blackboxsw> so ultimately it may not entirely be necessary to pre-create those files in postinst
[18:59] <blackboxsw> the issue at play was originally upgrade path where ubuntu-advantage.log was world readable (before it contained secrets/tokens) so that permission bit needed to be set to lock it down in postinst
[19:00] <vorlon> ah; so that shouldn't be a concern for the new log files?
[19:00] <ddstreet> blarg...distro-info again breaks anything and everything that is using it...will that get updated today?
[19:01] <ddstreet> release day "fun" for the stable release apps using distro-info ;-)
[19:03] <blackboxsw> vorlon: I think ultmately the chmod we are performing in postinst it probably is probably supplemental and may be unneeded given that setup_logging calls we have generate the log file with the right permissions. orndorffgrant or Lucas do you agree?
[19:04] <vorlon> ddstreet: this has never been identified as a release-day-critical task... what are the things that break, and shouldn't those be fixed to not fail when there is currently no devel series?  There's precedent for us going up to a week without a new release opened in Launchpad
[19:04] <vorlon> ddstreet: (without even having a name for it, which blocks both lp opening and distro-info sruing)
[19:04] <sarnold> heh I thought we'd go two weeks in the past.. granted I don't think anyone *liked* that delay ..
[19:07] <orndorffgrant> blackboxsw: Yes that does appear unneeded
[19:14] <blackboxsw> orndorffgrant: ok I created a bug card against ua-t to remove postinst handling of new logs and put in in selected for development. I think this is something we should easily be able to add for 27.4 if it ends up not being critical for this current SRU.
[19:15] <orndorffgrant> I agree
[19:35] <ddstreet> vorlon problem is on release day, *everything* that calls distro-info --devel (or via python, etc) will fail with "ubuntu-distro-info: Distribution data outdated."
[19:36] <ddstreet> i assume past arguments have been something like "there is no devel release on release day" but that doesn't change the fact that everything expecting distro-info --devel to actually return a non-error will fail
[19:41] <tumbleweed> personally, that's my reminder that Ubuntu has released and I should keep an eye out for the new name
[19:42] <tumbleweed> (but that's just noise from my .bashrc and some extra cron email)
[19:43] <ddstreet> tumbleweed unfortunately some things like tests actually rely on it not returning an error, e.g. https://launchpadlibrarian.net/563631361/buildlog_ubuntu-hirsute-amd64.ubuntu-dev-tools_0.185~0ubuntu21.04.1~test1_BUILDING.txt.gz
[19:43] <ddstreet> the real unfortunate thing about it is that contrary to the stated error message, the installed distro-info is NOT outdated, it is in fact the latest distro-info available.
[19:44] <tumbleweed> it has no way of knowing that, though
[19:45] <ddstreet> and unless everyone using distro-info changes their code to handle distro-info --devel failures (but only this specific failure, and at this specific time) everything using distro-info --devel just has to wait until it's finally working again
[19:45] <ddstreet> tumbleweed what, distro-info? yeah of course not, it's not the code's problem - the problem is that the package has a self-destruct date for distro-info --devel, and it never gets updated before that date
[19:46] <tumbleweed> there's no reason it couldn't be, if we could get a name
[19:46] <ddstreet> IMHO it should either 1) just return the 'newly stable' release as the 'devel' release until a new 'devel' release is crowned, or 2) get updated before the devel release becomes stable
[19:47] <ddstreet> yeah, exactly
[19:47] <ddstreet> it just never happens ;-)
[19:47] <tumbleweed> occasionally it used to
[19:47] <ddstreet> i don't think the 'devel' release should even *have* an end date, personally
[19:47] <tumbleweed> I think we'd need a new API that returns devel-or-latest
[19:47] <ddstreet> it ends when some other new devel release is created
[19:47] <ddstreet> i think that's overthinking it
[19:48] <ddstreet> what exactly is going to break if distro-info --devel returned 'impish' for the next few days
[19:48] <ddstreet> nothing
[19:49] <ddstreet> anyway ;-)
[20:23] <vorlon> ddstreet: I agree; my point is exactly that we should be fixing the code (whether in distro-info or in the callers), not considering it a fire drill to SRU distro-info everywhere on release day
[20:24] <ricotz> hello, congrats finishing the release :)
[20:26] <ricotz> there are two libreoffice SRUs for focal and impish, it would be great to have those accepted
[20:26] <ricotz> https://bugs.launchpad.net/ubuntu/focal/+source/libreoffice/+bug/1929999
[20:26] <ricotz> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1946558
[20:29] <jchittum> distro-info also has to get SRUd as soon as there's a name, right? so it makes sense in my head to handle those few days gracefully
[20:30] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-desktop-icons (focal-proposed/main) [20.04.0-3~ubuntu20.04.3 => 20.04.0-3~ubuntu20.04.4] (ubuntu-desktop)
[20:41] <mwhudson> vorlon, bdmurray: should doing this vhttps://github.com/tianon/docker-brew-ubuntu-core/pull/218 be on the release checklist?
[20:41] <mwhudson> although alex has done it within minutes of release for the last two so maybe we don't need to...
[20:41] <tumbleweed> jchittum: nope, only the data package
[20:42] <vorlon> mwhudson: I'm unclear on the semantics of "rolling" here, why is it the latest stable rather than a devel daily?
[20:43] <vorlon> mwhudson: also unclear on the effects of this change in this context
[20:44] <mwhudson> vorlon: it controls the tags the image gets published with
[20:44] <mwhudson> ubuntu:latest is lts, ubuntu:rolling is latest release, ubuntu:devel is, well, you can guess
[20:44] <mwhudson> not sure this is sensible terminology but well
[20:47] <vorlon> ok
[20:47] <vorlon> then yes, seems it should be part of the release tasks
[20:47] <vorlon> are the images themselves still produced downstream of CPC?
[20:50] <mwhudson> vorlon: i'm tempted to quibble with your assumptions a bit there but essentially no
[20:51] <vorlon> uh
[20:51] <mwhudson> the docker official images are single layer
[20:51] <mwhudson> and that layer is exactly the tarball we produce
[20:51] <mwhudson> the base layer of the official images has been the tarball we produce for a long time, what's changed is that there used to be layers on top
[20:52] <vorlon> my question is, who does the release team need to interact with to a) know this is ready to be done and b) get it done
[20:52] <mwhudson> ah we need to make sure the image at https://partner-images.canonical.com/oci/$release is final
[20:52] <mwhudson> which is produced by CPC
[20:53] <vorlon> ok
[20:55] <mwhudson> hmm, there is a plan to streamline how the images get from cpc to the docker hub, not sure what's going on there
[20:55] <mwhudson> that might obviate the need to do this
[21:21] -queuebot:#ubuntu-release- Unapproved: libsignon-glib (impish-proposed/universe) [2.1-3 => 2.1-3ubuntu0.21.10] (kubuntu)
[21:22] -queuebot:#ubuntu-release- Unapproved: libsignon-glib (hirsute-proposed/universe) [2.1-3 => 2.1-3ubuntu0.21.04] (kubuntu)
[21:27] <jchittum> mwhudson : CPC has it on their radars to do docker hub. toabctl has been handling things
[21:28] <jchittum> hm, looks like there's nothing in the oci bucket recently
[21:29] <vorlon> jchittum: so should the release process capture that there is a dockerhub step or do you consider this unneccessary?
[21:29] <vorlon> -c
[21:30] <jchittum> I would consider it unnecessary. It can be in the CPC bucket (which we should more clearly write up for everyone else)
[21:35] <vorlon> orndorffgrant: hi, another comment from me on LP: #1942929; unless I'm missing something, this is a blocker for SRU acceptance for me
[21:43] -queuebot:#ubuntu-release- Unapproved: sway (impish-proposed/universe) [1.5.1-2 => 1.5.1-2ubuntu1] (no packageset)
[21:44] -queuebot:#ubuntu-release- Unapproved: accepted sway [source] (impish-proposed) [1.5.1-2ubuntu1]
[22:04] -queuebot:#ubuntu-release- Unapproved: gdebi (impish-proposed/universe) [0.9.5.7+nmu5ubuntu1 => 0.9.5.7+nmu5ubuntu2] (ubuntu-mate)
[23:48] -queuebot:#ubuntu-release- Unapproved: apache2 (focal-proposed/main) [2.4.41-4ubuntu3.7 => 2.4.41-4ubuntu3.8] (i386-whitelist, ubuntu-server)