[03:20] -queuebot:#ubuntu-release- New binary: rustc [s390x] (hirsute-proposed/universe) [1.44.1+dfsg1+llvm-3ubuntu1] (i386-whitelist)
[03:56] -queuebot:#ubuntu-release- New binary: rustc [i386] (hirsute-proposed/universe) [1.44.1+dfsg1+llvm-3ubuntu1] (i386-whitelist)
[04:04] -queuebot:#ubuntu-release- New binary: rustc [amd64] (hirsute-proposed/universe) [1.44.1+dfsg1+llvm-3ubuntu1] (i386-whitelist)
[04:07] -queuebot:#ubuntu-release- New binary: rustc [ppc64el] (hirsute-proposed/universe) [1.44.1+dfsg1+llvm-3ubuntu1] (i386-whitelist)
[05:24] -queuebot:#ubuntu-release- New binary: telepathy-haze [amd64] (hirsute-proposed/none) [0.8.0-3] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: telepathy-haze [ppc64el] (hirsute-proposed/none) [0.8.0-3] (no packageset)
[05:28] -queuebot:#ubuntu-release- New binary: telepathy-haze [arm64] (hirsute-proposed/universe) [0.8.0-3] (no packageset)
[05:29] -queuebot:#ubuntu-release- New binary: telepathy-haze [armhf] (hirsute-proposed/universe) [0.8.0-3] (no packageset)
[05:30] -queuebot:#ubuntu-release- New binary: telepathy-haze [s390x] (hirsute-proposed/universe) [0.8.0-3] (no packageset)
[05:41] -queuebot:#ubuntu-release- New binary: telepathy-haze [riscv64] (hirsute-proposed/universe) [0.8.0-3] (no packageset)
[06:13] <vorlon> https://autopkgtest.ubuntu.com/packages/r/rust-proc-macro2/hirsute/s390x ugh, '@', what a terrible name for a test
[07:36] -queuebot:#ubuntu-release- Unapproved: update-notifier (bionic-proposed/main) [3.192.1.8 => 3.192.1.9] (ubuntu-desktop, ubuntu-server)
[07:36] -queuebot:#ubuntu-release- Unapproved: update-notifier (groovy-proposed/main) [3.192.34 => 3.192.34.1] (ubuntu-desktop, ubuntu-server)
[07:36] -queuebot:#ubuntu-release- Unapproved: update-notifier (focal-proposed/main) [3.192.30.1 => 3.192.30.2] (ubuntu-desktop, ubuntu-server)
[07:36] -queuebot:#ubuntu-release- Unapproved: update-notifier (xenial-proposed/main) [3.168.11 => 3.168.12] (ubuntu-desktop, ubuntu-server)
[08:43] -queuebot:#ubuntu-release- New binary: rustc [armhf] (hirsute-proposed/universe) [1.44.1+dfsg1+llvm-3ubuntu1] (i386-whitelist)
[09:11] -queuebot:#ubuntu-release- Unapproved: borgbackup (xenial-proposed/universe) [1.0.12-0ubuntu1.16.04.1 => 1.0.13-0ubuntu1.16.04.1] (no packageset)
[09:13] -queuebot:#ubuntu-release- Unapproved: borgbackup (bionic-proposed/universe) [1.1.5-1 => 1.1.14-2ubuntu1.18.04.1] (no packageset)
[09:14] -queuebot:#ubuntu-release- Unapproved: borgbackup (focal-proposed/universe) [1.1.11-5 => 1.1.14-2ubuntu1.20.04.1] (no packageset)
[09:15] <LocutusOfBorg> they superseeds previous versions ^^ I added a testcase to the code to show regressions on the fixed bug
[10:02] -queuebot:#ubuntu-release- New binary: rustc [arm64] (hirsute-proposed/universe) [1.44.1+dfsg1+llvm-3ubuntu1] (i386-whitelist)
 vorlon, ahh, and now entangled with re2 and perl
