[04:46] <wxl> hey where would i go to to point out that lxd images don't seem to be available as of the 1st?
[04:46] <wxl> (for cosmic)
[04:49] <Ukikie> They've removed it from repos, they want you to use the 'snap'..
[04:49] <wxl> i'm not talking about the lxd packages
[04:50] <wxl> i'm talking about the actual images
[04:50] <wxl> i.e. `lxc image list ubuntu-daily: | grep cosmic | grep 20180903` returns nothing
[04:51] <wxl> oddly they are at images.linuxcontainers.org
[04:51]  * wxl scratches his head
[04:52] <wxl> oops s/cosmic/18\.10/
[04:54] <Ukikie> Ah.
[05:38] <slangasek> wxl: 'ubuntu-daily' does not necessarily mean that they're produced daily; as http://cloud-images.ubuntu.com/cosmic/ shows, there were no new images between the 1st and the 4th, and the ones from today may not have made their way through the importing process yet
[05:39] <slangasek> (indeed, these images are generally expected to be trigger-based in responses to changes in the image contents, and there may have been no changes in the past few days on account of glibc)
[05:39] <wxl> slangasek: ok, that makes sense.
[05:41] <wxl> slangasek: fwiw i've been trying to monitor a weird situation i've run into where the last few images have not had a network connection, at least with lxd 3.0.1-0ubuntu1~18.04.1
[05:45] <slangasek> hmm
[05:45] <wxl> the one from the 26th works fine
[05:45] <slangasek> only with the cosmic images?
[05:46] <wxl> i tried bionic and had no such issues
[05:46] <wxl> although i wonder if i didn't install a release version rather than a daily
[05:46] <wxl> let me try to remember to command to figure that out
[05:50] <wxl> yep i tried 20180831 bionic and all was well
[05:56] <wxl> interestingly, i had a working container that i made the mistake of enabling proposed on and then doing an upgrade. i managed to do some pinning and used apt-offline to get it back to release state, but it didn't fix the issue. i think whatever broke managed to migrate to release
[06:19] -queuebot:#ubuntu-release- Unapproved: accepted gnu-efi [source] (bionic-proposed) [3.0.8-0ubuntu1~18.04.1]
[06:22] -queuebot:#ubuntu-release- Unapproved: accepted gnu-efi [source] (xenial-proposed) [3.0.8-0ubuntu1~16.04.1]
[06:26] -queuebot:#ubuntu-release- Unapproved: accepted gnu-efi [source] (trusty-proposed) [3.0.8-0ubuntu1~14.04.1]
[06:30] -queuebot:#ubuntu-release- Unapproved: rejected shim [sync] (trusty-proposed) [13-0ubuntu2]
[06:31] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [sync] (trusty-proposed) [1.33.1~14.04.1]
[06:37] <acheronuk> 07:04:10 /usr/bin/ruby: relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
[06:38] -queuebot:#ubuntu-release- Unapproved: shim (trusty-proposed/main) [0.9+1474479173.6c180c6-1ubuntu1 => 13-0ubuntu2] (core) (sync)
[06:38] <acheronuk> does ruby 2.5 need a rebuild?
[06:39] <slangasek> that looks like you have a running process that needs restarted when glibc is upgraded due to loading of NSS modules at runtime
[06:39] -queuebot:#ubuntu-release- Unapproved: accepted shim [sync] (trusty-proposed) [13-0ubuntu2]
[06:41] <acheronuk> it's in a docker image build, so not sure how that would work
[06:44] <slangasek> well, /lib/x86_64-linux-gnu/libnss_files.so.2 comes from the libc6 package and should never be out of sync on the filesystem
[06:47] <acheronuk> seems to be upgrading libc ok https://kci.pangea.pub/view/bionic%20FIX/job/mgmt_docker/label=master/2455/console
[07:38] <LocutusOfBorg> infinity, everything I don't understand worries me :) thanks for caring!
[07:38] <doko> apw: please have a look at the linux autopkg test failure triggered by gcc-7?
[07:39] <doko> slangasek: I have seen such messages as well, but not yet on the buildd. Involving libpthread
[07:43] <LocutusOfBorg> [09:00:19] <BTS> Opened #908013 (serious) in src:libindicator 0.5.0-3 by Adrian Bunk (bunk) «libindicator FTBFS with glib 2.58». https://bugs.debian.org/908013
[07:43] <LocutusOfBorg> [09:00:26] <BTS> Opened #908014 (serious) in src:libldm 0.2.4-1 by Adrian Bunk (bunk) «libldm FTBFS with glib 2.58». https://bugs.debian.org/908014
[07:43] <ubot5> Debian bug 908013 in src:libindicator "libindicator FTBFS with glib 2.58" [Serious,Open]
[07:43] <ubot5> Debian bug 908014 in src:libldm "libldm FTBFS with glib 2.58" [Serious,Open]
[07:44] <LocutusOfBorg> src:libqmi  src:network-manager-iodine and so on...
[07:44] <LocutusOfBorg> are we sure syncing glib was a good idea?
[08:03] <seb128> LocutusOfBorg, you would have preferred to stay on an unstable version than do the update to the stable release?
[08:05] <Laney> don't make deprecations into build errors
[08:34] <LocutusOfBorg> seb128, I trust you as usual, just I'm worried about all the packages that now needs fixes... for sure moving from snapshot to stable is good, maybe adding a patch to avoid reverse-deps FTBFS was worth the effort?
[08:35] <seb128> there is probably not that many packages that error out on deprecation warnings and those are easy enough to fix
[08:36] <Laney> we're not going to un-deprecate a function in a distro patch
[10:10] <juliank> hmm
[10:10] <juliank> cosmic:
[10:11] <juliank>  sbuild-build-depends-packagekit-dummy : Depends: libgtk-3-dev (>= 3.2) but it is not going to be installed
[10:11] <juliank> for https://launchpad.net/ubuntu/+source/packagekit/1.1.10-1ubuntu5
[10:11] <juliank> what broke?
[10:12] <Laney> it's probably skew with the recently uploaded gtk+3.0
[10:13] <juliank> yeah
[10:13] <juliank> amd64 builds and does not have the gtk published yet
[10:14] <juliank> probably that's the reason - libgtk-3-common missing
[10:14] <juliank> so should work again once it's published
[10:14] <Laney> indeedies
[11:51] -queuebot:#ubuntu-release- Unapproved: xorg-server (bionic-proposed/main) [2:1.19.6-1ubuntu4 => 2:1.19.6-1ubuntu4.1] (desktop-core, xorg)
[11:56] -queuebot:#ubuntu-release- Unapproved: xorg-server-hwe-16.04 (xenial-proposed/main) [2:1.19.6-1ubuntu4~16.04.1 => 2:1.19.6-1ubuntu4.1~16.04.1] (no packageset)
[12:11] -queuebot:#ubuntu-release- Unapproved: rejected xorg-server-hwe-16.04 [source] (xenial-proposed) [2:1.19.6-1ubuntu4.1~16.04.1]
[12:12] -queuebot:#ubuntu-release- Unapproved: xorg-server-hwe-16.04 (xenial-proposed/main) [2:1.19.6-1ubuntu4~16.04.1 => 2:1.19.6-1ubuntu4.1~16.04.1] (no packageset)
[12:29] <ahasenack> hi, does anybody know if the dep8 test runners mount filesystems with noexec perhaps? I'm debugging this error:
[12:29] <ahasenack> + debian/tests/login.exp testuser1 testuser1kerberos testuser1@EXAMPLE.COM
[12:29] <ahasenack>  /tmp/autopkgtest.cRVUhE/build.cWY/src/debian/tests/ldap-user-group-krb5-auth: 57: /tmp/autopkgtest.cRVUhE/build.cWY/src/debian/tests/ldap-user-group-krb5-auth: debian/tests/login.exp: Permission denied
[12:29] <ahasenack> that script is +x, and it worked in lxd and kvm locally
[12:39] <apw> ahasenack, we have executable tests in the kernel package, and they run ok, so i don't think that file can be on a noexec filesystem
[12:40] <ahasenack> it's odd
[12:40] <ahasenack> I'm calling it with the interpreter in the command line now, will see
[12:47] <apw> ahasenack, the form of that error seems odd to me, the repeat of the krb5-auth in particular
[12:49] <ahasenack> yeah
[12:51] -queuebot:#ubuntu-release- Unapproved: openvpn (bionic-proposed/main) [2.4.4-2ubuntu1 => 2.4.4-2ubuntu1.1] (ubuntu-server)
[13:58] -queuebot:#ubuntu-release- New: accepted smc-tools [source] (cosmic-proposed) [1.1.0-0ubuntu1]
[14:00] -queuebot:#ubuntu-release- New binary: smc-tools [ppc64el] (cosmic-proposed/none) [1.1.0-0ubuntu1] (no packageset)
[14:00] -queuebot:#ubuntu-release- New binary: smc-tools [s390x] (cosmic-proposed/none) [1.1.0-0ubuntu1] (no packageset)
[14:01] -queuebot:#ubuntu-release- New binary: smc-tools [i386] (cosmic-proposed/none) [1.1.0-0ubuntu1] (no packageset)
[14:02] -queuebot:#ubuntu-release- New binary: smc-tools [amd64] (cosmic-proposed/none) [1.1.0-0ubuntu1] (no packageset)
[14:04] <doko> LocutusOfBorg: I saw your diffoscope and cmake-extras uploads. do you follow-up on these?
[14:05] -queuebot:#ubuntu-release- New binary: smc-tools [arm64] (cosmic-proposed/universe) [1.1.0-0ubuntu1] (no packageset)
[14:08] -queuebot:#ubuntu-release- New binary: smc-tools [armhf] (cosmic-proposed/universe) [1.1.0-0ubuntu1] (no packageset)
[14:13] -queuebot:#ubuntu-release- New: accepted smc-tools [amd64] (cosmic-proposed) [1.1.0-0ubuntu1]
[14:13] -queuebot:#ubuntu-release- New: accepted smc-tools [armhf] (cosmic-proposed) [1.1.0-0ubuntu1]
[14:13] -queuebot:#ubuntu-release- New: accepted smc-tools [ppc64el] (cosmic-proposed) [1.1.0-0ubuntu1]
[14:13] -queuebot:#ubuntu-release- New: accepted smc-tools [arm64] (cosmic-proposed) [1.1.0-0ubuntu1]
[14:13] -queuebot:#ubuntu-release- New: accepted smc-tools [s390x] (cosmic-proposed) [1.1.0-0ubuntu1]
[14:13] -queuebot:#ubuntu-release- New: accepted smc-tools [i386] (cosmic-proposed) [1.1.0-0ubuntu1]
[14:14] -queuebot:#ubuntu-release- Unapproved: libvirt (bionic-proposed/main) [4.0.0-1ubuntu8.4 => 4.0.0-1ubuntu8.5] (ubuntu-server, virt)
[14:16] <LocutusOfBorg> doko, diffoscope is sad, I asked mapreri to help me
[14:16] <LocutusOfBorg> I don't know why, so if you want to help it is appreciated, because I think I'll stop there
[14:17] <LocutusOfBorg> (it is quick and easy to fix the test, but the problem is that I don't understand why it changed, and it might be an llvm issue)
[14:17] <doko> and cmake-extras?
[14:17] <LocutusOfBorg> (the new diffoscope fom debian FTBFS even before)
[14:17] <LocutusOfBorg> cmake-extras just needed a no change rebuild and is good already
[14:18] <doko> but the autopkg tests still fail?
[14:18] <LocutusOfBorg> damn it is not
[14:18] <LocutusOfBorg> indeed
[14:18] <LocutusOfBorg> let me check
[14:18] <doko> ta
[14:19] <LocutusOfBorg> ok fixed.
[14:19] <LocutusOfBorg> doko, btw, FYI https://salsa.debian.org/debian-ayatana-team/cmake-extras/commit/0a0439c6a565c5c20143a236d6c6b9c799d418be
[14:19] <LocutusOfBorg> this is the reason for me introducing the new python-clang metapackage
[14:20] <LocutusOfBorg> but I only fixed git, never uploaded
[15:13] <ahasenack> apw: I switched that call to this, and tests are green now: + /usr/bin/expect -f debian/tests/login.exp testuser1 testuser1kerberos testuser1@EXAMPLE.COM
[15:26] <doko> xnox: libu2f: that seeding helped
[16:03] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (bionic-proposed/main) [1:18.04.25 => 1:18.04.26] (core)
[16:04]  * slangasek tries to figure out what's going on with llvm versions in cosmic main :P
[16:45] <ahasenack> infinity: hi, do you think squid4 for cosmic is still doable? We are 2w into feature freeze
[16:45] <ahasenack> https://launchpad.net/ubuntu/cosmic/+queue?queue_state=0&queue_text=squid
[16:46] <teward> can a release team member review an FFe request for NGINX 1.15.3, and either ACK (so I can upload) or NACK it?  Primary "feature change" is minor, the primary drive to get this in is the bugfixes to the WebDAV module from upstream.
[16:46] <teward> (LP #1790149)
[16:46] <ubot5> Launchpad bug 1790149 in nginx (Ubuntu) "[FFe needed] Update NGINX in Cosmic to 1.15.3 for bugfixes" [Wishlist,New] https://launchpad.net/bugs/1790149
[16:51] -queuebot:#ubuntu-release- Unapproved: nautilus (bionic-proposed/main) [1:3.26.3-0ubuntu4 => 1:3.26.4-0~ubuntu18.04.1] (ubuntu-desktop)
[17:10] -queuebot:#ubuntu-release- New sync: pipewire (cosmic-proposed/primary) [0.2.2-1]
[17:11] -queuebot:#ubuntu-release- New sync: fontpens (cosmic-proposed/primary) [0.1.0-1]
[17:11] -queuebot:#ubuntu-release- New sync: ufonormalizer (cosmic-proposed/primary) [0.3.5-1]
[17:44] -queuebot:#ubuntu-release- New sync: python-osc-placement (cosmic-proposed/primary) [1.3.0-1]
[17:53] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.18 => 2.02~beta2-36ubuntu3.19] (core)
[17:58] -queuebot:#ubuntu-release- Unapproved: grub2 (trusty-proposed/main) [2.02~beta2-9ubuntu1.15 => 2.02~beta2-9ubuntu1.16] (core)
[17:59] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.4 => 2.02-2ubuntu8.5] (core)
[18:03] <LocutusOfBorg> slangasek, seems doko trying to get llvm7 in main and llvm6 in universe
[18:04] <doko> yes, as in every release cycle
[18:04] <LocutusOfBorg> but llvm 6 will go out once mesa is fixed
[18:04] <LocutusOfBorg> and also doxygen, and defaults...
[18:05] <doko> doxygen is fixed
[18:05] <doko> mesa is on the way
[18:07] <LocutusOfBorg> oh nice!
[18:07] <LocutusOfBorg> so we need diffoscope and we are goo
[18:07] <LocutusOfBorg> *good
[18:07] <LocutusOfBorg> and also an llvm-7 stable maybe... it should be released today, but they are usually one month late...
[18:08] <doko> that's ok. we don't have many dependencies
[18:09] <LocutusOfBorg> you should also care about end user installing a snapshot rc compiler as default
[18:27] <LocutusOfBorg> please any AA kill anbox from cosmic https://bugs.launchpad.net/ubuntu/+source/anbox/+bug/1780655
[18:27] <ubot5> Ubuntu bug 1780655 in anbox (Ubuntu) "RoM: please remove this from ubuntu, doesn't work" [Undecided,New]
[18:44] -queuebot:#ubuntu-release- Unapproved: grub2 (cosmic-proposed/main) [2.02+dfsg1-5ubuntu2 => 2.02+dfsg1-5ubuntu2] (core)
[18:53] <slangasek> LocutusOfBorg: done
[19:03] <slangasek> doko: did you also promote python-django-babel?  Did this not need an MIR?
[19:22] -queuebot:#ubuntu-release- Unapproved: grub2 (cosmic-proposed/main) [2.02+dfsg1-5ubuntu2 => 2.02+dfsg1-5ubuntu2] (core)
[19:26] <slangasek> LocutusOfBorg: symfony testsuite still failing on armhf and s390x (and should this not have had an FFe?)
[19:44] -queuebot:#ubuntu-release- New: accepted kubernetes [source] (cosmic-proposed) [1.0]
[19:46] -queuebot:#ubuntu-release- New binary: kubernetes [amd64] (cosmic-proposed/none) [1.0] (no packageset)
[19:50] <slangasek> coreycb: panko still blocked in -proposed due to armhf autopkgtest failure, which seems very reproducible.  any idea what's what here?
[19:51] <coreycb> slangasek: i'm working on it here: https://bileto.ubuntu.com/#/ticket/3405. i believe curl is not installed for arm.
[19:51] <slangasek> coreycb: ah, yes if you use curl in your tests you should depend on it :-)
[19:53] -queuebot:#ubuntu-release- New: accepted kubernetes [amd64] (cosmic-proposed) [1.0]
[19:53] <coreycb> slangasek: well, yes :) but it doesn't need explicit install for other non-arm for some reason.
[19:55] <slangasek> coreycb: armhf is the only architecture which uses containers instead of VMs; the lxd images should still be derived from the standard cloud image the same as the nova images are, I'm not sure why there would be different results
[19:56] <coreycb> slangasek: ok
[20:00] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (cosmic-proposed) [2.02+dfsg1-5ubuntu2]
[20:00] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (cosmic-proposed) [2.02+dfsg1-5ubuntu2]
[20:05] -queuebot:#ubuntu-release- Unapproved: snapcraft (bionic-proposed/universe) [2.43+18.04 => 2.43.1+18.04] (no packageset)
[20:07] -queuebot:#ubuntu-release- Unapproved: snapcraft (xenial-proposed/universe) [2.43 => 2.43.1] (no packageset)
[20:11] -queuebot:#ubuntu-release- Unapproved: shim-signed (trusty-proposed/main) [1.33.1~14.04.1 => 1.33.1~14.04.2] (core)
[20:26] -queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.33.1~16.04.1 => 1.33.1~16.04.2] (core)
[20:48] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (trusty-proposed) [1.33.1~14.04.2]
[20:49] <cyphermox> SRU team: could you please check / release https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.4  to bionic-proposed?
[20:49] <cyphermox> I mean bionic-updates.
[20:51] <slangasek> cyphermox: doing
[20:52] <slangasek> cyphermox: done
[21:05] <cyphermox> ta
[21:06] <cyphermox> slangasek: could you please also reject grub2 from bionic-proposed queue? I'll upload a new one with an extra fix
[21:10] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (bionic-proposed) [2.02-2ubuntu8.5]
[21:11] <cyphermox> ta
[21:13] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.4 => 2.02-2ubuntu8.5] (core)
[21:15] -queuebot:#ubuntu-release- Unapproved: grub2-signed (bionic-proposed/main) [1.93.5 => 1.93.6] (core)
[21:15] <slangasek> juliank, Laney: so http://autopkgtest.ubuntu.com/running shows a python3.7 autopkgtest that's been hung with no output for 148h.  I've traced down the corresponding systemd unit (autopkgtest@bos02-arm64-5.service) which is not failed so hasn't been restarted.  Do you think there's any more investigation warranted here before I reset it?
[21:19] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (bionic-proposed) [2.02-2ubuntu8.5]
[21:22] -queuebot:#ubuntu-release- Unapproved: rejected grub2-signed [source] (bionic-proposed) [1.93.6]
[21:28] <LocutusOfBorg> slangasek, nope, symfony is the really same release :)
[21:28] <slangasek> LocutusOfBorg: 3.4.14->3.4.15?
[21:28] <LocutusOfBorg> oh, I see changes are mostly fixes, 30k diff
[21:29] <LocutusOfBorg> did you see new features?
[21:29] <LocutusOfBorg> 12 bug fixed, no new features AFAICS
[21:29] <slangasek> I didn't look deeply
[21:29] <LocutusOfBorg> btw the test always failed on those architectures
[21:30] <slangasek> proposed-migration thinks it's a regression
[21:30] <LocutusOfBorg> it was good when I made the testsuite return 0 because of the phpunit deprecation warnings, so now it is seen as regression
[21:30] <LocutusOfBorg> I missed that it was failing on two archs, and when I discovered the error testsuite had already run
[21:30] <LocutusOfBorg> so now I'm trying to ignore testsuite there, and I fail
[21:30] <slangasek> well, the last upload has the autopkgtest failing on all archs
[21:31] <LocutusOfBorg> yep, I know, not sure why it works locally :(
[21:31] <LocutusOfBorg> I'll have a look tomorrow
[21:31] <LocutusOfBorg> some damn bash bug
[21:32] <LocutusOfBorg> oh... missing dpkg-architecture dependency...
[21:32] <LocutusOfBorg> so dpkg-dev is not installed during testsuite?
[21:46] <slangasek> juliank, Laney: actually, there are 7 of these borked units; I'll go ahead and clear 6 of them and leave one of the ppc64el ones around for investigation if wanted (autopkgtest@bos02-ppc64el-20.service)
[22:09] <jbicha> could sysprof/s390x/cosmic please be removed? it only built there because we ignored build test failures in the previous upload