[01:00] <utkarsh2102> vorlon: apologies for not checking it thoroughly and thanks for fixing it! \o/
=== tomreyn_ is now known as tomreyn
[06:37] <juliank> vorlon: sil2100 wanted to skip test them
[07:06] <sil2100> mwhudson: hey! Is the fix for https://bugs.launchpad.net/subiquity/+bug/1946668 already available in the stable channel?
[07:06] <ubottu> Launchpad bug 1946668 in subiquity "subiquity no longer confirms that the requested storage config is desired" [Critical, Fix Committed]
[07:08] <sil2100> jibel: morning! Will you be helping us with some regular desktop testing this release?
[07:24] <jibel> sil2100, Good morning, yes, as usual
[07:35] <sil2100> Thank you ;)
[07:36] <sil2100> This might not be the *final* image, but hm, who knows
[07:37]  * sil2100 feels a bit weak today, bad timing
[07:47] <juliank> sil2100: did you skiptest the packages?
[07:47] <juliank> sil2100: yesterday, the meta packages
[07:48] <juliank> sil2100: db-defaults|init-system-helpers|java-common|lsb|ruby-defaults|tcltk-defaults
[07:48] <juliank> sil2100: because vorlon was complaining that none of them were skiptested apparently
[08:00] <sil2100> I did!
[08:00] <sil2100> Did I put wrong versions..?
[08:01] <sil2100> https://git.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu/commit/?id=cf04445d9050f199f60b8171a8aaf02c93544a43 <- did I miss something here?
[08:01] <ubottu> Commit cf04445 in ~ubuntu-release/britney/+git/hints-ubuntu "skiptest a few packages from the no-change rebuild list."
[08:03] -queuebot:#ubuntu-release- Unapproved: retext (impish-proposed/universe) [7.2.1-3 => 7.2.2-1] (no packageset) (sync)
[08:03] <sil2100> juliank: most of the packages actually migrated, so I don't know what vorlon was complaining about?
[08:04] <juliank> sil2100: it was 8 hours ago, probably last lines in your backlog for yesterday
[08:04] <juliank> > juliank: so you dropped metapackage-triggered autopkgtest runs; was there also coordination to skiptest these packages so they would migrate? I see base-files was skiptest'ed, but no others
[08:04] <juliank> >  (and 2075 tests 'in progress' on update_excuses, but only 1161 in the queue)
[08:04] -queuebot:#ubuntu-release- Unapproved: accepted retext [sync] (impish-proposed) [7.2.2-1]
[08:05] <sil2100> I think vorlon was just confused, as you can see above ^
[08:05] <juliank> ok
[08:05] <juliank> just wanted to check with you
[08:06] <sil2100> I think it's good, I mean, I might have missed a package or two but I *think* what was supposed to go in went in
[08:06] <sil2100> Maybe vorlon thought we were letting more packages in
[08:14] <paride> sil2100, hi! so it's pretty clear now that https://bugs.launchpad.net/snapd/+bug/1946656 is not a snapcraft.io issue :/
[08:14] <ubottu> Launchpad bug 1946656 in Ubuntu CD Images "[daily impish-live-server] snap stuck in the installer system" [Undecided, New]
[08:15] <sil2100> paride: yeah... ;/
[08:17] <mwhudson> sil2100: no, let me fix that
[08:20] <sil2100> mwhudson: thanks! And yeah, I see that the snapd team is helping out, but since we already know this is serious, I added LP: #1946656 as a release blocker
[08:20] <ubottu> Launchpad bug 1946656 in Ubuntu CD Images "[daily impish-live-server] snap stuck in the installer system" [Undecided, New] https://launchpad.net/bugs/1946656
[08:21] <sil2100> So if you and dbungert could put a high priority on this one (in case it's somehow subiquity doing something funny!), that'd be awesome ;)
[08:44] <paride> jibel, hi! I can't reach venonat anymore, and it's also offline on the platform-qa-jenkins
[08:44] <paride> are you perhaps doing some cleanup or maintenance there?
[08:47] <mwhudson> ahh
[08:47] <mwhudson> sil2100: for sure
[08:47] <mwhudson> somehow we have two copies of the requests library in the snap :(
[08:48] <jibel> paride, no, I didn't touch anything
[08:55] <paride> jibel, not a good day for venonat to go down :/ I'm looking for a bmc address for the machine
[09:06] -queuebot:#ubuntu-release- Unapproved: gdm3 (impish-proposed/main) [41~rc-0ubuntu1 => 41~rc-0ubuntu2] (desktop-core)
[09:07] <seb128> sil2100, ^ would be nice if we could get that one accepted, it can be turned into a 0 day SRU if really needed but if we get a respin it would be nice to let in, it should fix the session selection being unreliable
[09:09] <mwhudson> sil2100: so i think i have a patch for bug 1946656, do you want me to try to get it landed now or is it ok if it waits for dbungert to have a look at it?
[09:09] <ubottu> Bug 1946656 in Ubuntu CD Images "[daily impish-live-server] snap stuck in the installer system" [Undecided, New] https://launchpad.net/bugs/1946656
[09:19] <sil2100> mwhudson: you're close to EODing, right? Since of course we'd like to get this landed and released into stable ASAP so we can respin, but if you feel that it would be best to get dbungert's review first, we can wait. Dan has the power to push to stable, right?
[09:19] <sil2100> seb128: let me get to you in a moment!
[09:20] <mwhudson> sil2100: i am basically asleep, yes
[09:21] <mwhudson> sil2100: dan and steve can both push to stable
[09:22] <paride> Once there's .snap available I can verify the fix via `livefs_edit --inject-snap`
[09:24] <mwhudson> paride, sil2100: https://github.com/canonical/subiquity/pull/1094
[09:24] <ubottu> Pull 1094 in canonical/subiquity "close the session object after each request to the snapd API" [Open]
[09:26] <paride> mwhudson, thanks! I'll build a snap from that branch and test it
[09:28] <sil2100> mwhudson: ok, let's wait for Dan then, thanks for prepping the fix! ;)
[09:28] <mwhudson> sil2100: yeah time to crash
[09:34] -queuebot:#ubuntu-release- Unapproved: linux-firmware-raspi2 (impish-proposed/restricted) [4-0ubuntu3 => 5-0ubuntu1] (raspi)
[09:48] -queuebot:#ubuntu-release- Unapproved: mate-media (impish-proposed/universe) [1.26.0-0ubuntu1 => 1.26.0-0ubuntu2] (ubuntu-mate)
[10:04] -queuebot:#ubuntu-release- Unapproved: mate-notification-daemon (hirsute-proposed/universe) [1.24.1-1 => 1.26.0-0ubuntu2] (ubuntu-mate, ubuntukylin)
[10:08] -queuebot:#ubuntu-release- Unapproved: accepted oem-sutton.simon-baird-meta [sync] (focal-proposed) [20.04~ubuntu3]
[10:12] -queuebot:#ubuntu-release- Unapproved: accepted oem-sutton.newell-cade-meta [sync] (focal-proposed) [20.04~ubuntu3]
[10:23] <sil2100> waveform: uh oh what's this linux-firmware-raspi upload in the queue? Can you give me more context? Is this making the video hang situation better?
[10:25] <sil2100> Ah, no, it's actually for the no-display thing, right?
[10:25] <sil2100> This bug is confusing me
[10:25] <sil2100> Since people are basically using this one bug for like talking about two bugs
[10:27] <waveform> sil2100, sure -- I'd forgotten about this in all the mess around the video freeze thing: a pre-condition of the kernel fix for the no-display bug is a firmware bump for compatibility with the kernel side of things
[10:28] <waveform> had it in the PPA for testing, but completely forgot to push it the archive
[10:28] <waveform> however, this does nothing for the video freeze issue
[10:29] <sil2100> ouch, but we basically need it for the no-display bug to be fixed? And I suppose it's quite serious, right?
[10:30] <waveform> correct
=== ginggs_ is now known as ginggs
[10:34] <waveform> (I should add while it is obviously serious, it does appear limited to a smaller number of monitors -- we've only had a couple of reproduction cases, while the freeze issue appears ubiquitous albeit less than immediate depending on the connected monitor)
[10:35] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware-raspi2 [source] (impish-proposed) [5-0ubuntu1]
[10:48]  * sil2100 needs to AFK for a bit
[11:02] <seb128> sil2100, did you get to review the gdm upload? it's a tiny patch should be easy to review
[11:30] <Wimpy> Please reject mate-notification-daemon (hirsute-proposed/universe) 1.26.0-0ubuntu2
[11:30] <Wimpy> hirsute ^
[11:31] -queuebot:#ubuntu-release- Unapproved: mate-notification-daemon (impish-proposed/universe) [1.26.0-0ubuntu1 => 1.26.0-0ubuntu2] (ubuntu-mate, ubuntukylin)
[11:55] <sil2100> Wimpy: on it
[11:56] <sil2100> seb128: not yet, will get to it - we might pull it since we might be respinning desktop
[11:56] <Wimpy> sil2100: ty
[11:57] -queuebot:#ubuntu-release- Unapproved: rejected mate-notification-daemon [source] (hirsute-proposed) [1.26.0-0ubuntu2]
[12:00] <sil2100> seb128: I'll accept it, and we can think of migrating it into release
[12:01] -queuebot:#ubuntu-release- Unapproved: accepted gdm3 [source] (impish-proposed) [41~rc-0ubuntu2]
[12:07] <sil2100> hmm, I wonder if maybe the freeze block is botched or something? I don't see linux-firmware-raspi2 in it
[12:08] <sil2100> Even though it's seeded for ubuntu-server-raspi
[12:08] <waveform> sil2100, should be seeded for desktop too -- something to do with it being in restricted maybe?
[12:09] <seb128> sil2100, thx
[12:12] <sil2100> waveform: hm, maybe, I don't know how generate-freeze-block works - anyway, right now it was good that it is migrating, but we need to keep this in mind
[12:12] <sil2100> bdmurray, vorlon: ^
[12:16] <jchittum> marked bug 1944004 as fixed released. If anyone else wants to spin up some s390x or ppcle64 lxd stuff to test, please do. Public cloud pipelines have happy test runs so far leading up to release
[12:16] <ubottu> Bug 1944004 in snapd "snapd.seeded.service never finishes on non-amd64" [Undecided, New] https://launchpad.net/bugs/1944004
[12:17] <sil2100> jchittum: hey! Any blockers from the cloud POV we should still be keeping an eye out for impish?
[12:25] <jchittum> It doesn't look like it. the snapd issue is solved, and the cloud-init + google cloud agent seems unblocked (though it's a workaround, not root cause fixed, I believe)
[12:31] <sil2100> \o/
[12:33] <sil2100> juliank: hey! How's the glib fix going? I saw one review already, you think you can prep an upload now?
[12:36] <juliank> sil2100: no review yet, just comment from NM folks
[12:37] <juliank> sil2100: Philip Withnall just tagged it a minute ago, so maybe it gets reviewed _soon_?
[12:37] <juliank> sil2100: So I can still upload it we can always fix it in proposed
[12:42] -queuebot:#ubuntu-release- Unapproved: glib2.0 (impish-proposed/main) [2.68.4-1build1 => 2.68.4-1ubuntu1] (core, i386-whitelist)
[12:42] <juliank> sil2100: ^ there it is
[12:43] <sil2100> \o/
[12:43] <sil2100> I'll review it in a sec
[12:47] <sil2100> juliank: ok, I see one review comment on the PR!
[12:48] <sil2100> But in generall it looks like a +1
[12:53] <juliank> sil2100: shall I implement the suggestion and reupload?
[12:53] <juliank> it's certainly cleaner that way
[13:02] <juliank> sil2100: The new patch is much smaller, it's nice
[13:05] <sil2100> \o/
[13:05] <sil2100> juliank: if you're confident that it works, upload away o/
[13:05] <juliank> sil2100: uploaded
[13:07] -queuebot:#ubuntu-release- Unapproved: glib2.0 (impish-proposed/main) [2.68.4-1build1 => 2.68.4-1ubuntu1] (core, i386-whitelist)
[13:08] -queuebot:#ubuntu-release- Unapproved: rejected glib2.0 [source] (impish-proposed) [2.68.4-1ubuntu1]
[13:10] -queuebot:#ubuntu-release- Unapproved: accepted glib2.0 [source] (impish-proposed) [2.68.4-1ubuntu1]
[13:11] <bdmurray> sil2100: ubiquity uploaded
[13:11] <sil2100> \o/
[13:11] <sil2100> Reviewing as well
[13:12] -queuebot:#ubuntu-release- Unapproved: ubiquity (impish-proposed/main) [21.10.9 => 21.10.10] (desktop-core)
[13:12] <sil2100> juliank: once the package is built, can you give it a spin to confirm that it's all working as expected and give me a sign?
[13:12] <juliank> sure
[13:16] -queuebot:#ubuntu-release- Unapproved: glm (impish-proposed/main) [0.9.9.8+ds-1 => 0.9.9.8+ds-1ubuntu1] (ubuntu-desktop)
[13:20] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (impish-proposed) [21.10.10]
[13:24] <juliank> ugh it's still running tests
[13:40] <juliank> sil2100: verified the built binaries
[13:45] <sil2100> juliank: \o/
[13:46] <sil2100> Let me put an unblock hint for that
[13:46] <sil2100> Same for ubiquity
[13:48] <sil2100> seb128: I also put an unblock for gdm3, but please double-check if the binary in -proposed works as expected
[13:49] <seb128> sil2100, ack, thank you!
[13:49] <seb128> sil2100, we are keeping the stack of rebulding in proposed for release?
[13:50] <sil2100> seb128: you mean the no-change rebuilds?
[13:50] <seb128> yes
[13:51] <sil2100> Yeah, those stay blocked, we'll pull them off into JJ
[13:52] <sil2100> Since it's just too late and there's too many, we'd have to slip by a week at least to get them all migrated for impish
[13:52] <dbungert> sil2100: catching up on scrollback, I see we have a plausible fix for subiquity/snapd
[13:53] <sil2100> dbungert: hey! Good to see you! Yes, there's a fix that mwhudson prepared and wanted you to review+merge+release if all good
[13:53] <dbungert> reading it now
[13:53] <sil2100> Thanks
[14:02] <bdmurray> dbungert: There'll also be a new version of ubiquity on the install media later today which should fix bug 1942648. So if you can test that later that would be helpful.
[14:02] <ubottu> Bug 1942648 in ubiquity (Ubuntu Impish) "restart button remains visible in the advanced partitioner after the bitlocker page is shown" [Medium, In Progress] https://launchpad.net/bugs/1942648
[14:03] <dbungert> bdmurray: will do
[14:43] <vorlon> sil2100, juliank: oh, poor eyesight, I didn't find the skiptest hints that were added but I see them now ;)
[14:58] <bdmurray> vorlon: with the removal of azure-cli do we also want to add it to the sync blacklist as it is in Debian?
[14:59] <vorlon> sil2100, bdmurray: generate-freeze-block: unfortunately this script uses the local apt cache to associate seeded binaries with source packages, which means that if armhf/arm64 is not in your apt sources on the host system, it doesn't land in the block hint
[14:59] <vorlon> bdmurray: my understanding of the removal is that it's removed because it's currently broken, not because it's unfixably broken; but I didn't review the rationale for azure-cli removal since apw had already done it
[15:00] <apw> vorlon, the version in debian is anchient and broken, upstream changes about every two weeks seemingly
[15:00] <bdmurray> "Microsoft further recommends their own PPAs"
[15:00] <bdmurray> that was the part I was thinking about
[15:00] <vorlon> apw: then perhaps you want to add it to the sync blacklist, per bdmurray's question :)
[15:01] <CodeMouse92> I was in that meeting with MS, btw.
[15:02] <CodeMouse92> MS requested that azure-cli be removed because it's too many versions behind, and they didn't *exactly* own the packaging.
[15:02] <apw> vorlon, ack
[15:02] <CodeMouse92> They are WANTING to package a newer version themselves, and hoping for MIR, but there are some other factors that may hold that back.
[15:02] <juliank> sil2100, vorlon So I requeued all tests a couple hours that got lost in deletions; the running to normal queue and running-alwaysfail to huge. But now I uploaded glib2.0 and queues are huge again :(
[15:03] <juliank> shall we move the glib2.0 ahead of the others / into the normal queue?
[15:03] <vorlon> juliank: huge queue backlog seems relatively small now; we could juggle but I'm not sure it actually matters?  I'd give it a few hours and see
[15:04] <vorlon> when does sil2100 want this migrated by
[15:04] <vorlon> I'll work back from that target ;)
[15:04] <dbungert> sil2100: I have merged the subiquity/snapd PR, and am starting the release process there
[15:04] <juliank> I guess it's on all images, so ASAP?
[15:04] <paride> dbungert, great
[15:04] <vorlon> juliank: in that case maybe we want a skiptest
[15:05] <juliank> possibly, maybe he already is planning on / has added one
[15:05] -queuebot:#ubuntu-release- Unapproved: util-linux (impish-proposed/main) [2.36.1-8ubuntu1 => 2.36.1-8ubuntu2] (core, i386-whitelist)
[15:05] <juliank> vorlon: I wonder if we should queue self-tests (foo triggers foo) on normal queue even if foo is huge otherwise
[15:05] <paride> dbungert, I noticed that at the moment we have subiquity 21.10.2+git12.06a2626d in latest/stable/ubuntu-20.10. Is having a +gitX version in stable intended?
[15:06] <juliank> because those self-tests could provide timely feedback on lazy uploaders / syncs :D
[15:06] <paride> dbungert, or was it "stable but not really", and now we'll try to go with 21.10.3?
[15:07] <juliank> which reminds me I did not run the glib2.0 autopkgtests
[15:07] <juliank> I'll move up the self-test
[15:07] <juliank> on amd64
[15:08] <dbungert> paride: that's an appropriate git commit id for post-21.10.2, for a fix for the disk format confirm dialog.  I'm guessing that version was promoted as part of testing that fix.  I'm starting the process to replace with 21.10.3.
[15:09] <paride> dbungert, good, that matches what I expected, thanks
[15:11] <bdmurray> vorlon: so how do you use generate-freeze-block?
[15:11] <vorlon> juliank: I wouldn't object, though I'm not sure it gives us very much benefit overall
[15:11] <vorlon> bdmurray: I'm not sure I've ever been the one to use it officially :)
[15:12] <juliank> vorlon: I think we have uploads failing their own tests a couple of times, could be useful if you then don't need to run all the huge tests :)
[15:12] <vorlon> bdmurray: running it an environment that has all the archs added as dpkg --add-architecture would solve this problem
[15:12] <juliank> people forget to run locally, or it only fails in the cloud :D
[15:13] <sil2100> vorlon: I'd like the glib2.0 migrated ASAP ;)
[15:14] <vorlon> sil2100: so will you skiptest it?  any tests you want to see finish before doing so?
[15:14] <sil2100> Since this is a release blocker fix that I'd like to have in release before we respin
[15:14] <sil2100> eh, crap, forgot glib2.0 triggers so much
[15:14] <vorlon> :)
[15:15] <sil2100> I'd for sure like to see if glib2.0 ADT tests pass
[15:15] <vorlon> ubiquity is also still building
[15:15] <vorlon> on riscv64
[15:15] <sil2100> Rest I think we could just skiptest
[15:16] <sil2100> juliank: considering the nature of the change, would it make sense to also wait for network-manager ADT tests?
[15:16] <sil2100> I don't actually know what we test there tho
[15:16] <vorlon> ok then let me queue those tests in the regular queue
[15:17] <juliank> I did requeue glib2.0 itself and its running already
[15:17] <juliank> I just copied them and did not clean up the dupes so far
[15:17] <sil2100> Thanks!
[15:18] <sil2100> vorlon: so basically right now we're waiting for the following to migrate: glib2.0, ubiquity, gdb3 + waiting for dbungert to push the new subiquity to stable
[15:19]  * vorlon nods
[15:19] <sil2100> *gdm3
[15:19] <vorlon> and that's the subiquity workaround for the snapd restart hang?
[15:19] <dbungert> vorlon: yes
[15:19] <vorlon> (so we're not waiting for snapd itself?)
[15:19] <sil2100> Well, gdm3 is a bit optional, same for ubiquity, but since we respin a lot it made sense to include those
[15:19] <sil2100> vorlon: that's correct, yes
[15:26] <dbungert> paride: 21.10.3 on latest/candidate
[15:28] <paride> dbungert, thanks, I'm baking it into an ISO right now
[15:31] -queuebot:#ubuntu-release- Unapproved: zfs-linux (hirsute-proposed/main) [2.0.2-1ubuntu5.3 => 2.0.2-1ubuntu5.4] (core, kernel-dkms)
[15:39] <paride> dbungert, tested and LGTM, I updated https://bugs.launchpad.net/ubuntu-cdimage/+bug/1946656
[15:39] <ubottu> Launchpad bug 1946656 in Ubuntu CD Images "[daily impish-live-server] snap stuck in the installer system" [Undecided, New]
[15:39] <dbungert> paride: great, ty
[15:39] <dbungert> I'm letting an autoinstall test run, I've already done a manual test
[15:42] <sil2100> \o/
[15:43] <dbungert> sil2100: subiquity 21.10.3 on channel latest/stable/ubuntu-21.10
[15:45] <sil2100> Great news, thanks a lot o/
[15:50] <bdmurray> vorlon: I ran generate-freeze-block in a chroot w/ the dpkg architectures added and uh the number of packages in the freeze was reduced
[15:53] <sil2100> uh
[15:54]  * vorlon squints :)
[15:54] <vorlon> bdmurray: with all components enabled as well?
[15:54] <bdmurray> indeed, I'm double checking in a VM though
[15:58] <bdmurray> oh, do I also need to configure ports.ubuntu.com?
[15:58] <vorlon> bdmurray: oh yes, you would
[15:59] <vorlon> sorry :)
[16:03] <sil2100> I see that for the new ubiquity the casper ADT tests for amd64 failed, I retried them - but the test failure seems unrelated to anything in ubiquity
[16:05] <sil2100> So I might eventually skiptest ubiquity as well
[16:05]  * vorlon nods
[16:32] <bdmurray> Thanks to vorlon of 10 years ago for https://wiki.ubuntu.com/MultiarchHowto
[16:33] <bdmurray> vorlon: so I added them to /etc/dpkg/dpkg.cfg.d/multiarch and updated sources.list and ran apt-get update and now I still have the same number of packages being output by generate-freeze-block
[16:34] <bdmurray> I confirmed my cache is good via apt-cache policy hello:$arch
[16:40] <sergiodj> vorlon: hi there.  do you think we can proceed with 0-day SRU for u-a-t on Impish?  I'm holding back the uploads for the other series until we get this sorted out
[16:41] <sergiodj> FWIW, the u-a-t team improved the Test Case section of https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942929.  I reviewed it and it looks good for me
[16:41] <ubottu> Launchpad bug 1942929 in ubuntu-advantage-tools (Ubuntu Impish) "[SRU] ubuntu-advantage-tools (27.2.2 -> 27.3) Xenial, Bionic, Focal, Hirsute" [Undecided, New]
[16:42] <xnox> bdmurray:  i think /etc/dpkg/dpkg.cfg.d/multiarch has not been used for years now. one adds architectures with dpkg --add-architecture and then in sources.list one can specify required architectures in [] as options after deb.
[16:57] <sil2100> I go AFK now for some moments, but I skiptested ubiquity
[16:58] <sil2100> vorlon, bdmurray: I'd say that once we have some positive results on glib2.0 and network-manager tests for the glib2.0 upload, we should skiptest it and let it migrate as well
[16:58] <sil2100> Can you guys keep an eye on it?
[16:59] <bdmurray> I'll keep both my eyes on it
[17:03] <paride> sil2100, do you plan to trigger the build of another round of dailies today?
[17:04] <bdmurray> paride: yes, because of glib2.0
[17:05] <paride> bdmurray, good to hear, as I want to retrigger the iso tests with images with the new subiquity
[17:09] -queuebot:#ubuntu-release- Unapproved: zfs-linux (focal-proposed/main) [0.8.3-1ubuntu12.13 => 0.8.3-1ubuntu12.14] (core, kernel-dkms)
[17:30] <bdmurray> Ah, making progress with generate-freeze-block.
[17:45] <bdmurray> So these would get added to the freeze-block after some hackery
[17:45] <bdmurray> https://paste.ubuntu.com/p/6gXvxHWGYY/
[17:46] <bdmurray> That all seems reasonable so I'll them in
[17:49] <bdmurray> Well except the freeze is britney's hints has less than what I have even without my changes...
[17:56] <bdmurray> I've pushed a new freeze hints
[18:02] <juliank> glib2.0 itself looks good, nm passed on ppc64el so far
[18:03] <bdmurray> juliank: thanks for the update
[18:03] <juliank> I'm just excited :D
[18:17] <vorlon> sergiodj: 0-day SRU is fine; I haven't accepted it yet into -proposed because I didn't want to cause any confusion vs mastering the release media
[18:18] <sergiodj> vorlon: awesome, so I will go ahead and perform the remaining uploads.  thanks
[18:27] <laney> good luck team ;-)
[18:28] <laney> sort of missing tonight's all nighter :D
[18:30] <vorlon> you have my permission to stay up all night anyway
[18:40] <bdmurray> network-manager and glib2.0 passed on amd64 now
[19:00] <juliank> bdmurray: hooray
[19:00] <sil2100> \o/
[19:00] <sil2100> Ok, let me skiptest it after a quick look
[19:02] <sil2100> Seeing that the glib2.0 tests passed on armhf, amd64, ppc64el and s390x - I think it's safe to say we have coverage of at least those two core test suites
[19:03] <bdmurray> Where did the arm64 test go?
[19:04] <vorlon> into a queue
[19:04] <sil2100> And I see it's rather green in other tests too, one regression I see so far, looking at it
[19:04] <bdmurray> update_excuses said it was running
[19:05] <sil2100> hm hmmm
[19:05] <bdmurray> oh, does it say test in progress for everything in the queue?
[19:05] <sil2100> Bail out! GLib-Net:ERROR:../tls/base/gtlsconnection-base.c:1400:g_tls_connection_base_handshake_thread_verify_certificate: assertion failed: (priv->handshake_context)
[19:05] <sil2100> FAIL: libgdata/contacts.test (Child process killed by signal 6)
[19:05] <vorlon> bdmurray: yes
[19:05] <sil2100> Probably unrelated, but it makes me shiver a bit
[19:07] <sil2100> Worrying, since I didn't see this failure before there
[19:08] <juliank> sil2100: looks unrelated, how would network online monitoring break tls handshake
[19:09] <juliank> sil2100: where was that?
[19:09] <sil2100> And it's perfectly fine for other arches, weird!
[19:09] <sil2100> https://autopkgtest.ubuntu.com/packages/libg/libgdata/impish/armhf
[19:10] <juliank> sil2100: I see that on 2021-09-10 20:22 for the gobject-introspection/1.68.0-1build1 libffi/3.4.2-1ubuntu3	 run too
[19:10] <sil2100> \o/
[19:11] <sil2100> Anyway, checked other failures, all flaky tests
[19:16] <mwhudson> good mirning
[19:16] <mwhudson> *morning
[19:16] <mwhudson> how extremely on fire are we feeling today
[19:17] <sil2100> Morning!
[19:17] <sil2100> Less on fire than in my morning I suppose
[19:18] <mwhudson> that's good
[19:20] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (xenial-proposed/main) [27.2.2~16.04.1 => 27.3~16.04.1] (no packageset)
[19:21] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (bionic-proposed/main) [27.2.2~18.04.1 => 27.3~18.04.1] (core)
[19:23] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [27.2.2~20.04.1 => 27.3~20.04.1] (core)
[19:39] -queuebot:#ubuntu-release- Unapproved: barbican (hirsute-proposed/main) [2:12.0.0-0ubuntu1 => 2:12.0.0-0ubuntu2] (openstack)
[19:58] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (hirsute-proposed/main) [27.2.2~21.04.1 => 27.3~21.04.1] (core)
[20:19] <bdmurray> sil2100: glib2.0 seems to have migrated now, shall I create new images?
[20:22] <sil2100> oooh, already?
[20:22] <sil2100> bdmurray: do we have all ubiquity, glib2.0, gdm3?
[20:23] <sil2100> bdmurray: if yes, please spin images indeed o/
[20:25] -queuebot:#ubuntu-release- Unapproved: geonkick (impish-proposed/universe) [2.8.0-0ubuntu1 => 2.8.0-0ubuntu2] (ubuntustudio)
[20:26] <Eickmeyer[m]> ^ That should be good for a 0-day SRU.
[20:37] <bdmurray> rebuilding the world now
[20:54] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Impish Final] has been updated (20211012)
[20:55] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Impish Final] has been updated (20211012)
[21:03] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Impish Final] has been updated (20211012)
[21:05] <RikMills> mparillo: https://i.imgur.com/jXJTxJ2.png
[21:05] <RikMills> bdmurray: ^^
[21:08] <bdmurray> hunh, I checked ubuntu-quality and ubuntu-flavors but not here
[21:11] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Impish Final] has been updated (20211012)
[21:11] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Impish Final] has been updated (20211012)
[21:12] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Impish Final] has been updated (20211012)
[21:13] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Impish Final] has been updated (20211012)
[21:14] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Impish Final] has been updated (20211012)
[21:28] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Impish Final] has been updated (20211012)
[21:39] <bdmurray> dbungert: bug 1942648 should be testable now
[21:39] <ubottu> Bug 1942648 in ubiquity (Ubuntu Focal) "restart button remains visible in the advanced partitioner after the bitlocker page is shown" [Undecided, New] https://launchpad.net/bugs/1942648
[21:46] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Impish Final] has been updated (20211012)
[21:46] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Impish Final] has been updated (20211012)
[21:46] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Impish Final] has been updated (20211012)
[21:46] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Impish Final] has been updated (20211012)
[22:02] <mparillo> bdmurray: If the question is why did I add https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1890173 that is because my bug https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681144 was marked as a duplicate
[22:02] <ubottu> Launchpad bug 1890173 in ubiquity (Ubuntu) "[kubuntu] 'Release notes' link doesn't open" [Medium, Fix Released]
[22:02] <ubottu> Launchpad bug 1890173 in ubiquity (Ubuntu) "[kubuntu] 'Release notes' link doesn't open" [Medium, Fix Released] [duplicate: 1681144]
[22:04] <mparillo> It is not a critical bug, but it certainly is a bug.
[22:05] <bdmurray> mparillo: both of those bugs are quite old could you open a new one?
[22:05] <mparillo> The bug is reproducible in a VM. None of the slideshow links open.
[22:05] <mparillo> Sure.
[22:06] <bdmurray> mparillo: slideshow links are different than the release notes link which first shows up
[22:07] <mparillo> Then my original bug should not be a duplicate.
[22:08] <bdmurray> Let's start off with a new bug and see what we can do about sorting this out
[22:09] <dbungert> bdmurray: bitlocker thing looks resolved
[22:09] <bdmurray> dbungert: cool, thanks for checking
[22:11] <mparillo> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1946803
[22:11] <ubottu> Launchpad bug 1946803 in ubiquity (Ubuntu) "Clicking on URLs in Kubuntu Installer Slideshow does nothing" [Undecided, New]
[22:12] <bdmurray> mparillo: thanks and this is with an impish image?
[22:12] <mparillo> Yup. Let me get the SHA256
[22:13] <mparillo> 282b5125da5a952e8ce59652fe35be618e71a0cfee497715bf91219fbe8cacf9 *impish-desktop-amd64.iso
[22:14] <mparillo> But it has been that way since at least 17.04. I am pretty sure I have tested this on almost every release and beta reported it every time.
[22:16] <mparillo> Also at least one time, I tested on Lubuntu (looks like the 17.10 beta back when once or twice the shipped LXQt and LXDE) and it was on their LXQt installer back then.
[22:23] <vorlon> sil2100, bdmurray: fyi I've just updated https://wiki.ubuntu.com/ReleaseProcess to document the bits that I've been doing each release cycle to clean up i386 binaries; this ought to be officially part of the release process instead of something in my head
[22:23] <vorlon> (I would put it on the discourse, but the checklist seems to be a comment rather than part of the post, oops?  But anyway, it's done for this cycle)
[22:23] <bdmurray> vorlon: you can still edit the checklist
[22:23] <vorlon> ah?
[22:24] <vorlon> interesting
[22:24] <bdmurray> I see a pencil in the header of the comment
[22:24] <vorlon> well anyway, it's done for this cycle, but feedback appreciated so it's clear what to do for the future
[22:25] <vorlon> for the moment the script is in foundations-sandbox which is not public, but better than it being local to my machine
[22:25] <vorlon> also the script is terrible
[22:28] <bdmurray> mparillo: okay, I've recreated the issue
[22:29] <mparillo> Thank you.
[22:30] <mparillo> As I said, I never thought it was a critical bug, but it is good to see it live again.
[22:30] <mparillo> There was this guy once who used to call that kind of thing a paper-cut.
[22:46] -queuebot:#ubuntu-release- Unapproved: mate-menus (impish-proposed/universe) [1.26.0-0ubuntu1 => 1.26.0-0ubuntu2] (ubuntu-mate)
[23:30] <bdmurray> I don't know where our riscv64 builds went
[23:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Impish Final] has been updated (20211012)
[23:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Impish Final] has been updated (20211012)
[23:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unleashed [Impish Final] has been updated (20211012)
[23:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Impish Final] has been updated (20211012)
[23:49] <bdmurray> well there they are!
[23:50] <jawn-smith> nice, good timing