[00:54] -queuebot:#ubuntu-release- Unapproved: update-notifier (bionic-proposed/main) [3.192.1.9 => 3.192.1.10] (ubuntu-desktop, ubuntu-server)
[00:54] -queuebot:#ubuntu-release- Unapproved: update-notifier (xenial-proposed/main) [3.168.13 => 3.168.14] (ubuntu-desktop, ubuntu-server)
[00:55] -queuebot:#ubuntu-release- Unapproved: update-notifier (focal-proposed/main) [3.192.30.6 => 3.192.30.7] (ubuntu-desktop, ubuntu-server)
[00:56] -queuebot:#ubuntu-release- Unapproved: update-notifier (hirsute-proposed/main) [3.192.40 => 3.192.40.1] (ubuntu-desktop, ubuntu-server)
[00:56] -queuebot:#ubuntu-release- Unapproved: update-notifier (impish-proposed/main) [3.192.40 => 3.192.41] (ubuntu-desktop, ubuntu-server)
[05:55] -queuebot:#ubuntu-release- Unapproved: rejected ceph [sync] (impish-proposed) [16.2.1-0ubuntu0.21.04.1]
[05:55] -queuebot:#ubuntu-release- Unapproved: accepted ruby2.7 [sync] (impish-proposed) [2.7.2-4ubuntu1.1]
[06:52] <doko> jibel: ubuntu-report dashboard ping
[07:08] <jibel> Hi doko
[07:12] <doko> jibel: see private message please
[08:35] -queuebot:#ubuntu-release- Unapproved: debootstrap (impish-proposed/main) [1.0.123ubuntu6 => 1.0.124] (desktop-core) (sync)
[08:37] <Laney> right I'm going to try one test run of impish proposed-migration against the new environment
[08:42] -queuebot:#ubuntu-release- Unapproved: udisks2 (hirsute-proposed/main) [2.9.2-1 => 2.9.2-1ubuntu1] (core, i386-whitelist)
[09:09] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-13 [sync] (focal-proposed) [13.0.7+5-0ubuntu1~20.04]
[09:12] -queuebot:#ubuntu-release- New: accepted openjdk-16 [sync] (focal-proposed) [16.0.1+9-1~20.04]
[10:00] <Laney> sil2100: time to switch bileto/security britney
[10:08] <LocutusOfBorg> just a question, recipes/ppas are still not working with impish? they still try to autogenerate a version such as boinc_7.18.0+dfsg+git20210426+r24906~r93~ubuntu21.04.1_source.changes
[10:10] <cjwatson> I think that's just because base-files hasn't migrated yet
[10:10] <cjwatson> Which is presumably related to Laney's ongoing work on proposed-migration
[10:21] <Laney> it seems to be working ok, I'll turn it back on and we can unblock a few things modulo testing
[10:27] <LocutusOfBorg> I'll be happy to test it then :) thanks!
[10:32] -queuebot:#ubuntu-release- Unapproved: iio-sensor-proxy (focal-proposed/main) [2.8-1 => 2.8-1ubuntu1] (desktop-core)
[10:40] <Laney> juliank: https://paste.ubuntu.com/p/vcPRXVh67m/ any idea why this would have started happening and/or what to do about it?
[10:45] <juliank> Laney: nope
[10:46] <rbasak> There's some retry logic here: https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/lib/adtlog.py#L58
[10:46] <rbasak> Do you have that in your version?
[10:46] <rbasak> If so, maybe bump up the retry times?
[10:47] <Laney> https://git.launchpad.net/~ubuntu-release/autopkgtest/+git/development/tree/lib/adtlog.py#n58
[10:47] <Laney> that's our version (so, yeah)
[10:47] <rbasak> Seems odd for it to use non-blocking mode and then retry
[10:48]  * Laney channels past pitti
[10:49] <Laney> I never saw this on the previous (xenial) deployment though, feels like something which changed between then and focal
[10:54] <sil2100> Laney: switch to the new world?
[10:55] <Laney> yus
[10:57] <sil2100> Will get in touch with you in a bit!
[10:57] <Laney> ddstreet: when you get a chance can you check systemd upstream's webhooks to see if they are still working please? We just updated DNS for autopkgtest.ubuntu.com so it is now pointing to a new environment
[10:57] <Laney> so any dispatches from now-ish onwards
[10:57] <Laney> allowing for TTL I guess
[11:03] <juliank> Laney: exciting days
[11:04] <juliank> Laney: and lots of tests to give it a good start, huh?
[11:04] <juliank> :D
[11:13] <Laney> indeed
[11:14] <Laney> ubuntu-image upstream tests work so that's a good sign for systemd ones I guess
[11:14] <Laney> juliank: want to figure out this blocking thing though
[11:17] <sil2100> \o/
[11:50] <Laney> https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html results have the nice URLs now too oooooooh yeahhhhh
[11:58] -queuebot:#ubuntu-release- Unapproved: gcc-11 (impish-proposed/main) [11-20210424-1ubuntu1 => 11.1.0-1ubuntu1] (core, i386-whitelist)
[12:00] -queuebot:#ubuntu-release- Unapproved: accepted debootstrap [sync] (impish-proposed) [1.0.124]
[12:00] -queuebot:#ubuntu-release- Unapproved: accepted gcc-11 [source] (impish-proposed) [11.1.0-1ubuntu1]
[13:37]  * enyc meows
[13:37] <mdeslaur> hey SRU team, looks like bug 1868127 has been verification done for months yet it's not in -updates yet...could someone please take a look?
[13:37] <ubot3> Bug 1868127 in openvpn (Ubuntu Focal) "[SRU] OpenVPN will not reload due to misconfigured .service file" [Medium, Fix Committed] https://launchpad.net/bugs/1868127
[13:38] <enyc> "Archive: Closed" as per 21.04 ?  or not yet ready to accept 21.10 related?
[13:39] <mdeslaur> oh I guess https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1868127/comments/14 explains why it's not in -updates
[13:39] <sil2100> mdeslaur: hey! It looks block-proposed, so we're not touching it
[13:39] <ubot3> Launchpad bug 1868127 in openvpn (Ubuntu Focal) "[SRU] OpenVPN will not reload due to misconfigured .service file" [Medium, Fix Committed]
[13:39] <mdeslaur> I'll bundle it in my security update than
[13:39] <mdeslaur> sil2100: oh! just noticed xenial autopkgtests showed up, thanks!
[13:39] <mdeslaur> sil2100: yeah, that explains it still being in -proposed, thanks :)
[14:00] <doko> impish autopkg tests seem to work, the reddish color looks familiar ;)
[14:48] <sil2100> mdeslaur: yw! Just a heads up - I need to do some changes for security-britney now for the new ADT deployment, so don't worry if things don't quite work right now
[14:48] <mdeslaur> sure, thanks sil2100
[15:01] <Laney> OK armhf should be running properly now
[15:03] <Laney> why is the queue metric all jaggedy
[15:22] -queuebot:#ubuntu-release- Unapproved: pi-bluetooth (focal-proposed/multiverse) [0.1.10ubuntu6 => 0.1.15ubuntu0~20.04.1] (raspi)
[15:31] <Laney> not sure it is running properly :(
[15:31] <Laney> I'm seeing a lot of VirtSubproc.Timeout
[15:42] -queuebot:#ubuntu-release- Unapproved: pi-bluetooth (groovy-proposed/restricted) [0.1.15ubuntu1 => 0.1.15ubuntu1.1~20.10.1] (raspi)
[16:41] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (hirsute-proposed) [3.192.41]
[17:13] -queuebot:#ubuntu-release- Unapproved: update-notifier (hirsute-proposed/main) [3.192.40 => 3.192.40.1] (ubuntu-desktop, ubuntu-server)
[17:14] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (hirsute-proposed) [3.192.40.1]
[17:36] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (hirsute-proposed) [3.192.40.1]
[17:39] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (focal-proposed) [3.192.30.7]
[17:41] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (focal-proposed) [3.192.30.7]
[17:43] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (bionic-proposed) [3.192.1.10]
[17:43] <coreycb> hello SRU team, if anyone has cycles we'd like to see if we can get a review of python-ovsdbapp in the groovy and focal unapproved queues
[17:44] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (bionic-proposed) [3.192.1.10]
[17:47] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (xenial-proposed) [3.168.14]
[17:51] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (xenial-proposed) [3.168.14]
[18:17] -queuebot:#ubuntu-release- Unapproved: gcc-11-cross (impish-proposed/main) [3ubuntu5 => 4ubuntu1] (i386-whitelist, ubuntu-desktop)
[18:21] <bdmurray> coreycb: I can have a look
[18:21] <coreycb> bdmurray: thank you
[18:23] -queuebot:#ubuntu-release- Unapproved: gcc-11-cross-ports (impish-proposed/universe) [2ubuntu3 => 3ubuntu1] (i386-whitelist)
[18:24] -queuebot:#ubuntu-release- Unapproved: accepted python-ovsdbapp [source] (groovy-proposed) [1.5.0-0ubuntu2]
[18:25] -queuebot:#ubuntu-release- Unapproved: accepted python-ovsdbapp [source] (focal-proposed) [1.1.0-0ubuntu2]
[18:26] -queuebot:#ubuntu-release- Unapproved: accepted gcc-11-cross-ports [source] (impish-proposed) [3ubuntu1]
[18:26] -queuebot:#ubuntu-release- Unapproved: accepted gcc-11-cross [source] (impish-proposed) [4ubuntu1]
[18:34] -queuebot:#ubuntu-release- Unapproved: accepted murano-dashboard [source] (hirsute-proposed) [1:11.0.0-0ubuntu1.1]
[18:39] -queuebot:#ubuntu-release- Unapproved: neutron (bionic-proposed/main) [2:12.1.1-0ubuntu4 => 2:12.1.1-0ubuntu6] (openstack, ubuntu-server)
[18:40] -queuebot:#ubuntu-release- Unapproved: accepted gnome-desktop3 [source] (hirsute-proposed) [3.38.5-1ubuntu2~21.04.1]
[18:46] <falcojr> sil2100: "Looking at the cloud-init SRU - can someone do a quick test of hirsute? Since I see all other series are verified" Done! I believe cloud-init should be ready now
[18:50] <sil2100> \o/
[18:57] <ddstreet> Laney systemd-upstream ci tests seem like they're still running normally, so i assume the changeover worked fine
[19:08] -queuebot:#ubuntu-release- Unapproved: accepted lightdm [source] (groovy-proposed) [1.30.0-0ubuntu4~20.10.1]
[19:09] -queuebot:#ubuntu-release- Unapproved: accepted lightdm [source] (focal-proposed) [1.30.0-0ubuntu4~20.04.1]
[19:14] -queuebot:#ubuntu-release- Unapproved: accepted ovn [source] (groovy-proposed) [20.06.3-0ubuntu0.20.10.1]
[19:16] <bdmurray> JawnSmith: bug 1921915 is missing SRU information
[19:16] <ubot3> Bug 1921915 in pi-bluetooth (Ubuntu Groovy) "Bluetooth controller not detected on CM4" [Undecided, In Progress] https://launchpad.net/bugs/1921915
[19:21] <dbungert> blackboxsw: will the update notifier stuff be heading to impish also?  I have a crash fix pending LP: #1926298
[19:21] <ubot3> Launchpad bug 1926298 in update-notifier (Ubuntu) "Segfault added in the recent changes" [High, In Progress] https://launchpad.net/bugs/1926298
[19:23] <JawnSmith> Thanks bdmurray, will fix
[19:24] <bdmurray> dbungert: Its in the upstream branch for update-notifier, so if you put it there I can upload it for impish.
[19:24] <dbungert> bdmurray: let me rebase the patch and I'll report back
[19:41] <JawnSmith> bdmurray, fixed
[19:44] -queuebot:#ubuntu-release- Unapproved: rejected magnum [source] (groovy-proposed) [11.0.0-0ubuntu2]
[19:46] -queuebot:#ubuntu-release- Unapproved: rejected magnum [source] (groovy-proposed) [11.0.0-0ubuntu1.1]
[19:48] -queuebot:#ubuntu-release- Unapproved: magnum (groovy-proposed/universe) [11.0.0-0ubuntu1 => 11.0.0-0ubuntu1.1] (openstack)
[19:50] <bdmurray> JawnSmith: Where are bluez and linux-firmware-raspi2 for groovy? I don't see them in the queue now.
[19:53] <bdmurray> icey, coreycb: bug 19215734 is missing SRU information
[20:00] <JawnSmith> bdmurray: linux-firmware-raspi2 is awaiting a sponsor. LP: #1925971
[20:00] <ubot3> Launchpad bug 1925971 in linux-firmware-raspi2 (Ubuntu) "SRU bluetooth fixes and CVEs to focal and groovy" [Undecided, New] https://launchpad.net/bugs/1925971
[20:01] <JawnSmith> Fairly certain the bluez patch for groovy has already landed
[20:01] <JawnSmith> but I'll double check
[20:02] <bdmurray> I guess my real question is "does the new pi-bluetooth require a versioned package relationship to these other packages"?
[20:02] <JawnSmith> confirmed, bluez 5.55-0ubuntu1.1 in groovy has the relevant bluetooth fix
[20:04] <JawnSmith> They generally don't need to be updated together. When new Pi hardware comes out then they likely all need an update, as happened here
[20:05] <JawnSmith> But generally speaking there would be plenty of scenarios where only one of the three needs an update
[20:08] -queuebot:#ubuntu-release- Unapproved: accepted ovn [source] (focal-proposed) [20.03.2-0ubuntu0.20.04.1]
[20:24] <ddstreet> bdmurray do you happen to know what's going on with the update_excuses page detail for makedumpfile? it says that the makedumpfile autopkgtests for ppc failed, but looking at the autopkgtest test result list page, it has no output at all for the new version
[20:26] <vorlon> ddstreet: in focal?
[20:27] <ddstreet> sorry groovy
[20:27] <ddstreet> e.g. the tests are listed as some passing, ppc failing here https://people.canonical.com/~ubuntu-archive/proposed-migration/groovy/update_excuses.html
[20:27] <vorlon> hmm
[20:27] <ddstreet> but e.g. here it doesn't show any test at all for the new version https://autopkgtest.ubuntu.com/packages/makedumpfile/groovy/ppc64el
[20:27] <vorlon> GREAT QUESTIOQN
[20:29] <LocutusOfBorg> oops I triggered it manually some seconds ago
[20:29] <vorlon> so, I can say that updates of https://autopkgtest.ubuntu.com/packages and update_excuses are not synchronized
[20:29] <vorlon> but it's unusual that britney output would be updated first
[20:30] <vorlon> Laney: ^^ any possibility this is related to the new deployment?
[20:35] -queuebot:#ubuntu-release- Unapproved: accepted pi-bluetooth [source] (groovy-proposed) [0.1.15ubuntu1.1~20.10.1]
[20:36] <vorlon> ddstreet: anyway, it does link to the specific test log, which is newer than anything reported on https://autopkgtest.ubuntu.com/packages/m/makedumpfile/groovy/ppc64el - but also more than a day old.  So it looks like a failure to update the autopkgtest.ubuntu.com view, indeed
[20:49] -queuebot:#ubuntu-release- Unapproved: accepted heat-dashboard [source] (focal-proposed) [3.0.1-0ubuntu1]
[21:25] -queuebot:#ubuntu-release- Unapproved: accepted iio-sensor-proxy [source] (focal-proposed) [2.8-1ubuntu1]
[21:46] -queuebot:#ubuntu-release- Unapproved: glibc (focal-updates/main) [2.31-0ubuntu9.3 => 2.31-0ubuntu9.2] (core, i386-whitelist) (sync)
[21:47] -queuebot:#ubuntu-release- Unapproved: accepted glibc [sync] (focal-updates) [2.31-0ubuntu9.2]
[22:00] -queuebot:#ubuntu-release- Unapproved: rejected pi-bluetooth [source] (focal-proposed) [0.1.15ubuntu0~20.04.1]
[22:14] <bryce> bdmurray, heya, once a package is in -proposed on launchpad (i.e. https://launchpad.net/ubuntu/+source/update-notifier/3.168.14) how long does it typically take before it's available to install from the archive?
[22:15] <bdmurray> bryce: If I'm in a hurry I usually switch to archive.ubuntu.com instead of a local mirror
[22:15] <bryce> bdmurray, yeah that's what I'm pulling from
[22:15] <bryce>      3.168.13 500
[22:15] <bryce>         500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
[22:27] <bryce> bdmurray, guessing things are just bogged down with impish or something?
[22:27] <bdmurray> bryce: if you use the ip address for achive.ubuntu.com you'll see the latest package version
[22:28] <bdmurray> bryce: so maybe its some cache'ing thing
[22:28] <bryce> ahh
[22:30] <bryce> bdmurray, thanks that explains it
[23:54] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (impish-proposed/main) [26.2 => 27.0] (core)