[02:03] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1057.62] (kernel)
[02:12] <vorlon> doko, infinity: well so I sorted out what was broken with archive-reports, somehow the 'run-britney' subprocess had a stale lockfile from /July/ that I had to remove in order to get everything to run to completion.  But I don't understand how that could've been the case given that reports have run successfully since then.
[02:12] <vorlon> (the file in question was testing/.run-britney.lock)
[03:08] -queuebot:#ubuntu-release- New: accepted linux-signed-gke-4.15 [amd64] (bionic-proposed) [4.15.0-1042.44]
[03:09] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1057.62]
[03:09] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (xenial-proposed) [4.15.0-1042.44]
[03:48] <apw> vorlon, could the runs since have been manual trying to debug it and finding it worked fine stylee
[03:49] <vorlon> apw: I don't think so, c-m reports have updated far too consistently
[04:21] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (xenial-proposed/main) [4.15.0-1023.26~16.04.1] (kernel)
[04:22] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (bionic-proposed/main) [4.15.0-1023.26] (kernel)
[04:24] -queuebot:#ubuntu-release- Unapproved: systemd (disco-proposed/main) [240-6ubuntu5.6 => 240-6ubuntu5.7] (core)
[04:45] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (bionic-proposed) [4.15.0-1023.26]
[04:45] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (xenial-proposed) [4.15.0-1023.26~16.04.1]
[05:33] <doko> vorlon: please ignore, not reproducible. http://autopkgtest.ubuntu.com/running#pkg-binutils amd64 and armhf are past the initial configure step, arm64 and s390x are waiting ... and https://launchpad.net/~doko/+archive/ubuntu/toolchain/+sourcepub/10464018/+listing-archive-extra looks good as well on amd64
[06:23] <vorlon> doko: done
[06:29] -queuebot:#ubuntu-release- New binary: haskell-github [amd64] (eoan-proposed/universe) [0.20-2] (no packageset)
[06:29] -queuebot:#ubuntu-release- New binary: haskell-github [i386] (eoan-proposed/universe) [0.20-2] (no packageset)
[06:39] <vorlon> Laney, juliank: s390x autopkgtests seem to be at half capacity, with only 1 worker in bos01 instead of 16; do you know why?
[06:49] <ginggs> vorlon: thanks for the autopkgtest-cloud merge, do you know when changes will take effect?  i retried mkl-dnn now, but it seems to have still run on a small instance
[06:49] -queuebot:#ubuntu-release- New sync: elisa-player (eoan-proposed/primary) [1.1+really0.4.0-1]
[06:50] <vorlon> ginggs: ah, let me deploy that
[06:50] -queuebot:#ubuntu-release- New binary: haskell-github [ppc64el] (eoan-proposed/universe) [0.20-2] (no packageset)
[06:50] <vorlon> ginggs: ginggs: deployed, takes effect immediately
[06:58] <ginggs> vorlon: ta!
[07:05] -queuebot:#ubuntu-release- New binary: pywps [amd64] (eoan-proposed/universe) [4.2.1-1ubuntu1] (no packageset)
[07:16] <marcustomlinson> vorlon: hey, could I ask you to sponsor another libreoffice upload for me? Had some component mismatches
[07:18] <marcustomlinson> some _more_ component mismatches (facepalm)
[07:19] <juliank> vorlon: that's not optimal. Haven't seen anything weird in email though, so a bit surprised
[07:22] <marcustomlinson> hey doko could you sponsor my libreoffice upload to fix those component mismatches?
[07:24] <doko> marcustomlinson: sure, where can I find it?
[07:25] <marcustomlinson> doko: https://drive.google.com/drive/folders/1RujzWuAdacd9bdpTVGyk3-AJXKpCVgTq?usp=sharing
[07:25] <doko> glibc migrated \o/
[07:32] <marcustomlinson> vorlon: ignore me, timezone fail :)
[07:48] <LocutusOfBorg> +    rm /dev/random
[07:48] <LocutusOfBorg> +    ln -s /dev/urandom /dev/random
[07:48] <LocutusOfBorg> why should anybody sane do this in a debian/test script?
[07:56] -queuebot:#ubuntu-release- New binary: haskell-github [s390x] (eoan-proposed/universe) [0.20-2] (no packageset)
[07:57] <LocutusOfBorg> shouldn't a test that does rm and ln -s of /dev devices declare "breaks testbed"?
[08:04] <Laney> vorlon: nope, did you figure it out in the meantime?
[08:05] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (disco-proposed/main) [5.0.0-28.30] (core, kernel)
[08:08] <Laney> infinity: I think Colin did some work on moving to a more recent version but it didn't work and one of us needs to pick that back up
[08:16] <Laney> vorlon: the units are disabled - why is that?
[08:17]  * Laney is going to put them back up
[08:17] <Laney> done
[08:21] -queuebot:#ubuntu-release- New binary: haskell-github [armhf] (eoan-proposed/universe) [0.20-2] (no packageset)
[08:40] -queuebot:#ubuntu-release- New: accepted haskell-github [amd64] (eoan-proposed) [0.20-2]
[08:40] -queuebot:#ubuntu-release- New: accepted haskell-github [i386] (eoan-proposed) [0.20-2]
[08:40] -queuebot:#ubuntu-release- New: accepted haskell-github [s390x] (eoan-proposed) [0.20-2]
[08:40] -queuebot:#ubuntu-release- New: accepted haskell-github [armhf] (eoan-proposed) [0.20-2]
[08:41] -queuebot:#ubuntu-release- New: accepted haskell-github [ppc64el] (eoan-proposed) [0.20-2]
[09:47] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (disco-proposed/main) [5.0.0-28.30] (core, kernel)
[09:48] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (disco-proposed/main) [5.0.0-28.30] (core, kernel)
[09:58] <RikMills> apw or another AA, any chance you could look at the elisa-player sync in New? steve said no ffe required, and just need to persuade an AA to process it. ;)
[10:13] <doko> LocutusOfBorg: any idea about the lintian autopkg test failure on armhf?
[10:31] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (disco-proposed) [5.0.0-28.30]
[10:31] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (disco-proposed) [5.0.0-28.30]
[10:31] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (disco-proposed) [5.0.0-28.30]
[10:51] <LocutusOfBorg> doko, I syncd 2.20 hoping to fix it :)
[10:51] <LocutusOfBorg> I'll have a look
[10:51] <ginggs> +binaries-general (binary): spelling-error-in-binary usr/bin/static iIF if
[10:53] <ginggs> new binutils introduces a spelling error
[10:54] <doko> really?
[10:54] <ginggs> well, it looks like lintian think it is
[11:05] <ginggs> I'm trying to skip that in my PPA...
[11:57] -queuebot:#ubuntu-release- New binary: github-backup [amd64] (eoan-proposed/universe) [1.20170301-2build2] (no packageset)
[11:57] -queuebot:#ubuntu-release- New binary: github-backup [i386] (eoan-proposed/universe) [1.20170301-2build2] (no packageset)
[11:57] <ginggs> lintian autopkgtest running now, will know in ~1hr
[11:58] -queuebot:#ubuntu-release- New binary: github-backup [ppc64el] (eoan-proposed/universe) [1.20170301-2build2] (no packageset)
[11:58] -queuebot:#ubuntu-release- New binary: github-backup [s390x] (eoan-proposed/universe) [1.20170301-2build2] (no packageset)
[12:04] -queuebot:#ubuntu-release- New binary: github-backup [armhf] (eoan-proposed/universe) [1.20170301-2build2] (no packageset)
[12:05] -queuebot:#ubuntu-release- New binary: github-backup [arm64] (eoan-proposed/universe) [1.20170301-2build2] (no packageset)
[12:12] <RikMills> iso are now startiing to bloat quite a lot due to including nvidia driver in ship-live :/
[12:19] <slashd> sil2100 or any SRU vanguard available, I found a regression in the most recent net-snmp upload, I want to let you guys know in case you want to revert the current package found in -updates until we figure out what is causing it original bug: https://bugs.launchpad.net/bugs/1835818 | regression-update bug: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843036
[12:20] <slashd> ddstreet, ^
[12:27] <slashd> sil2100, SRU vanguard, I think I found a fix, I'll keep you posted, if this still need to be reverted or not
[12:27] <slashd> ddstreet, ^
[12:50] <LocutusOfBorg> hello, do you think it is possible to kick xmds2 out because of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938925 ?
[12:50] <LocutusOfBorg> I uploaded a no-change rebuild just to have track of it
[13:04] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/xmds2/3.0.0+dfsg-2build1/+build/17530065
[13:04] <LocutusOfBorg> vorlon, ^^
[13:08] <LocutusOfBorg> (I don't see any recent upstream activity that would explain a fix in that test)
[14:06] <sil2100> slashd: ok, we'll need to revert it anyway
[14:06] <sil2100> slashd: is it a regression on all series?
[14:08] <sil2100> slashd: reverting
[14:15] <slashd> sil2100, we notice on Bionic, but won't be suprise it's the same behaviour everywhere
[14:16] <slashd> sil2100, current impact we can see is monitoring via snmp (e.g. nagios)
[14:16] <slashd> for disk
[14:16] <slashd> such as unable to monitor disk space
[14:18] -queuebot:#ubuntu-release- Unapproved: cloud-utils (disco-proposed/main) [0.31-0ubuntu1.1 => 0.31-0ubuntu1.2] (core, edubuntu)
[14:21] <slashd> thanks sil2100
[14:40] -queuebot:#ubuntu-release- Unapproved: net-snmp (bionic-updates/main) [5.7.3+dfsg-1.8ubuntu3.2 => 5.7.3+dfsg-1.8ubuntu3.1] (desktop-core, ubuntu-server) (sync)
[14:41] -queuebot:#ubuntu-release- Unapproved: net-snmp (xenial-updates/main) [5.7.3+dfsg-1ubuntu4.3 => 5.7.3+dfsg-1ubuntu4.2] (desktop-core, ubuntu-server) (sync)
[14:46] <sil2100> cjwatson: hey! Sorry to bother you, a quick AA question: if I remove (revert) a package from -updates, I usually have to copy the previous version on it's place - but what in the case of when -updates only had the faulty version that I removed? Should I still copy the release binaries to -updates anyway?
[14:49] <doko> ginggs: did you find out why this recently changed?
[14:53] <cjwatson> sil2100: seems unnecessary
[14:53] <sil2100> cjwatson: ok, thanks o/
[15:24] <vorlon> Laney: yeah, no idea at all why they were disabled, I didn't do it that's why I was asking the both of you
[15:25] <vorlon> anyway, thanks for re-enabling
[15:30] -queuebot:#ubuntu-release- Unapproved: accepted net-snmp [sync] (bionic-updates) [5.7.3+dfsg-1.8ubuntu3.1]
[15:30] -queuebot:#ubuntu-release- Unapproved: accepted net-snmp [sync] (xenial-updates) [5.7.3+dfsg-1ubuntu4.2]
[15:30] <sil2100> No worries, those are reverts for the net-snmp -updates regression ^
[15:31] <Laney> sil2100: don't you need to bump the version so that people who upgraded get the old version back?
[15:33] -queuebot:#ubuntu-release- New: accepted github-backup [amd64] (eoan-proposed) [1.20170301-2build2]
[15:33] -queuebot:#ubuntu-release- New: accepted github-backup [armhf] (eoan-proposed) [1.20170301-2build2]
[15:33] -queuebot:#ubuntu-release- New: accepted github-backup [ppc64el] (eoan-proposed) [1.20170301-2build2]
[15:33] -queuebot:#ubuntu-release- New: accepted haskell-github [amd64] (eoan-proposed) [0.20-1build2]
[15:33] -queuebot:#ubuntu-release- New: accepted haskell-github [armhf] (eoan-proposed) [0.20-1build2]
[15:33] -queuebot:#ubuntu-release- New: accepted haskell-github [ppc64el] (eoan-proposed) [0.20-1build2]
[15:33] -queuebot:#ubuntu-release- New: accepted pywps [amd64] (eoan-proposed) [4.2.1-1ubuntu1]
[15:33] -queuebot:#ubuntu-release- New: accepted github-backup [arm64] (eoan-proposed) [1.20170301-2build2]
[15:33] -queuebot:#ubuntu-release- New: accepted github-backup [s390x] (eoan-proposed) [1.20170301-2build2]
[15:33] -queuebot:#ubuntu-release- New: accepted haskell-github [i386] (eoan-proposed) [0.20-1build2]
[15:33] -queuebot:#ubuntu-release- New: accepted github-backup [i386] (eoan-proposed) [1.20170301-2build2]
[15:33] -queuebot:#ubuntu-release- New: accepted haskell-github [s390x] (eoan-proposed) [0.20-1build2]
[15:33] -queuebot:#ubuntu-release- New: accepted haskell-github [arm64] (eoan-proposed) [0.20-1build2]
[15:37] <sil2100> Laney: that's something we'll do later, for now I just reverted the version from -updates
[15:37] <sil2100> Rebuilding is like a separate thing, since it needs a rebuild, this was a bin copy
[15:37] <sil2100> So yes! Existing users will still be broken for now!
[15:37] <sil2100> slashd: did you find a fix already?
[15:39] <Laney> OK then
[16:03] -queuebot:#ubuntu-release- Unapproved: dpkg (bionic-proposed/main) [1.19.0.5ubuntu2.2 => 1.19.0.5ubuntu2.3] (core)
[16:04] -queuebot:#ubuntu-release- Unapproved: dpkg (disco-proposed/main) [1.19.6ubuntu1.1 => 1.19.6ubuntu1.2] (core)
[16:04] -queuebot:#ubuntu-release- Unapproved: dpkg (xenial-proposed/main) [1.18.4ubuntu1.6 => 1.18.4ubuntu1.7] (core)
[16:39] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-62.69~16.04.1] (kernel)
[16:39] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-62.69~16.04.1] (kernel)
[16:44] <slashd> sil2100, maybe, but need to test with impacted users first
[16:44] <slashd> sil2100, will know more most likely on Monday
[16:53] <sil2100> slashd: ok, so if the fix is not obvious, I guess I'll fast track a revert-upload with the version number bumped
[16:53] <sil2100> But after I'm back from practice
[16:55] <vorlon> coreycb: monasca-statsd is python2-only hasn't been uploaded since artful; what should we do with this?
[17:05] <vorlon> coreycb: LP: #1843078
[17:50] <coreycb> vorlon: i'll work on a new release with py3 only. it's clearly not a huge focus for us but not a dead project so might as well update it.
[18:04] -queuebot:#ubuntu-release- New binary: gdmd [amd64] (eoan-proposed/none) [2.068.2+git190828-1] (no packageset)
[18:09] -queuebot:#ubuntu-release- New: accepted gdmd [amd64] (eoan-proposed) [2.068.2+git190828-1]
[19:04] <vorlon> coreycb: ok; but in the pile of things yet to be done for 19.10, is it important to update this, vs removing it now and letting it come back in later when someone cares?
[19:05] <coreycb> vorlon: i almost came back and said let's just remove it but i already uploaded it. i agree though.
[19:08] <vorlon> hah ok
[19:48] <vorlon> coreycb: have you looked at python-cotyledon python2 removal at all?  I was working through python-os-testr NBS removal, and the obvious translations of debian/control and debian/rules fail because "PYTHON=python3.7 /usr/bin/testr-python3 run --parallel --subunit" calls "subunit2pyunit" which tries to run all the tests under python2 :P
[19:49] <vorlon> does subunit need to move to python3?  the binary package depends on both python-subunit and python3-subunit, but the shebang is python2
[19:50] <coreycb> vorlon: hmm, i haven't but happy to.
[19:50] <coreycb> vorlon: can i take it from you?
[19:51] <vorlon> coreycb: should I upload python-cotyledon as-is?  I think the bug is subunit
[19:51] <vorlon> but I don't know if it's safe to flip subunit to python3 instead of python2
[19:51] <coreycb> it should be fine to move subunit to python3 only
[19:51] <coreycb> the build-depend, that is
[19:52] <vorlon> ok, then I'll upload python-cotyledon now, and let you worry about making subunit DTRT
[19:52] <coreycb> vorlon: ok
[19:52] <vorlon> coreycb: if I hadn't already shown this to you, the burn-down list I'm working off of is https://people.canonical.com/~ubuntu-archive/nbs.html
[19:55] <coreycb> vorlon: i've seen that but i have a hard time making sense of the web of connections
[19:56] <coreycb> web of dependencies i should say
[19:58] <coreycb> i guess the confusion is when i've looked at that report, i look at corresponding source packages and they're already py3 only
[19:59] <vorlon> coreycb: but in some cases the py3-only versions might be stuck in -proposed (python-cliff, which doesn't migrate because it breaks python-os-testr and python-stestr, which are themselves NBS and should be removed, but have reverse-build-dependencies)
[20:04] <coreycb> vorlon: exactly :)
[20:04] <coreycb> vorlon: in that case does manually removing python-os-testr and python-stestr fix it?
[20:05] <vorlon> interestingly, python-pyghmi also b-d on subunit, invokes it the same way, and doesn't hit any problems due to missing python2 modules
[20:05] <vorlon> coreycb: yes but I'm also trying to unwind as much of this as possible rather than just create a pile of FTBFS packages that may or may not get looked at
[20:06] <coreycb> ok
[20:07] <vorlon> otoh some of these webs are getting knotty enough that I might start cutting through
[20:11] <vorlon> python-bandit breaks python-cliff build which doesn't migrate because it breaks python-stestr which is NBS but can't be removed because it breaks python-debtcollector which doesn't migrate because it breaks python-keystoneclient which is NBS but can't be removed because it breaks python-swiftclient which is NBS but simplestreams build-depends on it
[20:34] <vorlon> coreycb: novnc also looks like it needs switched to python3
[20:45] <coreycb> vorlon: i'll take a look
[20:48] <coreycb> vorlon: btw there's a bug for simplestreams - bug 1841277
[20:48] <vorlon> coreycb: yeah I know, I chatted briefly w/ powersj and rcj about it yesterday
[20:49] <coreycb> ok
[21:37] <coreycb> vorlon: novnc is uploaded and py2-only. i'll look at cotyledon monday.
[21:37] <vorlon> \o/
[21:37] <coreycb> great to see a couple packages trickling through out of eoan-proposed!
[22:13] <cjwatson> vorlon: In case you run into it, I'm planning to revert the removal of python-httmock temporarily, since I missed its build-dep from python-gitlab
[22:14] <vorlon> cjwatson: ok
[22:17]  * vorlon scratches his head and wonders how he managed to remove pylint2 prematurely and make things uninstallalbe
[22:20] <cjwatson> (httmock on its way into Debian NEW now)
[23:58] -queuebot:#ubuntu-release- Unapproved: net-snmp (disco-proposed/main) [5.7.3+dfsg-5ubuntu1.1 => 5.7.3+dfsg-5ubuntu1.2] (desktop-core, ubuntu-server)