/srv/irclogs.ubuntu.com/2020/07/09/#ubuntu-devel.txt

seb128hum, quite some desktop i386 autopkgtest unhappy due to08:08
seb128Processing triggers for libc-bin (2.31-0ubuntu10) ...08:08
seb128E: Could not configure 'libc6:i386'.08:08
seb128E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)08:08
seb128is that a known issue/something being worked on?08:08
seb128doko, ^ you might know?08:08
Unit193Silly seb, i386 doesn't exist!08:08
* Unit193 ducks.08:08
seb128oh, of course! :p08:09
Unit193Sorry, I'm only useful every other day. :)08:09
seb128that's fine, I will queue a question for tomorrow then :p08:10
=== M_hc[m] is now known as _hc
xnoxseb128:  although one is installing special packages, they are of the other arch, thus shouldn't actually try to require immediate configuration.12:03
ahasenackgood morning12:23
ahasenackhm, 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/1956148212:28
ahasenackoh12:28
ahasenackit helps when I reload the excuses page12:28
seb128xnox, 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
oSoMoNcan a MOTU please retry the node-body-parser tests with the correct triggers?12:42
oSoMoNhttp://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-412:42
oSoMoNhttp://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-412:42
oSoMoNhttp://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-412:42
oSoMoNhttp://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-412:42
oSoMoNhttp://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-412:42
=== Trevinho_ is now known as Trevinho
kanashirohey, 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:18
rafaeldtinocooSoMoN: doing13:21
oSoMoNthanks!13:21
rafaeldtinocoall done ;) you're welcome13:22
ahasenackrbasak: hi, ok to import a new package manually following those instructions?13:25
ahasenackon the usual host?13:25
rbasakahasenack: yes. I intend to move to the new host very soon (today or tomorrow maybe) but working on something else right now13:26
ahasenackk13:28
ahasenackoh, turns out this one is already imported, I typoed when checking13:29
=== zyga_ is now known as zyga-mbp
oSoMoNI 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:45
oSoMoNalso, 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 me15:49
oSoMoNsimilarly for http://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=arm64&package=node-clean-css&trigger=nodejs/12.18.1%7Edfsg-1ubuntu115:53
oSoMoNthe 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
oSoMoNhttp://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-416:01
oSoMoNhttp://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-416:01
oSoMoNhttp://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-416:01
oSoMoNhttp://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-416:01
oSoMoN(sorry for spamming with these requests, it's only the beginning, as there are many test failures in nodejs rdeps…)16:02
oSoMoNnode-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-1ubuntu116:04
oSoMoNhere we go again, node-cors needs an additional node-iconv trigger:16:06
oSoMoNhttps://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-416:06
oSoMoNhttps://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-416:06
oSoMoNhttps://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-416:06
oSoMoNhttps://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-416:06
oSoMoNhttps://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-416:06
LaneyoSoMoN: let me do those16:14
oSoMoNthanks!16:14
Laneyfor me a pastebin would be easier, then I can act on them all more quickly16:14
oSoMoNLaney, sure thing, let me pastebin them16:14
oSoMoNLaney, https://paste.ubuntu.com/p/8GSpKXVZ4z/16:16
Laneymerci16:16
Laneyall done16:16
=== thedac_ is now known as thedac
=== sadin999_ is now known as sadin999
vorlonmwhudson: 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 currently17:06
vorlonmwhudson: also Ubuntu has shim-signed seeded in live, Kubuntu does not17:07
vorlonand I frankly still don't understand the kubuntu build log output17:07
RikMillsxnox: what is the potential fix that landed for #188541417:55
RikMillsLP: #188541417:55
ubottuLaunchpad bug 1885414 in ubiquity (Ubuntu Groovy) "on flavours ubiquity: bootloader failed on /dev/vda" [Critical,Triaged] https://launchpad.net/bugs/188541417:55
xnoxRikMills:  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:10
xnoxRikMills:  so we had a period of completely toast images; and those that had borked ubiquity18:11
xnoxRikMills:  but flavour seeds may need further fixes.18:11
RikMillsxnox: thanks. just going to test today's kubuntu ISO in legacy mode then18:12
xnoxRikMills:  yes, thanks! It matters if one booting as CDROm or Disk/USB, legacy of uefi, which flavour, which image buildid.18:13
RikMillscan only do Vbox right away, but I know that was broken yesterday18:14
RikMillsif that is bust, maybe I will do some seed changes and hit the respin buttons18:17
RikMills20200709 is borked18:28
ahasenackhi all, just a fyi that I'm working on the certbot.* migration19:14
RikMillsvorlon mwhudson : even with grub-pc seeded in live, grub-efi-amd64 was still pulled in19:59
vorlonRikMills: 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:39
RikMillsvorlon: I don't k20:40
RikMills*know where to check that20:40
vorlonRikMills: 'apt show grub-efi-amd64' on groovy, but you would've had to have checked it before the build since it'll change over time20:41
vorlonRikMills: anyway the field has updated now so I think we should try another rebuild20:41
vorlon(doing)20:41
RikMillsI just did another20:41
vorlonah ok20:41
RikMillsI fiddled with blacklisting which I am 99% would not work, but respun anyway20:42
cjwatsonRikMills: 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:29
RikMillsok21:30
cjwatsonRikMills: (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:35
RikMillscjwatson: I suspect the other seed changes now propagated are more likely to be the cause for it 'working'. I will test later removing it21:37
* RikMills tries installing the new iso21:40
cjwatsonRikMills: Yeah, a manual run locally with the most recent kubuntu.groovy seed commit reverted doesn't seem to have grub-efi-amd64 in live21:41
cjwatsonRikMills: Very likely just slow propagation of the explicit addition of grub-pc21:42
* RikMills nods21:43
RikMillsvorlon cjwatson et al. ok, Kubuntu now installs ok in legacy mode for me (in a VM)21:46

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!