/srv/irclogs.ubuntu.com/2020/02/10/#ubuntu-release.txt

=== guiverc2 is now known as guiverc
mwhudsoni don't suppose anyone who can log into autopkgtest infra is around?02:22
handsome_fengHi, ukui-menu 2.0.1-1 is blocked when migrating from -proposed to release because missing build on i386, but the i386 package (ukui-menu=1.1.12-1) is migrate from eoan to focal, how to deal with this situation? Thanks!02:26
xnoxmwhudson:  i think i actually have the right permissions to do that.02:31
xnoxmwhudson:  but after initial training, it might be a while for me to dig up the right hostnames to ssh into02:31
xnoxmwhudson:  what specifically are you after?02:31
mwhudsonxnox: do you have any way of deriving what is causing https://autopkgtest.ubuntu.com/running#pkg-docker.io to hang?02:31
mwhudsonxnox: it doesn't hang when i run it locally :(02:31
xnoxle sigh02:33
xnoxfor that one may need to ssh all the way into the guest os, and i'm not sure i've done that, I only got to the queus and workers.02:33
xnoxit should be all local, cause it is importing a tarball and running it.02:33
mwhudsonactually i think it's possible you need to launch a job in a special way to allow a human to log into it, i forget02:34
xnoxunless dockerd is dead, or hung up, with a new kernel....02:34
mwhudsonxnox: it's triggered by the new containerd02:34
xnoxthat also sounds like something familear02:34
mwhudson(in focal-proposed)02:34
xnoxonce it times out and fails, there should be a log right. i wonder if things are not happy with new kernel, new systmed, new apparmor and the like with the new containerd.02:35
xnoxplus i thought debian has broken networking02:35
* xnox wonders if ubuntu true test would just work02:35
xnoxalthough networking stuff should have been fixed by now02:35
xnoxhorum02:35
xnoxi'm gonna finish my mint tea and go to bed =)02:36
mwhudsonxnox: nothing in logs iirc but maybe i should check an old failure indeed02:44
mwhudsonxnox: good night02:44
mwhudsonno nothing useful in artifacts02:45
mwhudsonxnox: i want to talk to you about vtoc tomorrow :)02:48
-queuebot:#ubuntu-release- New: accepted gitless [amd64] (focal-proposed) [0.8.8-2]03:12
handsome_fengSorry, I got it, It's because it migrate from python to qt, and the architecture changes from all to any.03:52
wxlhandsome_feng: p.s. kylin's looking good in qt :)03:52
handsome_fengwxl, Thanks! :)03:53
handsome_fengAnd anyone know how to deal with this situation? I didn't find the document. :(04:00
-queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-tesla-418 [amd64] (focal-proposed/multiverse) [418.116.00-3] (no packageset)05:24
-queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-tesla-418 [ppc64el] (focal-proposed/multiverse) [418.116.00-3] (no packageset)05:32
infinityhandsome_feng: Fixing ukui-menu (and panel appears to have the same issue).05:34
handsome_fenginfinity: Thanks!06:08
-queuebot:#ubuntu-release- New binary: cinnamon-control-center [s390x] (focal-proposed/universe) [4.4.0-2] (no packageset)06:14
-queuebot:#ubuntu-release- New binary: cinnamon-control-center [ppc64el] (focal-proposed/universe) [4.4.0-2] (no packageset)06:15
-queuebot:#ubuntu-release- New binary: cinnamon-control-center [amd64] (focal-proposed/universe) [4.4.0-2] (no packageset)06:16
-queuebot:#ubuntu-release- New binary: cinnamon-control-center [arm64] (focal-proposed/universe) [4.4.0-2] (no packageset)06:20
-queuebot:#ubuntu-release- New binary: cinnamon-control-center [armhf] (focal-proposed/universe) [4.4.0-2] (no packageset)06:20
RAOFSo, now that Mir builds and passes it's !i386 autopkgtests, the thing try do is to delete the stale i386 binaries and everything is hunky-dory, right?07:05
dokoRAOF: did you you schedule the rebuilds for the soname change?07:27
-queuebot:#ubuntu-release- New: accepted cinnamon-control-center [amd64] (focal-proposed) [4.4.0-2]07:31
-queuebot:#ubuntu-release- New: accepted cinnamon-control-center [armhf] (focal-proposed) [4.4.0-2]07:31
-queuebot:#ubuntu-release- New: accepted cinnamon-control-center [s390x] (focal-proposed) [4.4.0-2]07:31
-queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-tesla-418 [ppc64el] (focal-proposed) [418.116.00-3]07:31
-queuebot:#ubuntu-release- New: accepted cinnamon-control-center [arm64] (focal-proposed) [4.4.0-2]07:31
-queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-tesla-418 [amd64] (focal-proposed) [418.116.00-3]07:31
-queuebot:#ubuntu-release- New: accepted cinnamon-control-center [ppc64el] (focal-proposed) [4.4.0-2]07:31
RAOFdoko: To my knowledge there are no rdepends of Mir-built binaries (at present)07:46
RAOF(At least, ones that are not built from the Mir source package)07:47
-queuebot:#ubuntu-release- New binary: icu [s390x] (focal-proposed/main) [65.1-1] (core, i386-whitelist)07:51
-queuebot:#ubuntu-release- New binary: icu [i386] (focal-proposed/main) [65.1-1] (core, i386-whitelist)07:52
-queuebot:#ubuntu-release- New binary: icu [amd64] (focal-proposed/main) [65.1-1] (core, i386-whitelist)07:55
-queuebot:#ubuntu-release- New binary: icu [arm64] (focal-proposed/main) [65.1-1] (core, i386-whitelist)08:07
-queuebot:#ubuntu-release- New binary: icu [armhf] (focal-proposed/main) [65.1-1] (core, i386-whitelist)08:08
=== andrewc is now known as Guest88169
locutus_mwhudson, hello, I did sync python-traits, not sure but flaky tests seems to be not flaky anymore?09:35
locutus_it built fine on first attempt09:36
mwhudsonlocutus_: i don't remember that package i'm afraid09:48
mwhudsoni guess it's s good thing it's building :)09:48
tseliothello admins, I don't think nvidia-graphics-drivers-tesla-418 should have been synced, since we don't sync nvidia drivers from Debian10:32
tseliotapw ^^10:32
tseliotalso sil2100 ^10:32
rbalintsil2100, could you please merge https://code.launchpad.net/~rbalint/britney/hints-ubuntu/+merge/378651 for systemd?12:05
apwtseliot, i'll pull it, and that should also cause it to be blacklisted12:25
tseliotapw, thanks, I think this one should go with it too https://launchpad.net/ubuntu/+source/nvidia-settings-tesla-41812:27
apwtseliot, yeah ... both done12:27
tseliotapw, thanks again12:27
=== cpaelzer__ is now known as cpaelzer
cpaelzerhiho, why is wal2json in update_excuses complaining about "missing build on armhf: postgresql-12-wal2json (from 2.0-1)"13:23
cpaelzerthe whole point of 2.0-2 was to drop armhf and i38613:23
cpaelzerplease do not that is misses the "2.0-1" binary13:24
cpaelzerbut this is for 2.0-213:24
cpaelzeror it misses the armhf binary "coming from 2.0-1"13:25
cpaelzerbut never the less - the current 2.0-2 doesn't want to have the armhf/i386 binaries13:25
cpaelzeranything I can do to resolve that and get it moving again?13:25
cjwatsonBecause 2.0-1 was built on armhf in focal-proposed and not migrated, and proposed-migration doesn't automatically handle that case13:26
cjwatsonI'll remove it by hand13:26
cpaelzerFull discplaimer: in a few days hopefulyl there will be a 2.1-1 which will re-add armhf/i386 but I'd prefer not to rely on that13:26
cpaelzercjwatson: ah so it really is because 2.0-1 had armhf and it is now missing13:26
cpaelzerthanks cjwatson13:26
cjwatsondone13:27
cpaelzergreat, checking back later how migration goes on then13:27
-queuebot:#ubuntu-release- Unapproved: shim-signed (eoan-proposed/main) [1.39.1 => 1.41] (core) (sync)13:46
-queuebot:#ubuntu-release- Unapproved: shim (eoan-proposed/main) [15+1533136590.3beb971-0ubuntu1 => 15+1552672080.a4a1fbe-0ubuntu1] (core) (sync)13:46
-queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.4 => 1.41] (core) (sync)13:46
-queuebot:#ubuntu-release- Unapproved: shim (bionic-proposed/main) [15+1533136590.3beb971-0ubuntu1 => 15+1552672080.a4a1fbe-0ubuntu1] (core) (sync)13:46
-queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.33.1~16.04.5 => 1.41] (core) (sync)13:47
-queuebot:#ubuntu-release- Unapproved: shim (xenial-proposed/main) [15+1533136590.3beb971-0ubuntu1 => 15+1552672080.a4a1fbe-0ubuntu1] (core) (sync)13:47
juliankxnox: ^ shims for everyone :)13:47
juliankNot sure how this is going to work SRU wise, as we don't have an SRU bug number13:47
julianklast one did not have one either, though13:48
xnoxjuliank:  blame the guy who quit! =)13:48
juliankWe can reuse my bug, and tag it update-excuses maybe?13:49
juliankidk13:49
juliankcertainly we can tag it block-proposed-{xenial,bionic,eoan}13:49
juliankidk13:49
xnoxoooh update-excuse yeah13:49
* xnox ponders if update-excuse tag should be renamed to udpate-excuses13:49
* RikMills wonders who decided that a test error should show a red grinning face emoji13:51
-queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1071.81] (kernel)14:17
=== andrewc is now known as Guest3295
infinityRikMills: I believe the "design" (I use that term loosely) of most of that UI was pitti.14:24
rbalintsil2100, could you please drop current ec2-instance-connect srus from from the unapproved queue? I'm about to upload a new set instead14:25
juliankhmm should I only have copied shim, and not shim-signed?14:38
* juliank confused14:38
-queuebot:#ubuntu-release- Unapproved: ibm-java80 (xenial-release/partner) [8.0.6.0-0ubuntu1 => 8.0.6.5-0ubuntu1] (no packageset) (sync)14:38
juliankor should I have used proper backport SRUs for shim-signed, so that we get an SRU bug in there?14:39
juliankwiki page just said copy binaries, but shim-signed seems to have been uploaded with version per release14:40
apwjuliank, if i am remembering correctly (and that is questionable) we have switched things like enforcement at different times which might have necessitated skew15:07
juliankHmm15:08
juliankI think those should be hardcoded in the binaries, and they're the same15:09
juliankbut surrounding might be different15:09
julianke.g. update-secureboot-policy15:09
julianksomeone should probably reject the shim-signed uploads15:09
juliankand then they need redoing15:10
juliankWell, eoan probably nobody cares15:10
juliankah we do15:11
juliankYup gotta redo those15:12
apwjuliank, so reject the lot, or just -signed15:12
juliankapw: just signed is fine, if you reject all, I could copy the unsigned ones back, though, it doesn't really matter15:12
apwjuliank, ack15:13
=== msalvatore_ is now known as msalvatore
-queuebot:#ubuntu-release- Unapproved: rejected shim-signed [sync] (bionic-proposed) [1.41]15:15
-queuebot:#ubuntu-release- Unapproved: rejected shim-signed [sync] (eoan-proposed) [1.41]15:15
-queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1071.81]15:15
-queuebot:#ubuntu-release- Unapproved: rejected shim-signed [sync] (xenial-proposed) [1.41]15:15
apwjuliank, ^15:15
juliankthanks, apw15:15
-queuebot:#ubuntu-release- Unapproved: accepted clamav [source] (eoan-proposed) [0.102.1+dfsg-0ubuntu0.19.10.3]15:44
-queuebot:#ubuntu-release- Unapproved: accepted clamav [source] (bionic-proposed) [0.102.1+dfsg-0ubuntu0.18.04.3]15:59
slashdBig thanks sil2100 ^15:59
-queuebot:#ubuntu-release- Unapproved: accepted clamav [source] (xenial-proposed) [0.102.1+dfsg-0ubuntu0.16.04.3]16:07
sil2100yw!16:08
bashfulrobotinfinity: I'm just curious. Are you by chance aware as to when the LTS applications have to be in by?16:19
-queuebot:#ubuntu-release- Unapproved: rejected ec2-instance-connect [source] (bionic-proposed) [1.1.12+dfsg1-0ubuntu2~18.04.0]16:29
-queuebot:#ubuntu-release- Unapproved: rejected ec2-instance-connect [source] (eoan-proposed) [1.1.12+dfsg1-0ubuntu2~19.10.0]16:29
-queuebot:#ubuntu-release- Unapproved: rejected ec2-instance-connect [source] (xenial-proposed) [1.1.12+dfsg1-0ubuntu2~16.04.0]16:30
sil2100vorlon: hey! Looking at the xenial queue, I see a new ibm-java80 for partner, but the target destination seems to be the Release pocket - guess when I accept it, it will bypass partner proposed, right?16:40
-queuebot:#ubuntu-release- New source: python-gffutils (focal-proposed/primary) [0.10.1-1ubuntu1]17:08
vorlonsil2100_: yeah, if it's targeted to the release pocket, that's the case17:34
vorlondannf: ^^17:34
dannfvorlon, sil2100_ ah, sorry - probably me failing at trying to use copy-package again. should i retry w/ --to-suite xenial-proposed?17:40
vorlondannf: yes please :-)17:41
dannfvorlon: ok - that looks better.17:41
-queuebot:#ubuntu-release- Unapproved: ibm-java80 (xenial-proposed/partner) [8.0.6.0-0ubuntu1 => 8.0.6.5-0ubuntu1] (no packageset) (sync)17:42
-queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.4 => 1.37~18.04.5] (core)17:56
vorlonsil2100_: ^^ if you're doing reviews, this is a one-liner fix for a regression in the previous -proposed upload17:58
sil2100_vorlon: on it o/18:09
=== andrewc is now known as Guest88553
sil2100_vorlon: is this also fixing the previous issue? Since the previous LP bug got lost in the .changes, probably needs a reupload with -v18:19
vorlonsil2100_: I can do that18:20
vorlonplz reject18:20
-queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.4 => 1.37~18.04.5] (core)18:21
-queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (bionic-proposed) [1.37~18.04.5]18:22
vorlonrbalint, xnox: should LP: #1860432 be wontfix for systemd?  sounds like juju is going to change their behavior18:22
ubot5Launchpad bug 1860432 in systemd (Ubuntu Focal) "juju agent fails to start on focal " [Undecided,Confirmed] https://launchpad.net/bugs/186043218:22
xnoxi still wanted to at least file an upstream issue about it18:23
dokoso we still have a lot of b-d's on python and python-dev, which showed up in NBS a while ago. but not anymore. why not?18:25
vorlondoko: because python and python-dev are not NBS because they have been removed?18:26
vorlonthey were uninstallable, so there was no reason in terms of archive consistency to keep them around in the release pocket18:26
-queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (bionic-proposed) [1.37~18.04.5]18:26
-queuebot:#ubuntu-release- Unapproved: accepted ibm-java80 [sync] (xenial-proposed) [8.0.6.5-0ubuntu1]18:27
-queuebot:#ubuntu-release- Unapproved: rejected ibm-java80 [sync] (xenial-release) [8.0.6.5-0ubuntu1]18:27
dokook, then I assume we need to setup a transition tracker to point out the remaining ones18:28
-queuebot:#ubuntu-release- New binary: icu [amd64] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)20:14
-queuebot:#ubuntu-release- New binary: icu [s390x] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)20:14
-queuebot:#ubuntu-release- New binary: icu [i386] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)20:15
-queuebot:#ubuntu-release- New binary: icu [ppc64el] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)20:15
-queuebot:#ubuntu-release- New binary: icu [armhf] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)20:23
-queuebot:#ubuntu-release- New binary: icu [arm64] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)20:29
mwhudsonvorlon: ok https://autopkgtest.ubuntu.com/running#pkg-docker.io is hanging, if you could log in and run ps / lsof / strace any likely looking things / etc that would be great21:14
ddstreetinfinity i see you're listed in the sru rotation for today, though i'm not sure if that's still accurate, but if it is could you release qemu for b/e and network-manager for e21:17
vorlonmwhudson: ps: https://paste.ubuntu.com/p/Yp84qQWhp2/21:45
vorlonmwhudson: docker ps: https://paste.ubuntu.com/p/48jhgHGY7s/21:46
vorlonmwhudson: lsof/strace on the 'docker run': https://paste.ubuntu.com/p/tTVWNJ79H9/21:49
vorlonmwhudson: a second 'docker run' also hangs21:50
mwhudsonvorlon: can you strace the containerd-shim process?21:56
mwhudsonvorlon: also lsof21:57
mwhudsonvorlon: ideally before the test times out :)22:25
vorlonmwhudson: there are 2 containerd-shim processes, do you know if I should be looking at parent or child?22:27
mwhudsonvorlon: i only see one in your first ps listing, is that because you ran docker run again?22:28
vorlonoh, maybe?22:28
mwhudsonhttps://paste.ubuntu.com/p/Yp84qQWhp2/ only has 809222:28
vorlonright, it's not parent/child22:28
mwhudsonaiui docker run talks to dockerd talks to containerd22:28
vorlonmwhudson: https://paste.ubuntu.com/p/bJ4CKfS6tS/22:29
vorlonthe thread eventually woke up again, but it's just more futex/nanosleep nonsense22:30
mwhudsonyeah that's doing a whole lot of nothing isn't it22:30
mwhudsoni wonder if there's any way to see what the eventpoll things are22:31
mwhudsonyeah i definitely think that containerd-shim should have exited22:35
mwhudsonbiab22:35
mwhudsonvorlon: i don't suppose it'll reveal much but "ls -l /var/lib/containerd/io.containerd.runtime.v1.linux/moby/c37559527799313b65be7e8b63736947312b28986a3d6fcf3ee9a5a20cdd415a/" ?22:58
mwhudsonvorlon: and maybe ls -l /run/docker/containerd/22:59
mwhudsonvorlon: also can you gdb -p to a containerd-shim and 'thread apply all bt' or whatever that command is?23:01
mwhudsonhm might need to install the ddeb for that to be at all useful :(23:02
vorlonmwhudson: $ sudo ls -l /var/lib/containerd/io.containerd.runtime.v1.linux/moby/c37559527799313b65be7e8b63736947312b28986a3d6fcf3ee9a5a20cdd415a/23:02
vorlontotal 023:02
vorlonprwx------ 1 root root 0 Feb 10 21:05 shim.stderr.log23:02
vorlonprwx------ 1 root root 0 Feb 10 21:05 shim.stdout.log23:02
vorlon$ sudo ls -l /run/docker/containerd/23:02
vorlontotal 023:02
vorlondrwxr-xr-x 2 root root 80 Feb 10 21:05 c37559527799313b65be7e8b63736947312b28986a3d6fcf3ee9a5a20cdd415a23:02
vorlondrwxr-xr-x 2 root root 80 Feb 10 21:50 f8d72d17248ce5eb41b87f63a63c7507332bee28f7bee0214a79e3f60c09cff723:03
mwhudsonhm no we don't strip go things still23:03
mwhudsonhm no apparently we do but there is no ddeb on https://launchpad.net/ubuntu/+source/containerd/1.3.1-0ubuntu1/+build/18193736 ?23:03
vorlonheh oops23:04
mwhudsonhow did we manage that23:04
vorlonask the go maintainers23:04
mwhudsonyeah unfortunately that's me23:04
vorlonmwhudson: yeah, a whole lot of No symbol table info23:05
mwhudsonah upstream Makefile23:06
mwhudsonifndef GODEBUG23:06
mwhudson        EXTRA_LDFLAGS += -s -w23:06
mwhudsonffffffffffffuuuuuuuuuuuu23:06
mwhudsonoh heh i have containerd 1.3.2 in git locally23:12
vorlonI do not think I want to define a God EBUG23:16
mwhudsonoh wait maybe we want this fix https://github.com/containerd/containerd/pull/385723:17
mwhudsonso maybe if i just upload things will start working by magic23:17
gitbotcontainerd issue (Pull request) 3857 in containerd "Fix container pid race condition." [Cherry-Pick/1.3.X, Cherry-Picked/1.3.X, Priority/P0, Closed]23:17
-queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.7-2 => 1.3.7-3] (core)23:24
-queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.7-2 => 1.3.7-3] (core)23:28
-queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.7-2 => 1.3.7-3] (core)23:28
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (focal-proposed) [1.3.7-3]23:35
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (focal-proposed) [1.3.7-3]23:35
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (focal-proposed) [1.3.7-3]23:35
-queuebot:#ubuntu-release- New binary: qtlocation-opensource-src [s390x] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)23:44
-queuebot:#ubuntu-release- New binary: qtlocation-opensource-src [amd64] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)23:51
-queuebot:#ubuntu-release- New binary: qtlocation-opensource-src [ppc64el] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)23:54

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