[08:08] <seb128> hum, quite some desktop i386 autopkgtest unhappy due to
[08:08] <seb128> Processing triggers for libc-bin (2.31-0ubuntu10) ...
[08:08] <seb128> E: Could not configure 'libc6:i386'.
[08:08] <seb128> E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
[08:08] <seb128> is that a known issue/something being worked on?
[08:08] <seb128> doko, ^ you might know?
[08:08] <Unit193> Silly seb, i386 doesn't exist!
[08:08]  * Unit193 ducks.
[08:09] <seb128> oh, of course! :p
[08:09] <Unit193> Sorry, I'm only useful every other day. :)
[08:10] <seb128> that's fine, I will queue a question for tomorrow then :p
[12:03] <xnox> seb128:  although one is installing special packages, they are of the other arch, thus shouldn't actually try to require immediate configuration.
[12:23] <ahasenack> good morning
[12:28] <ahasenack> hm, so excuses for python-certbot 1.6.0-1 is saying "missing build" (https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python-certbot), but 1.6.0-1 built just fine 15h ago: https://launchpad.net/ubuntu/+source/python-certbot/1.6.0-1/+build/19561482
[12:28] <ahasenack> oh
[12:28] <ahasenack> it helps when I reload the excuses page
[12:42] <seb128> xnox, shouldn't, but yet https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/i386/a/at-spi2-atk/20200709_021603_3c926@/log.gz (and the other glib rdepends on the team report)
[12:42] <oSoMoN> can a MOTU please retry the node-body-parser tests with the correct triggers?
[12:42] <oSoMoN> http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=amd64&package=node-body-parser&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[12:42] <oSoMoN> http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=arm64&package=node-body-parser&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[12:42] <oSoMoN> http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=armhf&package=node-body-parser&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[12:42] <oSoMoN> http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=ppc64el&package=node-body-parser&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[12:42] <oSoMoN> http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=s390x&package=node-body-parser&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[13:18] <kanashiro> hey, what would be the correct version string for a bionic SRU if in bionic we have 1.4.9-1build3 and in focal 1.4.9-1build5?
[13:21] <rafaeldtinoco> oSoMoN: doing
[13:21] <oSoMoN> thanks!
[13:22] <rafaeldtinoco> all done ;) you're welcome
[13:25] <ahasenack> rbasak: hi, ok to import a new package manually following those instructions?
[13:25] <ahasenack> on the usual host?
[13:26] <rbasak> ahasenack: yes. I intend to move to the new host very soon (today or tomorrow maybe) but working on something else right now
[13:28] <ahasenack> k
[13:29] <ahasenack> oh, turns out this one is already imported, I typoed when checking
[15:45] <oSoMoN> I fixed the node-buffer-shims failing autopkgtests at https://salsa.debian.org/js-team/node-buffer-shims/-/merge_requests/1, can a MOTU please sponsor https://people.canonical.com/~osomon/+1maintenance/node-buffer-shims.debdiff in the meantime?
[15:49] <oSoMoN> also, can someone please retry http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=ppc64el&package=node-chokidar&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1 ? it looks flaky to me
[15:53] <oSoMoN> similarly for http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=arm64&package=node-clean-css&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1
[16:01] <oSoMoN> the node-client-sessions tests are failing because they need a node-iconv rebuilt against the new nodejs, can someone trigger these tests with the additional trigger:
[16:01] <oSoMoN> http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=amd64&package=node-client-sessions&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[16:01] <oSoMoN> http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=arm64&package=node-client-sessions&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[16:01] <oSoMoN> http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=ppc64el&package=node-client-sessions&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[16:01] <oSoMoN> http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=s390x&package=node-client-sessions&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[16:02] <oSoMoN> (sorry for spamming with these requests, it's only the beginning, as there are many test failures in nodejs rdeps…)
[16:04] <oSoMoN> node-concat-map/armhf needs triggering again: http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=armhf&package=node-concat-map&trigger=nodejs/12.18.1%7Edfsg-1ubuntu1
[16:06] <oSoMoN> here we go again, node-cors needs an additional node-iconv trigger:
[16:06] <oSoMoN> https://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=amd64&package=node-cors&trigger=nodejs%2F12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[16:06] <oSoMoN> https://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=arm64&package=node-cors&trigger=nodejs%2F12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[16:06] <oSoMoN> https://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=armhf&package=node-cors&trigger=nodejs%2F12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[16:06] <oSoMoN> https://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=ppc64el&package=node-cors&trigger=nodejs%2F12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[16:06] <oSoMoN> https://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=s390x&package=node-cors&trigger=nodejs%2F12.18.1%7Edfsg-1ubuntu1&trigger=node-iconv/2.3.5-4
[16:14] <Laney> oSoMoN: let me do those
[16:14] <oSoMoN> thanks!
[16:14] <Laney> for me a pastebin would be easier, then I can act on them all more quickly
[16:14] <oSoMoN> Laney, sure thing, let me pastebin them
[16:16] <oSoMoN> Laney, https://paste.ubuntu.com/p/8GSpKXVZ4z/
[16:16] <Laney> merci
[16:16] <Laney> all done
[17:06] <vorlon> mwhudson: yes, anywhere that shim-signed is seeded should probably also have grub-pc seeded at this point, to avoid grub-efi-amd64 being wrongly pulled in; although that doesn't explain the kubuntu thing anyway given that neither kubuntu nor ubuntu have grub-pc seeded in the same place as shim-signed currently
[17:07] <vorlon> mwhudson: also Ubuntu has shim-signed seeded in live, Kubuntu does not
[17:07] <vorlon> and I frankly still don't understand the kubuntu build log output
[17:55] <RikMills> xnox: what is the potential fix that landed for #1885414
[17:55] <RikMills> LP: #1885414
[18:10] <xnox> RikMills:  debian-cd images were fixed to correctly boot; followed by 20.10.8 ubiquity landing. It unbroke ubuntu flavour images, and should improve, if not fix, other ubiquity-using flavours.
[18:11] <xnox> RikMills:  so we had a period of completely toast images; and those that had borked ubiquity
[18:11] <xnox> RikMills:  but flavour seeds may need further fixes.
[18:12] <RikMills> xnox: thanks. just going to test today's kubuntu ISO in legacy mode then
[18:13] <xnox> RikMills:  yes, thanks! It matters if one booting as CDROm or Disk/USB, legacy of uefi, which flavour, which image buildid.
[18:14] <RikMills> can only do Vbox right away, but I know that was broken yesterday
[18:17] <RikMills> if that is bust, maybe I will do some seed changes and hit the respin buttons
[18:28] <RikMills> 20200709 is borked
[19:14] <ahasenack> hi all, just a fyi that I'm working on the certbot.* migration
[19:59] <RikMills> vorlon mwhudson : even with grub-pc seeded in live, grub-efi-amd64 was still pulled in
[20:39] <vorlon> RikMills: some of these changes might require time to propagate to the archive (task fields); do you know if the Task: kubuntu-live was dropped from grub-efi-amd64 before you tried rebuilding?
[20:40] <RikMills> vorlon: I don't k
[20:40] <RikMills> *know where to check that
[20:41] <vorlon> RikMills: 'apt show grub-efi-amd64' on groovy, but you would've had to have checked it before the build since it'll change over time
[20:41] <vorlon> RikMills: anyway the field has updated now so I think we should try another rebuild
[20:41] <vorlon> (doing)
[20:41] <RikMills> I just did another
[20:41] <vorlon> ah ok
[20:42] <RikMills> I fiddled with blacklisting which I am 99% would not work, but respun anyway
[21:29] <cjwatson> RikMills: At the risk of being a broken record, the only legitimate purpose I know of for "blacklisting" in seeds (hm, I should probably rename that) is to cause builds to fail if a blacklisted package is present.  Trying to use it for any other purpose is likely to cause more problems than it solves.
[21:30] <RikMills> ok
[21:35] <cjwatson> RikMills: (as in - I think in this case it may happen to have worked, but is likely to cause other problems so it's still worth finding another answer)
[21:37] <RikMills> cjwatson: I suspect the other seed changes now propagated are more likely to be the cause for it 'working'. I will test later removing it
[21:40]  * RikMills tries installing the new iso
[21:41] <cjwatson> RikMills: Yeah, a manual run locally with the most recent kubuntu.groovy seed commit reverted doesn't seem to have grub-efi-amd64 in live
[21:42] <cjwatson> RikMills: Very likely just slow propagation of the explicit addition of grub-pc
[21:43]  * RikMills nods
[21:46] <RikMills> vorlon cjwatson et al. ok, Kubuntu now installs ok in legacy mode for me (in a VM)