[01:01] -queuebot:#ubuntu-release- Unapproved: telegraf (impish-proposed/universe) [1.17.2+ds1-0ubuntu3 => 1.18.1+ds1-0ubuntu1] (no packageset) [01:11] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (hirsute-proposed/main) [26.2 => 27.0~21.04.1] (core) [01:43] -queuebot:#ubuntu-release- Unapproved: bridge-utils (hirsute-proposed/main) [1.6-5ubuntu1 => 1.7-1ubuntu1] (no packageset) [01:51] -queuebot:#ubuntu-release- Unapproved: mailcap (impish-proposed/main) [3.68ubuntu1 => 3.69ubuntu1] (core, i386-whitelist) [01:51] -queuebot:#ubuntu-release- Unapproved: rejected bridge-utils [source] (hirsute-proposed) [1.7-1ubuntu1] [01:53] -queuebot:#ubuntu-release- Unapproved: bridge-utils (impish-proposed/main) [1.6-5ubuntu1 => 1.7-1ubuntu1] (no packageset) [03:21] -queuebot:#ubuntu-release- Unapproved: sysvinit (impish-proposed/main) [2.96-6ubuntu1 => 2.96-7ubuntu1] (core, i386-whitelist) [03:23] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [20.3 => 27.0~20.04.1] (core) [03:24] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (xenial-proposed/main) [10ubuntu0.16.04.1 => 27.0~16.04.1] (no packageset) [03:41] -queuebot:#ubuntu-release- Unapproved: cadvisor (impish-proposed/universe) [0.38.7+ds1-1ubuntu1 => 0.38.7+ds1-2ubuntu1] (no packageset) [03:57] -queuebot:#ubuntu-release- Unapproved: wordpress (impish-proposed/universe) [5.6+dfsg1-2ubuntu1 => 5.7.1+dfsg1-2ubuntu1] (no packageset) [04:30] -queuebot:#ubuntu-release- New binary: gcc-11-cross-ports [amd64] (impish-proposed/universe) [3ubuntu1] (i386-whitelist) [05:19] -queuebot:#ubuntu-release- New: accepted gcc-11-cross-ports [amd64] (impish-proposed) [3ubuntu1] [05:30] -queuebot:#ubuntu-release- Unapproved: therion (impish-proposed/universe) [5.5.6ds1-5ubuntu1 => 5.5.7ds1-1ubuntu1] (no packageset) [05:34] distro-info-data migrated to impish release, si probably base-files should migrate as well. or just remove the migration block? [05:35] I was unclear why the migration block is still in place [05:36] IMHO it would be correct to remove it - we want to control packages being accepted into -proposed to ensure they're built with the right toolchain, but packages in -proposed are already built [05:40] -queuebot:#ubuntu-release- Unapproved: desktop-base (impish-proposed/universe) [10.0.3ubuntu1 => 11.0.3ubuntu1] (ubuntukylin, xubuntu) [05:42] vorlon: in any case, please manually accept base-files, if you want to delay the unblock decision [06:50] doko: done [06:50] -queuebot:#ubuntu-release- Unapproved: git-annex (impish-proposed/universe) [8.20201127-1ubuntu1 => 8.20210223-2ubuntu1] (no packageset) [06:54] -queuebot:#ubuntu-release- Unapproved: fai (impish-proposed/universe) [5.9.4ubuntu1 => 5.10.2ubuntu1] (no packageset) [06:58] bdmurray: sorry about that, updated the bug with SRU information [06:58] dbristow: my oversight [06:58] -queuebot:#ubuntu-release- Unapproved: libtpms (impish-proposed/universe) [0.8.0~dev1-1.2ubuntu1 => 0.8.2-1ubuntu1] (no packageset) [07:12] dbristow: sorry, polease ignore the previous mis-target [07:29] -queuebot:#ubuntu-release- Unapproved: magnum (groovy-proposed/universe) [11.0.0-0ubuntu1 => 11.0.0-0ubuntu1.1] (openstack) [08:00] do we have an ETA on the archive opening? if not possible to say, no problem [08:03] my plan was to get the current gcc-10 and gcc-11 uploads migrating, but I had to start the gcc-10 one twice on armhf ... base-files is now migrating, and Laney can tell you about other blocking stuff [08:07] no extra blockers from me [08:32] -queuebot:#ubuntu-release- Unapproved: llvm-toolchain-snapshot (impish-proposed/universe) [1:13~++20210129063721+010b176cdefb-1~exp1 => 1:13~++20210418105309+a0898f0cecc7-1~exp1] (no packageset) (sync) [08:33] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-snapshot [sync] (impish-proposed) [1:13~++20210418105309+a0898f0cecc7-1~exp1] [08:45] doko: we can unfreeze / remove the block / turn on auto sync when you are ready. I thought you mentioned wanting to migrate glibc first though, was that just gcc? [08:46] well I guess we should check the checklist through to see if everything was done [08:46] Laney: yes, just enable it, not that important, and I don't know when it will finish successfully [08:56] k, will do in a bit [08:56] I'm thinking about how https://ubuntu-release.kpi.ubuntu.com/d/76Oe_0-Gz/autopkgtest?viewPanel=12&orgId=1 is all uneven now [08:56] it's because we have multiple backend web servers now I think [08:57] generating the queue list on /running works by reading the whole queue and rejecting each item [08:57] so if multiple backends try to do that at the same time one of them doesn't see them all [08:57] wonder how to avoid that [09:05] could use a semaphore... /me tries that === cpaelzer__ is now known as cpaelzer [10:17] Laney: all failing amd64 autopkg tests triggered by debootstrap look like network/proxy issues [10:17] livecd-rootfs needs an impish image? [10:22] pbuilder, piuparts, sbuild were outdated distr-info-data [10:39] Laney, sil2100: I have the opening mail ready. please let me know when queues are open, and syncs enabled [10:41] -queuebot:#ubuntu-release- Unapproved: accepted bridge-utils [source] (impish-proposed) [1.7-1ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted desktop-base [source] (impish-proposed) [11.0.3ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted git-annex [source] (impish-proposed) [8.20210223-2ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted mailcap [source] (impish-proposed) [3.69ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted telegraf [source] (impish-proposed) [1.18.1+ds1-0ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (impish-proposed) [27.0] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted cadvisor [source] (impish-proposed) [0.38.7+ds1-2ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted libtpms [source] (impish-proposed) [0.8.2-1ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted therion [source] (impish-proposed) [5.5.7ds1-1ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted fai [source] (impish-proposed) [5.10.2ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted wordpress [source] (impish-proposed) [5.7.1+dfsg1-2ubuntu1] [10:41] -queuebot:#ubuntu-release- Unapproved: accepted sysvinit [source] (impish-proposed) [2.96-7ubuntu1] [10:42] -queuebot:#ubuntu-release- Unapproved: accepted csh [source] (impish-proposed) [20110502-6ubuntu1] [10:42] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (impish-proposed) [4.1-1ubuntu2] [10:42] -queuebot:#ubuntu-release- Unapproved: accepted murano-dashboard [source] (impish-proposed) [1:11.0.0-0ubuntu2] [10:42] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (impish-proposed) [3.192.41] [11:07] Laney: Shouldn't I be seeing the tests from https://bileto.ubuntu.com/excuses/4536/xenial.html - britney ran 40 minutes ago? [11:07] Don't see anything on the workers [11:07] sil2100: ^ [11:08] did they get requested? [11:09] I don't have insight into bileto [11:09] me neither [11:10] but you could maybe see the requests on the worker [11:10] doko: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/d/debuerreotype/20210428_110854_a788a@/log.gz [11:10] congratulations, you found a bug 💥 [11:11] https://git.launchpad.net/autopkgtest-cloud/commit/?id=443059cd35cb70a5cadca5907533681b5bfb83ac [11:11] Commit 443059c in autopkgtest-cloud "service-bundle: http_proxy needs -e prepended HEAD master" [11:11] Laney: At least "sudo rabbitmqctl list_queues | grep xenial" on rabiitmq server are all 0 [11:13] they could have run already though [11:14] no [11:14] i checked that first :D [11:14] alright [11:14] needs checking on the bileto side I guess [11:14] ideally someone would try a manual run of run-autopkgtest, submitting gzip or something [11:21] doko: can do opening things shortly after lunch [11:21] 90 minutes or so [11:22] I think my xenial apt autopkgtest fails locally in a VM because it has time zone CEST but apt only understands three letter zones :/ [11:22] Maybe autopkgtest-buildvm-ubuntu-cloud should set UTC timezone inside the VM [11:22] But not sure [13:00] -queuebot:#ubuntu-release- Unapproved: apt (xenial-proposed/main) [1.2.32ubuntu0.2 => 1.2.35] (core) [13:04] CPC is ready to build cloud images (including LXD and MaaS) once the archive is open, so please ping myself and philroche when the archive is open. Then we can kick off builds post-haste [13:20] -queuebot:#ubuntu-release- Unapproved: linux-firmware-raspi2 (groovy-proposed/restricted) [3-0ubuntu2~20.10.1 => 4-0ubuntu0~20.10.1] (raspi) [13:30] -queuebot:#ubuntu-release- Unapproved: linux-firmware-raspi2 (focal-proposed/multiverse) [3-0ubuntu2~20.04.1 => 4-0ubuntu0~20.04.1] (raspi) [13:58] patviafore: why do you need the archive being open for that? we have base-files and distro-info-data in the release pocket, so it should be ok to build these images? [13:59] doko: don't have a good answer, our process has always been to wait until archive being open [13:59] doko: I'll check to see if anyone on our team has history [13:59] ta [14:02] doko: it sounds like we were just waiting on archive to be open for us to know that cloud images are ready to be built for Ubuntu. We used the archive opening as a +1 signal to start building in the past. Is there a better signal we should be looking for in the future? [14:04] IMHO, "archive open" should mean "cloud images available already" - because so many other process in Ubuntu development depend on them now. [14:04] patviafore: as I said, the earliest would be to have key packages available in the new release pocket. base-files and distro-info-data [14:05] yes, exactly, that's why I think it's good to build those. sil2100, xnox, is that correct? [14:05] rbasak: I think we'd be fine with that (I know autopkgtests depend on lxd). I just wanted to make sure we weren't building images prematurely [14:07] patviafore: I can't think of a case where I'd consider them premature - they could just start as clones of the previous release and I'd be happy. [14:10] patviafore: looks like you're ready to go [14:10] anyway, I would wait for current base-files and distro-info-data [14:10] which are updated now [14:13] doko: thank you. Kicking off a build now. I'll update our process to explicitly wait on those two packages being ready instead of archive open. Is the presence of those packages good enough, or should we be checking in on this channel to make sure they are final (in the future)? [14:14] patviafore: it should be new uploads for the new development version. mentioning the new adjective ("impish" for this cycle) [14:15] alright, thank you [14:16] Laney, juliank: ok, so maybe the bileto creds were not automatically adjusted, will follow up with IS [14:17] Laney: is the http_proxy fix deployed? [14:23] doko: yes, that's the log I linked you to or you can see it in any other recent one [14:23] so yeah, retry away [14:24] let's do an open [14:26] ok, debootstrap retries done [14:27] -queuebot:#ubuntu-release- New binary: llvm-toolchain-snapshot [ppc64el] (impish-proposed/universe) [1:13~++20210418105309+a0898f0cecc7-1~exp1] (no packageset) [14:28] bdmurray: when you're around, can you set impish to current development or whatever it is please to open the archive? [14:28] Laney: its "active development" [14:29] ack [14:37] doko: you can send your email now [14:38] bdmurray: doko: sil2100: there's some unchecked items on the opening list still, can everyone grab a few? [14:41] Laney: sent, and waiting for moderation [14:41] I'll look tomorrow, not today anymore [14:43] the moderation has occurred [14:44] I will try... === Laney changed the topic of #ubuntu-release to: Released: 21.04 Hirsute Hippo | Archive: Open | Highlight ubuntu-archive for archive admin help | Hirsute Release Coordination | We accept payment in cash, cheque or gin | melius malum quod cognoscis | infinity, you will be missed [14:45] I'll grab at least a few later [14:46] 👍 [15:24] -queuebot:#ubuntu-release- Unapproved: rejected magnum [source] (groovy-proposed) [11.0.0-0ubuntu1.1] [15:26] -queuebot:#ubuntu-release- Unapproved: accepted magnum [source] (groovy-proposed) [11.0.0-0ubuntu1.1] [15:29] -queuebot:#ubuntu-release- Unapproved: accepted magnum [source] (focal-proposed) [10.0.0-0ubuntu0.20.04.2] [15:38] Laney, is it normal that topic mentions still "Hirsute Release Coordination"? [15:38] nah, you can change that === LocutusOfBorg changed the topic of #ubuntu-release to: Released: 21.04 Hirsute Hippo | Archive: Open | Highlight ubuntu-archive for archive admin help | Impish Release Coordination | We accept payment in cash, cheque or gin | melius malum quod cognoscis | infinity, you will be missed [15:39] I was wondering about 0 day SRUs and this kind of coordination [15:40] I find useful the topic because I'll learn the new codename in one month or two... [15:40] :) [15:44] oneiric [16:35] Ok, poked IS about Bileto credentials update [16:35] And also uh, poked the security-britney to actually update the creds [16:53] doko: in the past rcj & Odd_Bloke would just copy debootstrap into ~cloudware PPA to allow their livefs builds build for impish. [16:53] vorlon: do you know where landscape-client fixing bug 1911050 went? [16:53] doko: also we can fix live-build to pass in the `new-suite chroot ftpmaster.internal/ubuntu gutsy` to debootstrap => cause then it will use gutsy to build images without needing to wait for debootstrap uploads or migration. [16:54] Bug 1911050 in landscape-client (Ubuntu Hirsute) "AttributeError: 'array.array' object has no attribute 'tostring'" [High, Fix Committed] https://launchpad.net/bugs/1911050 [16:54] bdmurray: bwuh? I do not [16:55] doko: so unless they copy debootstrap out of impish-proposed they can't build images yet, because livefses are built out of release suite only. [16:56] bdmurray: it seems it missed the window for migration into the release pocket, so has only made it to impish release? [16:56] vorlon: weird it just turned up in impish. Should I reupload it for hirsute? [16:56] aha [16:56] bdmurray: I guess so :/ [16:56] and debootstrap will _not_ migrate until we have images [16:56] + lxc launch ubuntu-daily:impish/amd64 docker -c security.nesting=true [16:56] bdmurray: or we could binary copy it back to hirsute-proposed [16:56] Creating docker [16:56] Error: Failed instance creation: Failed getting image: The requested image couldn't be found [16:56] vorlon: that sounds easier [16:56] well for me at least ;-) [16:56] bdmurray: since everything is in order already to use it as an SRU [16:57] patviafore: we must copy debootstrap from impish-proposed to impish into your ppa to build the first livefs images for impish. As without them, debootstrap will never migrate.... as it tests that it can use docker impish images =) [16:57] bdmurray: revivified https://launchpad.net/ubuntu/+source/landscape-client/+publishinghistory [16:57] xnox: already done, thank you [16:57] jchittum clued me in on that [16:59] patviafore: awesomes! [16:59] patviafore: but let's make it smoother for the next release => this must be added to the checklist, right after livefs are copied and debootstrap is uploaded. [16:59] or we should fix up live-build to not need new debootstrap [17:00] LocutusOfBorg: you don't need to sync manually ... [17:00] patviafore: you are still running the builds with "repo_snapshot_stamp 1619618924" but that is still currently broken, is it not? [17:01] (my branches to fix up iptables are not merged yet) [17:02] doko, I'm syncing only nodejs stuff, to trigger trivial tests before the big sync [17:02] I want nodejs to fast migrate whenever possible [17:13] xnox: thanks for the catch, mess up on our part [17:15] xnox: also agreed to make this smoother for next release. I am already updating CPC process docs to make sure this step gets done and document what the triggers are. [17:37] is autosync on now? [17:38] Laney: ^^^ [17:38] the run that just finished says "Not copying packages in dry-run mode" [17:43] L_aney wanted to get a run of proposed-migration in first before dropping the block [17:44] ok :) [17:47] it would be nice to delay auto-sync for one more day... :D [17:47] so we can have some perl/node stuff migrate and ocaml migrate too before the world entangles [17:47] but probably due to freeze in Debian we don't have that many transitions [17:58] -queuebot:#ubuntu-release- New: rejected php-gearman [source] (xenial-proposed) [1.1.2-96-ge77f981+1.1.2+-2~ubuntu16.04.1] [17:59] -queuebot:#ubuntu-release- New: rejected ostree [source] (xenial-proposed) [2016.15-2ubuntu1~ubuntu16.04.1] [18:00] -queuebot:#ubuntu-release- New: rejected bubblewrap [source] (xenial-proposed) [0.1.7-0ubuntu0.16.04.1] [18:01] -queuebot:#ubuntu-release- New: rejected flatpak [source] (xenial-proposed) [0.8.2-1~ubuntu16.04.1] [18:02] -queuebot:#ubuntu-release- New: rejected woff2 [source] (xenial-proposed) [1.0.2-1ubuntu1~16.04.1] [19:54] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-advantage-tools [source] (xenial-proposed) [27.0~16.04.1] [19:54] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-advantage-tools [source] (focal-proposed) [27.0~20.04.1] [19:55] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-advantage-tools [source] (hirsute-proposed) [27.0~21.04.1] [20:23] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (xenial-proposed) [1.2.35] [21:35] -queuebot:#ubuntu-release- New: accepted google-osconfig-agent [arm64] (xenial-proposed) [20210219.00-0ubuntu1~16.04.0] [22:21] * enyc meows [22:41] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (bionic-proposed/main) [17 => 27.0~18.04.1] (core) [22:42] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (groovy-proposed/main) [24.4 => 27.0~20.10.1] (core) [22:42] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (xenial-proposed/main) [10ubuntu0.16.04.1 => 27.0~16.04.1] (no packageset) [22:43] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [20.3 => 27.0~20.04.1] (core) [22:43] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (hirsute-proposed/main) [26.2 => 27.0~21.04.1] (core)