[10:03] <doko> wake up, these are entangled from the start
[10:03] <doko> but there appears to be a britney bug that it is only shown now:
[10:03] <doko> Issues preventing migration:
[10:03] <doko> Implicit dependency: python3-defaults libsbml (not considered)
[10:04] <doko> this didn't show up before, only now
[10:21] <cpaelzer> doko: FYI I've seen a few more perl blocks and resolved former blocking autopkgtest of libpod-2-docbook-perl and netatalk (which blocked openldap which in turn blocked perl).
[10:21] <cpaelzer> Of these netatalk will stay broken (due to Debian changes in 3.1.12~ds-5), might need a test reset maybe?
[10:21] <cpaelzer> doko: sil2100: and thanks for the skip hint on postgresql-12!
[10:21] <cpaelzer> In addition the custom triggers I submitted yesterday also cut down the remaining issues from ~25 to 5 which leaves less of a bad feeling.
[10:23] <doko> cpaelzer: afk until Monday, please get in touch with vorlon and rbalint
[10:41] <RikMills> doko: I asked Laney about that excuses weirdness a few weeks ago. not sure if it is fixable IIRC
[10:42] <RikMills> https://irclogs.ubuntu.com/2020/11/09/%23ubuntu-release.html#t16:05
[10:48] <Laney> it depends what happened, someone would need to analyse the situation properly
[10:50] <Laney> btw, some proposed-migration improvements coming soon via Debian
[10:50] <Laney> improvements when adding extra triggers, don't pick ones already in the release pocket (thanks juliank)
[10:51] <Laney> don't queue tests for transitions until the rdep is installable again
[10:52] <Laney> that last one is still being reviewed
[10:56] <rbalint> cpaelzer, plusone i'm on unblocking perl
[10:57] <cpaelzer> rbalint: what is left actually? Only some autopkgtest on perl itself  think right - are you working on those?
[10:58] <rbalint> cpaelzer, and mariadb, which i'm filing a hint for
[10:58] <cpaelzer> +1 on that
[10:58] <rbalint> cpaelzer, LP: #1906628
[10:58] <cpaelzer> rbasak: ^^ FYI
[10:58] -queuebot:#ubuntu-release- Unapproved: backport-iwlwifi-dkms (focal-proposed/universe) [8324-0ubuntu3~20.04.1 => 8324-0ubuntu3~20.04.2] (no packageset)
[10:58] <rbalint> cpaelzer, it may need to be run on a big vm, i'm testing that
[10:59] <cpaelzer> I hope that https://release.debian.org/transitions/html/auto-openssl.html doesn't reach us before perl is over - that would be even more entanglement
[11:07] <rbalint> ubuntu-release could you please merge https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/394803 to let mariadb 10.5 in?
[11:08] <rbalint> cpaelzer,, if mariadb-10.5 migrates can we drop mariadb-10.3 from release?
[11:19] <cpaelzer> AFAIK yes, rbasak would be the expert to answer in case there is a hidden detail
[11:21] <rbalint> cpaelzer, thanks, then there is only a little left for perl, fingers crossed to get the custom triggered tests through quickly
[11:22] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (focal-proposed) [2.664.10]
[11:25] <cpaelzer> you have my crossed fingers as well ...
[11:25] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (focal-proposed/main) [2.664.8 => 2.664.10] (desktop-core, i386-whitelist)
[11:35] <rbalint> ubuntu-archive please act on LP: #1906640 to unblock perl
[11:38] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox [source] (groovy-proposed) [6.1.16-dfsg-4~ubuntu1.20.10.1]
[11:40] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-ext-pack [source] (groovy-proposed) [6.1.16-1~ubuntu1.20.10.1]
[11:44] <sil2100> rbalint: on it
[11:46] <doko> already done
[11:46] <rbalint> the hint is still left
[11:47] <Laney> The hint is wrong
[11:47] <Laney> It should be mariadb-10.3
[11:47] <Laney> rbalint:
[11:47] <rbalint> Laney, no, I'd like to let 10.5 in
[11:48] <Laney> I know
[11:48] <Laney> But you're resetting the wrong test.
[11:48] <Laney> autopkgtest for mariadb-10.3/1:10.3.25-0ubuntu1: amd64: Regression ♻ , arm64: Pass, armhf: Pass, i386: Ignored failure, ppc64el: Pass, s390x: Pass
[11:48] <rbalint> true, fixing
[11:48] <Laney> fwiw, this regression does reproduce for me, so this hint is only OK IMHO if mariadb-10.3 is going to be removed, so please check with rbalint
[11:48] <Laney> rbasak*
[11:50] <rbalint> Laney, you mean it is failing for you locally
[11:50] <rbalint> ?
[11:50] <Laney> yes
[11:50] <Laney> with 10.5 from proposed and it passes without that (release pocket only)(
[11:50] <Laney> same test failing as the log
[11:51] <Laney> but if 10.3 is going away, it's OK to not care I think
[11:51] <rbalint> Laney, how do you trigger it?
[11:52] <rbalint> Laney, just being curious, i'd like to have the hint :-)
[11:54] <rbalint> i've fixed the hint btw
[11:55] <Laney> autopkgtest --timeout-copy=6000 --shell-fail --apt-upgrade --apt-pocket=proposed=src:mariadb-10.5 mariadb-10.3 -- qemu --ram-size=1592 autopkgtest-hirsute-amd64.img
[11:56] <rbalint> Laney, thanks, trying to repro here
[11:56] <rbalint> Laney, i tried with even less ram, but it made more tests to fail
[11:58] <rbalint> Laney, according to cpaelzer 10.3 will go away with 10.5 migrating, but still waiting for rbasak's confirmation
[11:58] <Laney> ack
[12:13] <rbalint> Laney, passes with --ram-size=4096 fails with --ram-size=1592 here
[12:19] <rbalint> Laney, is it enough for the hint? rbasak may not be around to give his advice
[12:21] <rbalint> Laney, sil2100 https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/394808
[12:24] <Laney> rbalint: I get it, the tests come from mariadb-test-data and it's a new test with 10.5
[12:24] <Laney> big feels better
[12:24] <Laney> let's try that
[12:26]  * Laney adds to the right config file :p
[12:28] <rbalint> Laney, ok, retriggering the tests then
[12:28] <rbalint> Laney, could you please also add the hint?
[12:29] <rbalint> Laney, i don't want to miss the next britney run
[12:33] <RikMills> rbalint: mariadb-10.3 src is to be removed soon?
[12:33] <RikMills> oh, cpaelzer I mean. sorry
[12:34]  * RikMills will need to switch akoandi depends
[12:34] <cpaelzer> RikMills: well, the talk above was based on assumptions and we wanted to wait for rbasak to confirm/deny
[12:34] <cpaelzer> RikMills: also as you know "soon" can in those terms sometimes mean in 3 months
[12:35] <RikMills> indeed! lol
[12:35] <cpaelzer> and since I have no current insight into that transition it is hard to make a reliable statement
[12:35] <cpaelzer> rbalint: test wise mysql-8.0 (the closest sibling to mariadb) already has the big-package hint
[12:36] <cpaelzer> rbalint: that IMHO is another argument for hinting the bigtest for mariadb
[12:37] <Laney> rbalint: I'm watching it, I will make sure the next run sees the pass
[12:43] <Laney> rbalint: there you go, it passed before the previous one finished even
[12:51] <rbasak> o/
[12:51] <rbasak> Otto is planning a switch in mysql-defaults for 10.3->10.5 soon. It's already in VCS
[12:51] <rbasak> However I'm not sure when he's planning to remove 10.3.
[12:54] <LocutusOfBorg> looks like a perl package is failing, but maybe this is a launchpad sadness?
[12:54] <LocutusOfBorg> https://launchpadlibrarian.net/509667382/buildlog_ubuntu-hirsute-s390x.libcbor-xs-perl_1.82-1_BUILDING.txt.gz
[12:54] <LocutusOfBorg>     (result, consumed) = self._buffer_decode(data, self.errors, final)
[12:54] <LocutusOfBorg> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in position 36: invalid start byte
[12:55] <rbalint> LocutusOfBorg, saved the log and retried, let's see
[12:56] <LocutusOfBorg> rbalint, already retried, looks it failed
[12:56] <LocutusOfBorg> in any case, looks a lp issue, right?
[12:56] <rbasak> Looks like an invalid "this is valid UTF-8" assumption
[12:57] <rbasak> Then again, is something dumping non-UTF8 to the terminal? Unless the locale is configured that way, it probably shouldn't do that either.
[12:59] <rbalint> rbasak, lp should then convert the output
[13:18] <Laney> Buildd toolchain package versions: launchpad-buildd_191~460~ubuntu18.04.1
[13:18] <Laney> https://git.launchpad.net/launchpad-buildd/commit/?id=25d8b32caed56ba725c2b946b67f3b8622ece9d2
[13:18] <Laney> I think that commit is missing
[13:18] <Laney> cjwatson: ^- do s390x images need upgrading?
[13:19] <Laney> Looks like that fix is in 193
[13:19] <Laney> (do you want me to ask the help contact?)
[13:20]  * Laney does so
[13:22] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (groovy-proposed) [2:22.0.1-0ubuntu1]
[13:24] -queuebot:#ubuntu-release- Unapproved: rejected adduser [source] (groovy-proposed) [3.118ubuntu3]
[13:34] <Laney> #launchpad people are investigating
[13:38] -queuebot:#ubuntu-release- Unapproved: accepted rtl8812au [source] (focal-proposed) [4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.1]
[13:41] <rbalint> Laney, thanks!
[13:44] <Laney> apw: I'm seeing
[13:44] <Laney> awk: cmd. line:3: warning: command line argument `/home/ubuntu-archive/proposed-migration/var/data-b2/hirsute-proposed/Hints/kernel-testing-hints' is a directory: skipped
[13:44] <Laney> in britney logs
[13:44] <Laney> feels like a you thing :>
[13:48] <xnox> doko:  https://bugs.launchpad.net/ubuntu/+source/opensbi/+bug/1906668 should be fairly straight forward
[13:49] <doko> cpaelzer: ^^^
[13:52] <LocutusOfBorg> am I correct if I say that if we kick out graphviz 2.42.2-4build2 and restore 2.42.2-4build1 we can disentangle python and perl, and have python migrate?
[13:57] <xnox> doko:  https://bugs.launchpad.net/ubuntu/+source/usrmerge/+bug/1906671 for usrmerge
[13:58] <xnox> doko:  pinged sponsoree about adduser
[14:04] <LocutusOfBorg> can any ubuntu-archive please force-test-reset makedumpfile/1:1.6.8-1ubuntu1 ? it is already hinted, but the version increased
[14:05] <seb128> LocutusOfBorg, ubuntu-release you want, archive doesn't have access to hints
[14:05] <LocutusOfBorg> oops :/ sorry
[14:05] <LocutusOfBorg> maybe Laney can help here? :)
[14:06] <LocutusOfBorg> well, since I pinged ubuntu-archive, can anybody please have a look at graphviz to disentangle perl and python3-defaults?
[14:11] <doko> it is entangled, at multiple points, and I'm supposed to be afk
[14:14] -queuebot:#ubuntu-release- Unapproved: wireless-regdb (focal-proposed/main) [2018.05.09-0ubuntu1 => 2020.11.20-0ubuntu1~20.04.1] (core) (sync)
[14:14] -queuebot:#ubuntu-release- Unapproved: wireless-regdb (groovy-proposed/main) [2018.05.09-0ubuntu1 => 2020.11.20-0ubuntu1~20.10.1] (core) (sync)
[14:15] <Laney> LocutusOfBorg: can you do a merge proposal with the rationale? i'm just going to have lunch, you might make it easy enough for someone else to do
[14:15] <Laney> and indeed nack re: graphviz, that's not the only place
[14:15] <Laney> I think they're getting ready to be ready anyway
[14:15] -queuebot:#ubuntu-release- Unapproved: wireless-regdb (bionic-proposed/main) [2018.05.09-0ubuntu1~18.04.1 => 2020.11.20-0ubuntu1~18.04.1] (core) (sync)
[14:16] -queuebot:#ubuntu-release- Unapproved: wireless-regdb (xenial-proposed/main) [2018.05.09-0ubuntu1~16.04.1 => 2020.11.20-0ubuntu1~16.04.2] (core) (sync)
[14:17] <LocutusOfBorg> ack I still find difficult to parse the new update excuses (even if it is superior to the old one)
[14:20] -queuebot:#ubuntu-release- Unapproved: accepted wireless-regdb [sync] (groovy-proposed) [2020.11.20-0ubuntu1~20.10.1]
[14:21] -queuebot:#ubuntu-release- Unapproved: accepted wireless-regdb [sync] (focal-proposed) [2020.11.20-0ubuntu1~20.04.1]
[14:22] -queuebot:#ubuntu-release- Unapproved: accepted wireless-regdb [sync] (bionic-proposed) [2020.11.20-0ubuntu1~18.04.1]
[14:22] -queuebot:#ubuntu-release- Unapproved: accepted wireless-regdb [sync] (xenial-proposed) [2020.11.20-0ubuntu1~16.04.2]
[14:23] <apw> ^ these are all copies with binaries as they are destined for -security; pre-reviewed in the security compatible PPA
[14:36] -queuebot:#ubuntu-release- Unapproved: libevdev (groovy-proposed/main) [1.9.1+dfsg-1 => 1.9.1+dfsg-1ubuntu0.1] (core, i386-whitelist)
[14:38] <LocutusOfBorg> Laney, https://git.launchpad.net/~costamagnagianfranco/+git/hints-ubuntu/commit/?id=b081ba4bd635ef03867a9538ad2395d7e1f1cab1
[14:39] -queuebot:#ubuntu-release- Unapproved: libevdev (focal-proposed/main) [1.9.0+dfsg-1 => 1.9.0+dfsg-1ubuntu0.1] (desktop-core, i386-whitelist)
[14:40] <LocutusOfBorg> https://code.launchpad.net/~costamagnagianfranco/britney/+git/hints-ubuntu/+merge/394819
[14:40] <LocutusOfBorg> here we are ^^
[15:08] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle-5.4 [amd64] (bionic-proposed) [5.4.0-1031.33~18.04.1]
[15:20] <rbalint> Laney, could you please remove libcbor-xs-perl from -proposed to not hold back perl? the build did not get better yet
[15:20] <rbalint> maybe sil2100 ^?
[15:27] -queuebot:#ubuntu-release- Unapproved: libevdev (bionic-proposed/main) [1.5.8+dfsg-1 => 1.5.8+dfsg-1ubuntu0.1] (desktop-core)
[15:28] <sil2100> rbalint: just the one from proposed, right?
[15:28] <rbalint> sil2100, yes, i think that will be enough
[15:28] <rbalint> sil2100, thanks!
[15:29] <sil2100> Ah, FTBFS on s390x right now
[15:29] <sil2100> Ok
[15:33] <sil2100> rbalint: done o/
[15:36] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.8 [s390x] (focal-proposed/main) [5.8.0-32.34~20.04.1] (no packageset)
[15:37] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.8 [ppc64el] (focal-proposed/main) [5.8.0-32.34~20.04.1] (no packageset)
[15:37] <rbalint> plusone i've triggered all qtwebengine-opensource-src  tests for arm64 to speed up queueing them, it holds back re2
[15:37] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.8 [arm64] (focal-proposed/main) [5.8.0-32.34~20.04.1] (no packageset)
[15:38] -queuebot:#ubuntu-release- Unapproved: libinput (groovy-proposed/main) [1.16.2-1 => 1.16.2-1ubuntu0.1] (desktop-core, i386-whitelist)
[15:38] <rbalint> plusone clickhouse still needs to be resolved, looking
[15:39] -queuebot:#ubuntu-release- Unapproved: libinput (focal-proposed/main) [1.15.5-1ubuntu0.1 => 1.15.5-1ubuntu0.2] (desktop-core, i386-whitelist)
[15:40] -queuebot:#ubuntu-release- Unapproved: libinput (bionic-proposed/main) [1.10.4-1ubuntu0.18.04.1 => 1.10.4-1ubuntu0.18.04.2] (desktop-core)
[15:41] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.8 [amd64] (focal-proposed/main) [5.8.0-32.34~20.04.1] (no packageset)
[15:45] -queuebot:#ubuntu-release- New binary: linux-signed-dell300x [amd64] (bionic-proposed/universe) [4.15.0-1008.12] (no packageset)
[15:48] <Laney> rbalint: what is this "speed up queueing" that you're talking about?
[15:52] <rbalint> Laney, i triggered the tests manually since the arm64 package is built but tests were not queued
[15:52] <rbalint> Laney, like vorlon yesterday
[15:53] <Laney> how do you work out the list of tests to queue?
[15:54] <Laney> this results in double submissions, so I would really prefer not to get into the habit of doing this
[15:54] <rbalint> Laney, SELECT DISTINCT package from result JOIN test ON id = test_id WHERE triggers LIKE '%qtwebengine-opensource-src%' AND release LIKE 'hirsute';
[15:54] <Laney> (for results that aren't back by the next run)
[15:55] <rbalint> Laney, well, i don't do that as a hobby, just to migrate the entangled big transitions :-)
[15:56] <rbalint> plusone testing the clickhouse fix locally, will upload if it is enough
[15:58] <Laney> I'm sure you don't, but I don't want people getting into weird habits that waste resources, like bouncing on rmadison and then triggering tests in order to get their stuff in "fast"
[16:01] -queuebot:#ubuntu-release- Unapproved: apport (groovy-proposed/main) [2.20.11-0ubuntu50.2 => 2.20.11-0ubuntu50.3] (core, i386-whitelist)
[16:02] <rbalint> Laney, the 'waste' is below 1.0 USD: SELECT package, round(avg(duration/60)) from result JOIN test ON id = test_id WHERE triggers LIKE '%qtwebengine-opensource-src%' AND release LIKE 'hirsute' and arch = 'arm64' GROUP BY package;
[16:08] <Laney> rbalint: Come on, please :(
[16:09] <rbalint> Laney, it just try to keep in mind what costs i should ignore
[16:14] <Laney> If it's really so slow that you feel the need to resort to hacks then we should schedule working on some speedups, like having proposed-migration use the results from the sqlite database instead of going to swift each time
[16:19] <Laney> Regarding libcbor-xs-perl, don't we need to restore 1.71-1build2?
[16:34] <LocutusOfBorg> yep we need that
[16:34] <LocutusOfBorg> vorlon, btw, if you have some seconds of free time... missing build on i386: libusrsctp-dev, libusrsctp-examples, libusrsctp1 (from 0.9.3.0+20200422-1)
[16:38] <blackboxsw> rbasak:  I think update-notifier upload has now been queued for review into -proposed for X, B, F and G https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=update-notifier
[16:38] <rbasak> Thanks
[16:39] <blackboxsw> rbasak: X and B contain additional commits to fix pep8/pyflakes issues that were introduced in the previously rejected SRU
[16:39] <LocutusOfBorg> mmm Laney looks like copying libcbor-xs-perl nmight fail
[16:39] <LocutusOfBorg> ./copy-package --from=ubuntu --to=ubuntu --from-suite=hirsute-proposed --to-suite=hirsute-proposed --include-binaries libcbor-xs-perl --version 1.71-1build2 --force-same-destination
[16:40] <LocutusOfBorg> this commands wants to copy only s390x binaries... ?
[16:40] <Laney> try it, apparently that list of binaries can be wrong for reasons I don't understand
[16:40] <LocutusOfBorg> done :)
[16:40] <RikMills> vorlon: I am looking at kbibtex. at the moment waiting to see if the debian uploader really wants to build with optional QtWebengine without bothering to make the build dep architecture specific. plus pondering if the failing test is really useful, given that it never passes in debian, and when it fails in ubuntu it has not actually done a sane job of testing what it is intended to (that the apps GUI runs)
[16:40] <vorlon> removed clickhouse from release pocket, which is the last blocker for perl+python+re2 currently shown on update_excuses
[16:40] <LocutusOfBorg> yay looks like it worked
[16:41] <Laney> worked afaics
[16:41] <Laney> woot
[16:41] <vorlon> unfortunately, after the britney merge it seems update_excuses is much less reliable than update_output used to be in showing all the blockers
[16:41] <vorlon> RikMills: ok
[16:42] <Laney> help would be appreciated in getting it more reliable :-)
[16:42] <vorlon> LocutusOfBorg: should just need someone to do a binary copy of that same version back to hirsute-proposed to trigger the i386 build
[16:42] <Laney> even identifying classes of problems, ideally in the form of testcases, would be a good first step
[16:43] <LocutusOfBorg> vorlon, can I do that?
[16:43] <blackboxsw> rbasak: bugs related xenial and bionic are LP: #1906436, LP: #1901627, LP: #1822340, LP: #1842508 and LP: #1881632 F and G releases have a subset of those bugs
[16:44] <vorlon> LocutusOfBorg: I believe any uploader can
[16:47] <vorlon> Laney: honestly, I'd rather go back to the previous behavior where we could use update_output to trace these things, by having britney not block them for consideration when it detects that related packages are not migratable
[16:49] <vorlon> Laney: the latest issue I've seen was that openscap wasn't shown as entangling perl and python until today - even though it's been in the archive since the 19th of November.  So britney seems to truncate its search once it finds *a* blocker, which seriously impairs parallelization
[16:49] <vorlon> (parallelization of work by developers)
[17:01] <Laney> I think the way we decide to write "(not considered)" is a bit buggy but I didn't manage to comprehend the problem when I looked the other week
[17:03] <Laney> We could make the notest runs have the ImplicitDependencyPolicy be non blocking, I don't think I'd contend that one
[17:03] <Laney> Less sure about doing it universally
[17:05] <vorlon> that would be an improvement, at least
[17:06] <Laney> http://autopkgtest.ubuntu.com/packages/baconqrcode/hirsute/ppc64el
[17:06] <Laney> What on earth has happened there
[17:07] <vorlon> the runners really like their bacon
[17:07] <rbalint> Laney, this was not me :-)
[17:10] <Laney>  php-bacon-qr-code | 2.0.2-2 | hirsute/universe          | all
[17:10] <Laney>  php-bacon-qr-code | 2.0.3-1 | hirsute-proposed/universe | amd64
[17:10] <Laney> something to do with this I'd say
[17:11] <vorlon> wtf
[17:12] <vorlon> well, should probably just force the package through regardless
[17:15] <Laney> yeah, I added a skiptest
[17:18] <vorlon> ah ok - I just added a force-reset-test, since the binary is now only available on amd64 and I wasn't sure if we would see future attempts to test on the archs where it will shortly no longer exist
[17:18] <Laney> I was thinking it'll clear itself up once in the release pocket (hopefully)
[17:18] <Laney> heh
[17:19] <Laney> shortest lived hint ever - assumed that reset-test was someone's previous attempt to get this to migrate, sorry
[17:22] <vorlon> Laney: ah :)
[17:24] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (focal-proposed) [2.664.10]
[17:42] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.8 [amd64] (focal-proposed) [5.8.0-32.34~20.04.1]
[17:42] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.8 [ppc64el] (focal-proposed) [5.8.0-32.34~20.04.1]
[17:42] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.8 [arm64] (focal-proposed) [5.8.0-32.34~20.04.1]
[17:42] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.8 [s390x] (focal-proposed) [5.8.0-32.34~20.04.1]
[17:43] -queuebot:#ubuntu-release- New: accepted linux-signed-dell300x [amd64] (bionic-proposed) [4.15.0-1008.12]
[17:46] <LocutusOfBorg> vorlon, I don't think the copy worked
[17:46] <LocutusOfBorg> ./copy-package --from=ubuntu --to=ubuntu --from-suite=hirsute-proposed --to-suite=hirsute-proposed --include-binaries libusrsctp  --force-same-destination
[18:01] <kyrofa> How much RAM do the builder VMs have for the archive? I need to try and duplicate an error
[18:17] <LocutusOfBorg> kyrofa, does this help? https://launchpad.net/ubuntu/+source/procenv/0.50-1ubuntu3
[18:17] <LocutusOfBorg> hint: look inside each build log
[18:20] -queuebot:#ubuntu-release- Unapproved: apport (focal-proposed/main) [2.20.11-0ubuntu27.13 => 2.20.11-0ubuntu27.14] (core, i386-whitelist)
[18:25] <kyrofa> LocutusOfBorg, yeah handy, thanks!
[18:25] <LocutusOfBorg> you have to thank Colin, who give me that hint around 5 years ago :)
[18:26] <LocutusOfBorg> I'm just a dumb copy-paste man :)
[18:26] <kyrofa> Haha, you're in good company
[18:40]  * enyc meows
[19:23] <vorlon> LocutusOfBorg: didn't work> did you get an error?
[19:24] <LocutusOfBorg> no error
[19:24] <xnox> did it do what you wanted, or did it not?
[19:24] <vorlon> LocutusOfBorg: error email?
[19:24] <vorlon> (since copies are asynchronous)
[19:25] <vorlon> I've just tried as well with 'copy-package -b -e 0.9.3.0+20201102-2 libusrsctp --force-same-destination -s hirsute-proposed --auto-approve -y', I don't see a build record so waiting to see if I get an email
[19:25] <LocutusOfBorg> nope, no error I guess
[19:25] <LocutusOfBorg> no email I mean
[19:25] <LocutusOfBorg> but lots of lp goes into spam
[19:27] <vorlon> hmm the copy probably worked, but somehow the package is not in the packageset despite showing in germinate output
[19:27] <vorlon> digging
[19:29] <vorlon> oh I was looking at the focal germinate output :/  ok we should just remove these binaries from the release pocket, I'll follow throug
[19:31] <doko> Laney: autopkgtest for libcalendar-simple-perl/1.23-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Ignored failure, ppc64el: Regression ♻ , s390x: Regression ♻
[19:31] <doko> triggerd by perl, however that didn't show up earlier, and there doesn't seem to be any cycle involved
[19:35] <rbalint> doko, passing locally, i already retried them, but indeed, those did not show up for some reason
[19:35] <LocutusOfBorg> doko, it was failing since the begin
[19:35] <LocutusOfBorg> then a new version succeded and it migrated
[19:35] <LocutusOfBorg> so they are now seen as failures?
[19:36] <rbalint> LocutusOfBorg, that could be the explanation
[19:36] <LocutusOfBorg> it migrated 2 hours ago, the libcalendar-simple-perl
[19:36] <LocutusOfBorg> well, 4 hours ago
[19:37] <LocutusOfBorg> with the latest autosyncs and migrations, we lost something again in transitions
[19:37] <LocutusOfBorg> e.g. borgbackup has been syncd, but it should be fast
[19:37] <Eickmeyer[m]> Ok, I need some help. teward and I just reuploaded agordejo, which just completely FTBFS. In my PPA, it build perfectly just 40 minutes prior. What gives? https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=hirsute
[19:40] <LocutusOfBorg> Eickmeyer[m], looks like you are lying :D
[19:40] <Eickmeyer[m]> LocutusOfBorg: ?
[19:40] <LocutusOfBorg> your ppa is lying :)
[19:41] <LocutusOfBorg> hint: looks like you configured the ppa to use only release pocket and not proposed?
[19:41] <LocutusOfBorg> this is what I get with meld of both build logs, there is even no python3.9 in your ppa build :p
[19:42] <Eickmeyer[m]> LocutusOfBorg: Ok, that makes sense. However, the reupload was to set the python compatibility variable which should take care of the 3.9 issue.
[19:42] <LocutusOfBorg> this is another issue then :)
[19:42] <Eickmeyer[m]> Indeed. Upstream was notified, but has made zero action on it.
[19:43] <LocutusOfBorg> are you sure PYTHONCOMPATVERSIONVERSION is a valid keyword?
[19:44] <Eickmeyer[m]> LocutusOfBorg: According to the docs, yes. https://www.python.org/dev/peps/pep-0606/#python-3-8
[19:45] <Eickmeyer[m]> Unless they typo'd the living junk out of it.
[19:46] <LocutusOfBorg> googling for it failed
[19:47] <Eickmeyer[m]> LocutusOfBorg: Specifically: https://www.python.org/dev/peps/pep-0606/#command-line
[19:51] -queuebot:#ubuntu-release- Unapproved: apport (xenial-proposed/main) [2.20.1-0ubuntu2.27 => 2.20.1-0ubuntu2.28] (core)
[19:52] -queuebot:#ubuntu-release- Unapproved: apport (bionic-proposed/main) [2.20.9-0ubuntu7.20 => 2.20.9-0ubuntu7.21] (core)
[19:54] <vorlon> LocutusOfBorg: yes, the autopkgtest policy is not good at detecting the difference between progressions and regressions
[19:54] <vorlon> a fix would be to notice that the version of the succeeding autopkgtest is higher than the failing one and should be ignored
[19:54] <LocutusOfBorg> or automatic retry?
[19:55] <vorlon> or that
[19:55] <LocutusOfBorg> I prefer more green rather than more yellow/red :)
[19:55] <LocutusOfBorg> but yes, looks like a good fix
[19:55] <vorlon> I prefer faster migrations without regressing ;)
[19:56] <LocutusOfBorg> I did the same retry in node-mqtt just today, passed from red to green and triggering regressions everywhere
[19:57] <vorlon> LocutusOfBorg: did you retry mariadb-10.5 for perl only on ppc64el? there are failures also on armhf and s390x
[19:58] <LocutusOfBorg> vorlon, I didn't
[19:59] <vorlon> LocutusOfBorg: didn't which?  I do see a running mariadb-10.5/ppc64el test with your name on it
[19:59] <LocutusOfBorg> yes, but I tried also armhf and s390x
[20:00] <vorlon> oh ok
[20:00] <vorlon> I don't see them running or in the queue, did they fail fast? :/
[20:01] <LocutusOfBorg> maybe they just finished...
[20:01] <LocutusOfBorg> not sure it was around half an hour ago
[20:01] <vorlon> a successful test takes ~40m and the timestamp on the test didn't look old enough
[20:02] <vorlon> ... and ppc64el just disappeared after running < 10m so it looks like they're probably all failures and we'll have logs to look at soon
[20:03] <LocutusOfBorg> I think mariadb is having some sadness
[20:03] <LocutusOfBorg> migrating mariadb-common/1:10.3.27-1~exp1/amd64 to testing makes mariadb-client-core-10.5/1:10.5.8-3/amd64 uninstallable
[20:03] <LocutusOfBorg> meh, -dev packages not ship anymore
[20:09] <LocutusOfBorg> sure now that there is an higher mariadb-common in hirsute (from 10.5), the 10.3 can't migrate anymore
[20:09] <LocutusOfBorg> :/
[20:26] <LocutusOfBorg> I uploaded what I think can be a fix
[20:27] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (groovy-proposed/main) [5.8.0-1014.15] (core, kernel)
[20:28] -queuebot:#ubuntu-release- New binary: linux-signed-kvm [amd64] (groovy-proposed/main) [5.8.0-1012.13] (core)
[20:40] <LocutusOfBorg> I'm doing rebuilds so we can kick out 10.3
[20:40] <vorlon> LocutusOfBorg: I see you've dropped mariadb-common from mariadb-10.3; but there are several other binaries from mariadb-10.3 which are older in -proposed than the versions in release pocket... (mariadb-server, mariadb-client)
[20:41] <LocutusOfBorg> vorlon, I think we should just rebuild reverse deps and move to 10.5
[20:41] <vorlon> s/several/two/ :)
[20:41] <LocutusOfBorg> not only two...
[20:41] <LocutusOfBorg> https://launchpadlibrarian.net/509718099/upload_20361202_log.txt
[20:41] <vorlon> ah
[20:42] <LocutusOfBorg> reverse deps are  ~5 packages
[20:42] <LocutusOfBorg> lets rebuild and move forward
[20:42] <vorlon> rebuilds sound good, but how quickly will that help us get the mariadb-10.5 autopkgtest failures cleared
[20:42] <mwhudson> ubuntu-archive can someone let https://launchpad.net/ubuntu/+source/rustc/1.44.1+dfsg1+llvm-3ubuntu1 out of NEW pls
[20:43] <vorlon> would removing mariadb-10.3 from -proposed now help?
[20:43] <LocutusOfBorg> vorlon, it won't help
[20:43] <LocutusOfBorg> binaries are already in release
[20:43] <LocutusOfBorg> the ones from mariadb-10.5
[20:43] <vorlon> mwhudson: done
[20:43] <mwhudson> vorlon: thanks!
[20:43] <LocutusOfBorg> so, removing mariadb-10.3 is the best way to move forward
[20:43] <Laney> doesn't 10.5 have passes with the longer set of triggers anyway? won't the next run get those?
[20:44] <vorlon> Laney: the retries are failing before getting to the actual tests
[20:44] <Laney> in https://autopkgtest.ubuntu.com/packages/m/mariadb-10.5/hirsute/armhf
[20:44] -queuebot:#ubuntu-release- New: accepted rustc [amd64] (hirsute-proposed) [1.44.1+dfsg1+llvm-3ubuntu1]
[20:44] -queuebot:#ubuntu-release- New: accepted rustc [armhf] (hirsute-proposed) [1.44.1+dfsg1+llvm-3ubuntu1]
[20:44] -queuebot:#ubuntu-release- New: accepted rustc [ppc64el] (hirsute-proposed) [1.44.1+dfsg1+llvm-3ubuntu1]
[20:44] -queuebot:#ubuntu-release- New: accepted rustc [arm64] (hirsute-proposed) [1.44.1+dfsg1+llvm-3ubuntu1]
[20:44] -queuebot:#ubuntu-release- New: accepted rustc [s390x] (hirsute-proposed) [1.44.1+dfsg1+llvm-3ubuntu1]
[20:44] -queuebot:#ubuntu-release- New: accepted rustc [i386] (hirsute-proposed) [1.44.1+dfsg1+llvm-3ubuntu1]
[20:44] <Laney> the second result there has a perl/5.32.
[20:44] <Laney> 0-5 trigger
[20:45] <vorlon> LocutusOfBorg: I don't see why the mariadb-10.5 binaries being in release would cause the mariadb-10.5 autopkgtest to fail
[20:46] <doko> Laney: well, now it has a valid test (even three or four), but the 	2020-11-18 failure was never shown
[20:46] <vorlon> doko: because failures that are not regressions are not being shown on update_excuses output anymore, to make the page more manageable
[20:47] <vorlon> so it was never shown, until a progression caused britney to start considering it a regression
[20:47] <Laney> Right, it became a 'regression' when it migrated
[20:47] <Laney> At that point we should have requested a new test
[20:47] <doko> huh? what migrated?
[20:47] <Laney> because the migration could then cause *that* package to regress
[20:48] <doko> neither perl nor libcalendar-simple-perl migrated
[20:48] <vorlon> it doesn't depend on migration though; britney will consider it a regression as soon as a newer version of the package under test, present in -proposed, has passed
[20:48] <doko> there *is no newer version*
[20:49] <LocutusOfBorg>  2.0.0-1	release (universe)	5 hours ago
[20:49] <LocutusOfBorg> doko, ^^
[20:51] <doko> yes, and it takes >=5h for britney to show :-(
[20:52] <vorlon> yes; but in any case the autopkgtest log history shows up sooner and you can see the failed test triggered by perl was an older version than the current version
[20:55] <doko> no, balint's explicit trigger is 18:58:46, update_excuses was started 18:23:17, so you can't see it
[20:56] <doko> and yes, I looked before retrying
[20:58] <doko> Eickmeyer[m]: please stop using 3.8 ... http://launchpadlibrarian.net/509709488/agordejo_0.1.1-0ubuntu2_0.1.1-0ubuntu3.diff.gz
[20:59] <vorlon> LocutusOfBorg: I've removed mariadb-10.3 from -proposed and will retry the autopkgtests after the publisher runs
[20:59] <LocutusOfBorg> ack vorlon
[20:59] <LocutusOfBorg> I finished rebuilds so hopefully you will be able to remove 10.3 from release too?
[21:00] <teward> LocutusOfBorg: Eickmeyer[m]: even with Proposed working, while this builds *fine* in a schroot build by sbuild for hirsute with the proper -X argument to Python, it seems that something in the version of nuitka being called upon in -proposed explodes hard.  Which suggests the underlying problem is actually not in the agordejo package at all but the nuitka compatibility with Py3.9, regressions, and compatibility strings not being parsed
[21:00] <teward> so at the moment -0ubuntu3 needs to be pulled from proposed
[21:00] <teward> doko: ^
[21:00] <doko> it's harmless there, it ftbfs
[21:00] <teward> until such time that upstream and nuitka that's being used under the hood is fixed
[21:00] <teward> doko: it'll stay FTBFS until nuitka fixes their crap
[21:01] <teward> ten bucks says the underlying build env isn't 3.9 compatible yet ;)
[21:02] <teward> or agordejo upstream is not parsing version strings right
[21:06] <teward> ... nope, FTBFS is in nuitka
[21:06] <teward> so it's a nuitka needs to support Python 3.9 issue (because they actually CHECK supported version strings)
[21:57] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (groovy-proposed) [5.8.0-1014.15]
[21:57] -queuebot:#ubuntu-release- New: accepted linux-signed-kvm [amd64] (groovy-proposed) [5.8.0-1012.13]
[22:05] <cjwatson> Eickmeyer[m]: It says just PYTHONCOMPATVERSION further up the PEP, so that seems like a typo.  However, if you look at the top, that's a rejected PEP, and there's no match for PYTHONCOMPAT in the actual Python 3.9 codebase.
[22:06] <Eickmeyer[m]> cjwatson: See teward 's explanation.
[22:06] <cjwatson> Yes, I saw that too, just wanted to close the loop.
[22:08] <teward> didn't notice that was a rejected PEP, my brain hurts xD  Regardless, nuitka needs to fix their stuff ;)
[22:08] <mwhudson> packages that require a source-changing upload for each new python version are the best
[22:08] <teward> mwhudson: well, this is going to require their underlying builder to be fixed heh.  nuitka is a python builder framework, and... well it's broke :P
[22:09] <bdmurray> vorlon: Could you fully phase bluez? The package has stopped phasing due to the apport change which started reporting bluetoothd crashes so all the "regressions" are just bluetoothd noise.
[22:11] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (groovy-proposed/multiverse) [6.1.16-dfsg-1ubuntu1.20.10.1 => 6.1.16-dfsg-4ubuntu1.20.04.1] (no packageset)
[22:11]  * cjwatson wonders why this thing absolutely *requires* nuitka rather than being able to fall back to using the interpreter like everything else
[22:12] <LocutusOfBorg> please reject this virtualbox-hwe ^^
[22:14] <vorlon> bdmurray: which release?
[22:14] <vorlon> bdmurray: looks like groovy
[22:17] <vorlon> bdmurray: (done)
[22:20] <bdmurray> vorlon: yes groovy, thanks
[22:21] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox-hwe [source] (groovy-proposed) [6.1.16-dfsg-4ubuntu1.20.04.1]
[22:37] <Laney> proposed-migration did find that test result I mentioned in this run, fwiw
[22:38] <Laney> (perl -> mariadb-10.5/ppc64el)
[22:39] <Laney> at least afaics from my phone :>
[22:39] <mruffell> ubuntu-archive: I seem to have caused a regression in the recent adcli SRU for Bionic. Regression bug: https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1906627 SRU bug: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703, can I get some help removing the package from -security and stopping phasing to -updates
[22:39] <mruffell> I am investigating the failure now
[22:40] <mruffell> sssd is not affected, seems to be a problem with the default change to GSS-SPNEGO from GSS-API in adcli
[22:41] <LocutusOfBorg> thanks
[22:43] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (groovy-proposed/multiverse) [6.1.16-dfsg-1ubuntu1.20.10.1 => 6.1.16-dfsg-4ubuntu1.20.10.3] (no packageset)
[22:45] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (focal-proposed/multiverse) [6.1.10-dfsg-1~ubuntu1.20.04.1 => 6.1.16-dfsg-4ubuntu1.20.04.1] (no packageset)
[22:48] -queuebot:#ubuntu-release- Unapproved: virtualbox (focal-proposed/multiverse) [6.1.10-dfsg-1~ubuntu1.20.04.1 => 6.1.16-dfsg-4~ubuntu1.20.04.1] (ubuntu-cloud)
[22:49] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1104.115] (kernel)
[22:49] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-127.130~16.04.1] (kernel)
[22:49] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1101.112~16.04.1] (kernel)
[22:50] -queuebot:#ubuntu-release- New binary: linux-signed-azure-4.15 [amd64] (bionic-proposed/main) [4.15.0-1101.112] (no packageset)
[22:50] -queuebot:#ubuntu-release- New binary: linux-signed-oem-5.10 [amd64] (focal-proposed/universe) [5.10.0-1006.7] (no packageset)
[22:50] -queuebot:#ubuntu-release- New binary: linux-signed-gke-4.15 [amd64] (bionic-proposed/main) [4.15.0-1075.80] (no packageset)
[22:50] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-127.130~16.04.1] (kernel)
[23:07] <vorlon> rolling back borgbackup, which has reset python3-defaults as a candidate >_<
[23:09] <vorlon> I am going to disable autosyncs for a bit, too many packages entangled to keep playing whack-a-mole especially with the current britney runtimes
[23:09] <LocutusOfBorg> the tests for borgbackup should be already finished
[23:09] <vorlon> LocutusOfBorg: yes and 3 of them failed
[23:10] <LocutusOfBorg> oh... :/
[23:10] <vorlon> so I'm not letting that crap block
[23:10] <LocutusOfBorg> flaky tests are flaky
[23:11] <LocutusOfBorg> I had to upload a new virtualbox-hwe because the groovy upload otherwise can't be versioned properly
[23:11] <LocutusOfBorg> if you are in a hurry with the transition please rollback it too
[23:12] <vorlon> I don't see virtualbox-hwe was previously in -proposed and tied to the transitions, so shouldn't reset things?
[23:23] -queuebot:#ubuntu-release- New binary: libavif [ppc64el] (hirsute-proposed/universe) [0.8.4-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- Unapproved: update-notifier (focal-proposed/main) [3.192.30.1 => 3.192.30.2] (ubuntu-desktop, ubuntu-server)
[23:28] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (focal-proposed) [3.192.30.2]
[23:28] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (focal-proposed) [3.192.30.2]
[23:31] -queuebot:#ubuntu-release- New binary: golang-pault-go-ykpiv [ppc64el] (hirsute-proposed/universe) [1.3.4-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: libavif [s390x] (hirsute-proposed/universe) [0.8.4-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: libavif [amd64] (hirsute-proposed/universe) [0.8.4-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: golang-pault-go-ykpiv [amd64] (hirsute-proposed/universe) [1.3.4-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: libavif [riscv64] (hirsute-proposed/universe) [0.8.4-1] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: golang-pault-go-ykpiv [riscv64] (hirsute-proposed/universe) [1.3.4-1] (no packageset)
[23:41] -queuebot:#ubuntu-release- New binary: linux-signed-gkeop-5.4 [amd64] (bionic-proposed/main) [5.4.0-1006.7~18.04.1] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: golang-pault-go-ykpiv [s390x] (hirsute-proposed/universe) [1.3.4-1] (no packageset)
[23:43] -queuebot:#ubuntu-release- New binary: linux-signed-gkeop [amd64] (focal-proposed/universe) [5.4.0-1006.7] (no packageset)
[23:44] -queuebot:#ubuntu-release- New binary: libavif [arm64] (hirsute-proposed/universe) [0.8.4-1] (no packageset)
[23:44] -queuebot:#ubuntu-release- New binary: libavif [armhf] (hirsute-proposed/universe) [0.8.4-1] (no packageset)
[23:47] <mwhudson> anyone remember why we still build rustc and cargo on i386?
[23:48] <mwhudson> because uggh https://launchpad.net/~mwhudson/+archive/ubuntu/cargo-testing/+build/20361433
[23:48]  * mwhudson needs food before that makes any sense