[00:40] -queuebot:#ubuntu-release- New: accepted wcslib [armhf] (focal-proposed) [7.1+ds-2]
[00:40] -queuebot:#ubuntu-release- New: accepted wcslib [ppc64el] (focal-proposed) [7.1+ds-2]
[00:41] -queuebot:#ubuntu-release- New: accepted rhinote [amd64] (focal-proposed) [0.7.4-4]
[00:41] -queuebot:#ubuntu-release- New: accepted wcslib [arm64] (focal-proposed) [7.1+ds-2]
[00:41] -queuebot:#ubuntu-release- New: accepted wcslib [amd64] (focal-proposed) [7.1+ds-2]
[00:41] -queuebot:#ubuntu-release- New: accepted wcslib [s390x] (focal-proposed) [7.1+ds-2]
[05:43] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (eoan-proposed) [5.3.0-1014.15]
[05:43] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (eoan-proposed) [5.3.0-1013.14]
[05:44] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [5.0.0-1033.35]
[05:44] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1073.83]
[08:17] <ginggs> would someone please 'force-badtest ruby-declarative/0.0.10-1' ?  it seems to have regressed in release
[09:01] <locutus_> doko, can you please try to accept php-guzzlehttp-promises from queue? it is needed for symfony, but I don't know if the mismatched tarball will be ok or not...
[10:25] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (bionic-proposed/main) [5.3.0-41.33~18.04.1] (kernel)
[10:27] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [arm64] (bionic-proposed/main) [5.3.0-41.33~18.04.1] (kernel)
[10:27] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (bionic-proposed/main) [5.3.0-41.33~18.04.1] (kernel)
[11:26] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (bionic-proposed) [5.3.0-41.33~18.04.1]
[11:26] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (bionic-proposed) [5.3.0-41.33~18.04.1]
[11:26] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [arm64] (bionic-proposed) [5.3.0-41.33~18.04.1]
[12:08] <ahasenack> hi release team, the mysql8 tests seem to take too long in arm* and hit a timeout: http://autopkgtest.ubuntu.com/packages/m/mysql-8.0/focal/arm64 and https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/m/mysql-8.0/20200218_060750_f411f@/log.gz
[12:08] <ahasenack> what's the solution here?
[12:25] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (eoan-proposed/main) [5.3.0-1010.11] (core, kernel)
[13:00] -queuebot:#ubuntu-release- New binary: lighttpd [s390x] (focal-proposed/universe) [1.4.54-2ubuntu1] (no packageset)
[13:01] -queuebot:#ubuntu-release- New binary: lighttpd [amd64] (focal-proposed/universe) [1.4.54-2ubuntu1] (no packageset)
[13:03] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (eoan-proposed) [5.3.0-1010.11]
[13:05] -queuebot:#ubuntu-release- New binary: lighttpd [arm64] (focal-proposed/universe) [1.4.54-2ubuntu1] (no packageset)
[13:07] -queuebot:#ubuntu-release- New binary: lighttpd [armhf] (focal-proposed/universe) [1.4.54-2ubuntu1] (no packageset)
[15:16] -queuebot:#ubuntu-release- Unapproved: mod-wsgi (bionic-proposed/main) [4.5.17-1 => 4.5.17-1ubuntu1] (ubuntu-server)
[15:16] -queuebot:#ubuntu-release- Unapproved: mod-wsgi (xenial-proposed/main) [4.3.0-1.1build1 => 4.3.0-1.1ubuntu1] (ubuntu-server)
[15:52] -queuebot:#ubuntu-release- New: accepted lighttpd [amd64] (focal-proposed) [1.4.54-2ubuntu1]
[15:52] -queuebot:#ubuntu-release- New: accepted lighttpd [armhf] (focal-proposed) [1.4.54-2ubuntu1]
[15:52] -queuebot:#ubuntu-release- New: rejected php-guzzlehttp-promises [sync] (focal-proposed) [1.3.1-2]
[15:52] -queuebot:#ubuntu-release- New: accepted lighttpd [arm64] (focal-proposed) [1.4.54-2ubuntu1]
[15:52] -queuebot:#ubuntu-release- New: accepted pygobject-2 [amd64] (focal-proposed) [2.28.6-14ubuntu1]
[15:52] -queuebot:#ubuntu-release- New: accepted lighttpd [s390x] (focal-proposed) [1.4.54-2ubuntu1]
[17:25] -queuebot:#ubuntu-release- New binary: pyprof2calltree [amd64] (focal-proposed/universe) [1.4.4-2] (no packageset)
[17:30] <ginggs> would someone please 'force-badtest ruby-declarative/0.0.10-1' ?  it seems to have regressed in release
[17:31] <ginggs> would someone please 'force-badtest psi4/1:1.3.2-3build1/i386' ?
[18:03] <doko> vorlon: would you be willing to ignore every autopkg test for python3-defaults, dropping python3.7? the reason I'm asking is that everything else is still tested with 3.7, which we don't care about anymore
[18:03] <doko> once that migrates, everything is tested with 3.8 only
[18:18] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-89.89~16.04.1] (kernel)
[18:41] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-89.89~16.04.1]
[18:42] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-89.89~16.04.1] (kernel)
[18:47] <vorlon> ginggs: psi4/all/i386 badtested, sorry for missing it before
[18:47] <ginggs> vorlon: thanks!
[18:47] <vorlon> and hinting ruby-declarative now also
[18:48] <vorlon> doko: I'm not sure what you're asking for wrt python3-defaults ignoring.  The tests seem to be mostly passing, are you asking to not wait for test results?
[18:49] <doko> vorlon: ys
[18:50] <vorlon> doko: should we also dump the tests from the queue, so that they're not clogging up the runners running tests whose results we don't care about?
[18:50] <doko> we'll have a python3-defaults version bump anyway later, so we'll re-run these tests
[18:50] <doko> yes, dump these would be fine
[18:52] <vorlon> doko: and what's the impact to other reverse-dependencies that are not python3-defaults by letting this in?  I think you mentioned some packages with tests now failing when dropping python3.7 from supported?
[18:52] <vorlon> so if we don't track those down now there will be knock-on effects for other things migrating
[18:52] <vorlon> (not necessarily a blocker, I just want to be completely clear about the impact)
[18:52] <doko> these would be triggered by the packages itself, not passing their own autopkg tests
[18:53] <vorlon> or by other dependencies of those packages
[18:53] <doko> but again, I'm fine to re-upload python3-defaults, once the package migrated
[18:53] <doko> or wait for the version bump
[18:54] <vorlon> ok
[18:54] <doko> 3.8.3 will be next week, or the next week
[18:54] <doko> 2.8.2 even
[18:55] <doko> 3.8.2 even
[18:55] <vorlon> ok, sounds like a plan then
[19:00] <doko> vorlon: ok what? upload immediatly or after the version bump?
[19:00] <vorlon> doko: are you suggesting a second upload *just* to re-trigger the tests?  Please not that
[19:02] <doko> vorlon: as long as you're ok to do that with the version bumo, no.
[19:03] <doko> bump
[19:03] <vorlon> doko: yeah, if there's another upload coming anyway next week, please don't do a reupload just for this
[19:03] <doko> sure
[19:29] <vorlon> Laney: so I see you reset-test'ed colord/i386, which is fine, but I've been unable to reproduce the failure locally
[19:32] <ddstreet> infinity lp shows Disco as still 'supported', is that intentional for some reason, or just not updated yet? https://launchpad.net/ubuntu/disco/
[19:57] <vorlon> ddstreet: there is some cleanup yet to be done before we can close the archive in launchpad; infinity and apw know the details
[20:20] <apw> vorlon: cleaning NBS as far as I recall
[20:21] <apw> particularly of kernels which are huge
[20:21] <vorlon> apw: and did you or infinity do any particular work on scripting this?  Should I jfdi :)
[20:22] <apw> vorlon: I never actually did it, not could I say for sure that is the extent of it
[20:23] <vorlon> well NBS removals are slow
[20:23] <vorlon> but the scripting shouldn't be difficult
[20:24] <seb128> vorlon, @colord, the test depends on gnome-session which isn't build anymore on i386, how can it work for you?
[20:25] <vorlon> seb128: gnome-session is arch: all so would be /expected/ to be cross-installed, except it doesn't have the Multi-Arch: foreign flag set, so it /wouldn't/ install, so I really have no idea how it's working locally
[20:27] <seb128> vorlon, hum, I wonder if gnome-session arch:all is buggy, it deoends on gnome-session-bin which is an arch: any binary from the same source
[20:28] <seb128> or at least not compatible with a partial archive right?
[21:12] <vorlon> seb128: I suspect that gnome-session being declared Multi-Arch: foreign is probably fine because all the "interfaces" that gnome-session provides to its reverse-dependencies involve an exec() barrier; but it's also not hugely important
[21:37] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-89.89~16.04.1]
[23:19] -queuebot:#ubuntu-release- New binary: radare2 [amd64] (focal-proposed/universe) [4.2.1+dfsg-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: peony [amd64] (focal-proposed/universe) [2.0.0-1] (ubuntukylin)
[23:23] -queuebot:#ubuntu-release- New binary: radare2 [s390x] (focal-proposed/universe) [4.2.1+dfsg-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: radare2 [ppc64el] (focal-proposed/universe) [4.2.1+dfsg-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: radare2 [arm64] (focal-proposed/universe) [4.2.1+dfsg-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: radare2 [armhf] (focal-proposed/universe) [4.2.1+dfsg-1] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: peony [arm64] (focal-proposed/universe) [2.0.0-1] (ubuntukylin)