[00:09] <tsimonq2> doko: Looks like acheronuk got it, yep I was at work.
[00:11]  * valorie knows all, sees all
[00:16] <tsimonq2> Creepy!
[00:19] -queuebot:#ubuntu-release- New binary: insighttoolkit4 [ppc64el] (artful-proposed/universe) [4.12.0-dfsg1-1ubuntu2] (no packageset)
[00:50] <slangasek> jbicha: a binary reject of gjs?
[00:56] <jbicha> slangasek: yes please
[00:56] <slangasek> jbicha: that's not usual; what's the status of fixing the source?
[00:57] <jbicha> the unusual version number is because that upload was intended for a ppa
[00:57] <slangasek> jbicha: so should I also remove the source from artful-proposed?
[00:57] <jbicha> we're discussing the mozjs52 transition at tomorrow's Desktop meeting so I accidentally jumped the gun
[00:58] -queuebot:#ubuntu-release- New: rejected gjs [amd64] (artful-proposed) [1.49.90-0ubuntu0~artful1]
[00:58] -queuebot:#ubuntu-release- New: rejected gjs [armhf] (artful-proposed) [1.49.90-0ubuntu0~artful1]
[00:58] <jbicha> I think it's fine to leave the source there for now
[00:58] -queuebot:#ubuntu-release- New: rejected gjs [ppc64el] (artful-proposed) [1.49.90-0ubuntu0~artful1]
[00:58] -queuebot:#ubuntu-release- New: rejected gjs [arm64] (artful-proposed) [1.49.90-0ubuntu0~artful1]
[00:58] -queuebot:#ubuntu-release- New: rejected gjs [i386] (artful-proposed) [1.49.90-0ubuntu0~artful1]
[00:59] <slangasek> jbicha: but you don't need it there and you're not getting the binaries back - so I've gone ahead and removed it anyway
[00:59] <slangasek> package in -proposed that is expected to never migrate> zot
[01:01] <jbicha> if we didn't care about s390x, the binaries might have been fine, but thanks!
[01:03] <slangasek> it might technically be possible to resuscitate both source and binaries later without a rebuild, but tbf who cares, it's cheaper for you to reupload and let the NEW process work than to get someone to fish things out of the librarian
[01:03] <tsimonq2> slangasek: Could you please badtest libreoffice/s390x in artful triggered by debhelper/10.7.2ubuntu2 so debhelper can migrate? From what I remember it's a kernel regression that's unrelated to debhelper. I asked acheronuk to retrigger libreoffice/s390x with itself as a trigger at the beginning of the day today and it fails.
[01:05] <slangasek> tsimonq2: there are a mix of passes and failures for libreoffice/s390x recently; I'm going to need some more evidence that it's a testbed problem
[01:06] <slangasek> tsimonq2: n/m, I found my previous hint for i386+s390x about this issue
[01:06] <slangasek> tsimonq2: providing a reference to an existing hint in lp:~ubuntu-release/britney/hints-ubuntu is usually the most efficient way to get me to ack a badtest :)
[01:07] <slangasek> (done)
[01:21] -queuebot:#ubuntu-release- New binary: insighttoolkit4 [s390x] (artful-proposed/universe) [4.12.0-dfsg1-1ubuntu2] (no packageset)
[01:30] <tsimonq2> slangasek: Thanks!
[02:28] <ahoneybun> cyphermox: working on your idea
[02:43] <ahoneybun> that does not look better lol
[03:51] -queuebot:#ubuntu-release- Unapproved: lxd (xenial-backports/main) [2.15-0ubuntu6~ubuntu16.04.1 => 2.16-0ubuntu2~ubuntu16.04.1] (edubuntu, ubuntu-server)
[03:51] -queuebot:#ubuntu-release- Unapproved: lxd (zesty-backports/main) [2.15-0ubuntu6~ubuntu17.04.1 => 2.16-0ubuntu2~ubuntu17.04.1] (edubuntu, ubuntu-server)
[03:57] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-backports) [2.16-0ubuntu2~ubuntu16.04.1]
[03:58] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (zesty-backports) [2.16-0ubuntu2~ubuntu17.04.1]
[05:10] -queuebot:#ubuntu-release- New binary: courier-unicode [amd64] (artful-proposed/universe) [2.0-1] (no packageset)
[05:10] -queuebot:#ubuntu-release- New binary: courier-unicode [ppc64el] (artful-proposed/universe) [2.0-1] (no packageset)
[05:11] -queuebot:#ubuntu-release- New binary: courier-unicode [s390x] (artful-proposed/universe) [2.0-1] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: courier-unicode [arm64] (artful-proposed/universe) [2.0-1] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: courier-unicode [i386] (artful-proposed/universe) [2.0-1] (no packageset)
[05:13] -queuebot:#ubuntu-release- New binary: courier-unicode [armhf] (artful-proposed/universe) [2.0-1] (no packageset)
[07:24] <ginggs> would someone please update the winff hint? maybe 'force-badtest winff/all/armhf' is best, since it hasn't passed since trusty
[08:48] <LocutusOfBorg> hello slangasek what about doing the qt5.9 dance instead of trying to patch 5.7 against the new gcc?
[08:48] <LocutusOfBorg> it is ready to land, just needing an AA
[08:55] -queuebot:#ubuntu-release- Unapproved: magnum (zesty-proposed/universe) [4.1.0-0ubuntu1 => 4.1.3-0ubuntu0.17.04.1] (no packageset)
[09:02] <acheronuk> LocutusOfBorg: I would guess he's asleep now. I'm test building 5.7.1 in a ppa with opensuse/gentoo's patch, but I agree that getting 5.9 transition landed with be far preferable
[09:08] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (xenial-proposed/universe) [1.1+16.04ubuntu3 => 1.1+16.04ubuntu4] (no packageset)
[09:44] <mitya57> tsimonq2, I am personally fine with having it stuck in proposed for a week or two, but others may get not very happy about it.
[09:45] <mitya57> So far I think that if someone still needs ubuntu-ui-toolkit for their packages, *they* should take care of updating it to 5.9.
[09:46] <mitya57> And I do not know which packages we are talking about. If it is just checkbox, then we can revert to the pre-Qt version of it.
[11:08] -queuebot:#ubuntu-release- New binary: xml-rpc-el [amd64] (artful-proposed/none) [1.6.12-2] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: debpaste-el [amd64] (artful-proposed/none) [0.1.5-2] (no packageset)
=== agateau_ is now known as agateau
[12:25] -queuebot:#ubuntu-release- Unapproved: landscape-client (trusty-proposed/main) [14.12-0ubuntu5.14.04 => 14.12-0ubuntu6.14.04] (ubuntu-desktop, ubuntu-server)
[13:27] -queuebot:#ubuntu-release- Unapproved: packagekit (xenial-proposed/main) [0.8.17-4ubuntu6~gcc5.4ubuntu1.1 => 0.8.17-4ubuntu6~gcc5.4ubuntu1.2] (kubuntu, ubuntu-desktop)
[13:36] <tsimonq2> mitya57: I remember Qt being in -proposed for a month and a half when Unity 8 was still actively developed... one or two weeks is nothing right now ;)
[13:37] <tsimonq2> mitya57: But yeah, this transition will be unusual because we're working out the Unity 8 stuff. The next Qt transition *should* be easier.
=== Guest13936 is now known as med_
=== med_ is now known as medberry
=== medberry is now known as med_
[15:23] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (trusty-proposed) [14.12-0ubuntu6.14.04]
[15:41] <cpaelzer> ping on bug 1540323 for an aa to remove packages
[15:41] <ubot5> bug 1540323 in ubuntu-virt (Ubuntu) "ubuntu-virt is not generated from seeds" [Undecided,Triaged] https://launchpad.net/bugs/1540323
[15:50] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (xenial-proposed) [1.1+16.04ubuntu4]
[16:27] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (trusty-proposed/partner) [1:20170711.1-0ubuntu0.14.04.1 => 1:20170808.1-0ubuntu0.14.04.1] (no packageset)
[16:27] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (zesty-proposed/partner) [1:20170711.1-0ubuntu0.17.04.1 => 1:20170808.1-0ubuntu0.17.04.1] (no packageset)
[16:27] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (xenial-proposed/partner) [1:20170711.1-0ubuntu0.16.04.1 => 1:20170808.1-0ubuntu0.16.04.1] (no packageset)
[16:28] <xnox> Laney, slangasek - please hint util-linux s390-tools to go in together.
[16:33] <slangasek> xnox: what kind of hint are you looking for?  AIUI s390-tools is tied to net-snmp transition
[16:33] <slangasek> which means it's tied to the big transition
[16:35] <xnox> slangasek, it is tied, I do not see it tried together with the rest. E.g. util-linux and s390-tools are not tried together, despite both being valid candidates.
[16:36] <xnox> slangasek, as far as i can tell the two are installable in both -proposed and -release and thus those two leaf packages can migrate irrespective of the big transition.
[16:36]  * xnox is possibly wrong, but the only uninstallable currently listed in output is due to not trying the two together.
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted pollinate [source] (xenial-proposed) [4.25-0ubuntu1~16.04.1]
[16:36] <slangasek> xnox: it's not tried together with the rest because util-linux doesn't need to go in together, it only needs to go in after (because of the one-way breaks)
[16:37] <slangasek> xnox: so no manual hinting needed, we just need to get p-m to pass the stone
[16:37] <xnox> hm.
[16:39] <xnox> ok.
[16:40] <xnox> slangasek, any idea why http://people.canonical.com/~ubuntu-archive/transitions/ocaml.html ocaml is no longer installable? is that also in the big transition of doom now?
[16:41] <slangasek> xnox: according to http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt output, ocaml is not tied in
[16:45] -queuebot:#ubuntu-release- New binary: libgtop2 [amd64] (artful-proposed/main) [2.37.90-0ubuntu1] (ubuntu-desktop)
[16:45] -queuebot:#ubuntu-release- New binary: libgtop2 [ppc64el] (artful-proposed/main) [2.37.90-0ubuntu1] (ubuntu-desktop)
[16:45] <coreycb> hi release team, i synced sphinx from experimental and it's causing problems. can we reject it from artful-proposed and stick with 1.5.6-2 for now?
[16:46] -queuebot:#ubuntu-release- New binary: libgtop2 [i386] (artful-proposed/main) [2.37.90-0ubuntu1] (ubuntu-desktop)
[16:46] -queuebot:#ubuntu-release- New binary: libgtop2 [s390x] (artful-proposed/main) [2.37.90-0ubuntu1] (ubuntu-desktop)
[16:48] <slangasek> addressed coreycb's request
[16:51] -queuebot:#ubuntu-release- New binary: libgtop2 [arm64] (artful-proposed/main) [2.37.90-0ubuntu1] (ubuntu-desktop)
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted pollinate [source] (trusty-proposed) [4.25-0ubuntu1~14.04.1]
[16:56] -queuebot:#ubuntu-release- New binary: libgtop2 [armhf] (artful-proposed/main) [2.37.90-0ubuntu1] (ubuntu-desktop)
[17:00] <ginggs> would someone please update the winff hint? maybe 'force-badtest winff/all/armhf' is best, since it hasn't passed since trusty
[17:00] <ginggs> slangasek: ^ seeing you are around :)
[17:02] <slangasek> ginggs: /all/ hinting means that if and when the test is fixed we don't pick it up. the solution with least collateral damage is LP: #1700668, if you can convince Laney of the design ;)
[17:02] <ubot5> Launchpad bug 1700668 in britney "make it easier to reset baseline for autopkgtests that regress in release" [Undecided,New] https://launchpad.net/bugs/1700668
[17:04] <slangasek> we need a tool added to ubuntu-archive-tools that scans update_excuses for all regressions and matches them to existing badtest hints for a different version
[17:04] <slangasek> anyone want to write that? :)
[17:05] <ginggs> slangasek: elbrus cares about autopkgtests, so if it does start to pass on armhf i think he'll let us know
[17:05] <ginggs> but yeah, we do need a general solution
[17:06] <slangasek> I don't assume elbrus would notify us to remove a hint that's letting us ignore failures
[17:12] <slangasek> doko: ah, thanks for the pillow delete - let me also resurrect the no-change rebuild, then
[17:13] <xnox> slangasek, somehow i'm not sure how i can help with migrations. I think i will work on making ocaml stack installable and migratable again the bits that got synced/updated. but that is about it.
[17:13] <xnox> and the systemd adt regresions.
[17:14] <slangasek> xnox: well, for example, anything that's listed on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt as broken by the big migration, but not listed on http://people.canonical.com/~ubuntu-archive/proposed-migration/artful/update_output_notest.txt , needs sorting out what tests are failing
[17:16] <doko> xnox: you could look at lp: #1709396
[17:16] <ubot5> Launchpad bug 1709396 in gcc-7 (Ubuntu) "gcc-7/i386|armhf 12.1.2 FTBFS" [Undecided,New] https://launchpad.net/bugs/1709396
[17:18] <slangasek> xnox: (but ignore all the kde stuff there, because that's just waiting on tests to finish for qtwebengine-opensource-src)
[17:21] <slangasek> doko: I now have a "clean" autopkgtest of linux on armhf against new binutils/gcc showing a build failure; can you confirm this is a kernel bug, not a toolchain bug?
[17:21] <xnox> doko, or shall i fix linux/zfs s390x given that i ported that?
[17:21] <slangasek> hinting that will re-unblock binutils
[17:21] <slangasek> xnox: also valuable :)
[17:22] <slangasek> xnox: we've overridden that test for now, but obviously we need kernels to be uploadable
[17:23] <slangasek> xnox: mysql-5.7 also needs sorting (i386 test failure)
[17:24] <slangasek> tdaitx: you want to take a corner of this puzzle?
[17:24] <doko> slangasek: afaics this is the first build of one of the user space tools built using GCC 7, triggered by a warning turned into an error by the build process
[17:25] <slangasek> doko: so the message is correct / has precedent, and the kernel needs fixing. thanks, hinting
[17:31] <tdaitx> slangasek, which one you are referring to?
[17:31] <slangasek> tdaitx: the mega-transition clogging up proposed-migration; see above for a list of possible +1 maintenance tasks to work on
[17:31] <tdaitx> sure
[17:32] <slangasek> tdaitx: if you take one, please let us know which it is :)
[17:32] <tdaitx> will start on that after lunch
[17:35] <xnox> slangasek, please clean http://people.canonical.com/~ubuntu-archive/nbs.html
[17:35] <doko> xnox: done
[17:41] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (trusty-proposed) [1:20170808.1-0ubuntu0.14.04.1]
[17:41] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (zesty-proposed) [1:20170808.1-0ubuntu0.17.04.1]
[17:41] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20170808.1-0ubuntu0.16.04.1]
[18:03] <xnox> http://people.canonical.com/~ubuntu-archive/architecture-mismatches.html is odd no?
[18:07] -queuebot:#ubuntu-release- Unapproved: accepted postfix [source] (xenial-proposed) [3.1.0-3ubuntu0.1]
[18:24] <slangasek> a small tool that may help people deciphering the transition: https://code.launchpad.net/~vorlon/ubuntu-archive-tools/migration-blocked-by-tests
[18:25] <tsimonq2> slangasek: awesome! :D
[18:27] <slangasek> further enhancement would be to make that script track down which source package's failing test is at issue
[18:43] <slangasek> skiptest'ing pillow (it was a candidate once before, we don't need to wait for re-testing).  that should clear a lot of the underbrush
[19:08] <cyphermox> anyone already looking at libgtk2-perl?
[19:09] <cyphermox> (failing test there)
[19:11] <cyphermox> ahoneybun: what do you mean does not look better? maybe we should communicate by screenshot... I mean, if you're happy with the current state of the slideshow as it is in your original merge, I'll just upload that, but it really does look really bad to me here when running test-slideshow.
[19:14] <cyphermox> nevermind about libgtk2-perl, the test was not run with the same version
[19:16] <slangasek> anyone know offhand what's eating the buildd queue?
[19:17] <slangasek> oh hey look, pillow et al. migrated
[19:18] <tsimonq2> Lots of private jobs... :|
[19:19] <slangasek> rbalint1: hi, what can we say about grok? (libevent transition)
[19:19] <infinity> slangasek: iz livepatch.
[19:19] <slangasek> infinity: k
[19:20] <slangasek> rbalint1: looks like a wrong version comparison for gperf, is there a fix in flight anywhere?
[19:22] <slangasek> xnox: so you just uploaded hhvm? wasn't the version in -proposed already ready to migrate?
[19:25] <slangasek> claiming watchcatd
[19:42] <cyphermox> looking at picviz
[19:42] <cyphermox> or has that already been taken?
[19:53] <xnox> slangasek, the one in proposed was not good enough, and not if ftbfs with gcc-7
[19:53] <slangasek> xnox: 'not good enough' how?  was it not a candidate for migration with perl etc?
[20:19] <tsimonq2> Could someone on the SRU team please look at bug 1133477 and bug 1708619? The former of which is important to have because without it, there's potential data loss in Nautilus and Caja, and the latter is a regression in the audio applet in Lubuntu from 16.10 to 17.04 which should get fixed soon...
[20:19] <ubot5> bug 1133477 in gvfs (Ubuntu Xenial) "[SRU] cut-n-paste move files got stuck forever" [Undecided,Fix committed] https://launchpad.net/bugs/1133477
[20:19] <ubot5> bug 1708619 in indicator-sound-gtk2 (Ubuntu Zesty) "[SRU] sound settings does nothing - sound menu of the indicator applet" [Undecided,In progress] https://launchpad.net/bugs/1708619
[20:20] <tsimonq2> Both of which have been uploaded to the queues already, I just think the former is extremely important and worth poking about (the latter is less important but still annoying). :)
[20:22] <rbasak> tsimonq2: I'm EOD now, but please poke me tomorrow (it's my SRU day tomorrow) if you don't get a review before then.
[20:22] <tsimonq2> rbasak: Ok, thank you.
[20:22] <slangasek> rbalint: where would I find API docs for libevent explaining the changes from 2.0 to 2.1?  ev_arg and ev_flags seem to have disappeared without a trace
[20:22] <rbasak> I say that, but I'm still working, unwinding my stack :-/
[20:23] -queuebot:#ubuntu-release- New source: python-certbot-apache (xenial-proposed/primary) [0.14.2-0ubuntu0.16.04.1]
[20:23] -queuebot:#ubuntu-release- Unapproved: python-acme (xenial-proposed/universe) [0.4.1-1 => 0.14.2-0ubuntu0.16.04.1] (no packageset)
[20:24] -queuebot:#ubuntu-release- Unapproved: python-letsencrypt (xenial-proposed/universe) [0.4.1-1 => 0.4.1-1ubuntu0.16.04.1] (no packageset)
[20:24] -queuebot:#ubuntu-release- Unapproved: python-certbot-apache (zesty-proposed/universe) [0.10.2-1 => 0.14.2-0ubuntu0.17.04.1] (no packageset)
[20:24] -queuebot:#ubuntu-release- Unapproved: python-certbot (zesty-proposed/universe) [0.10.2-1 => 0.14.2-0ubuntu0.17.04.1] (no packageset)
[20:24] -queuebot:#ubuntu-release- Unapproved: python-letsencrypt-apache (xenial-proposed/universe) [0.4.1-1 => 0.4.1-1ubuntu0.16.04.1] (no packageset)
[20:24] -queuebot:#ubuntu-release- Unapproved: python-certbot-nginx (zesty-proposed/universe) [0.10.2-1 => 0.14.2-0ubuntu0.17.04.1] (no packageset)
[20:24] -queuebot:#ubuntu-release- Unapproved: python-acme (zesty-proposed/universe) [0.10.2-1 => 0.14.2-0ubuntu0.17.04.1] (no packageset)
[20:24] -queuebot:#ubuntu-release- New source: python-certbot-nginx (xenial-proposed/primary) [0.14.2-0ubuntu0.16.04.1]
[20:24] -queuebot:#ubuntu-release- New source: python-certbot (xenial-proposed/primary) [0.14.2-0ubuntu0.16.04.1]
[20:33] <xnox> i wish gtk2 and qt4 were dead =)
[20:33] <acheronuk> +1
[20:34] <tsimonq2> +1
[20:35] <tsimonq2> xnox: I'd like to eventually see if we could get Qt 4 off of all the images (well, Kubuntu and Lubuntu Next) and see if we could get it out of the archive after that.
[20:35] <tsimonq2> But I think I'll do a better analysis when 18.10 opens for development.
[20:36] <tsimonq2> Meanwhile, Lubuntu will kill GTK 2 shortly, I don't think it would be off to suggest that 18.10 will be that cycle.
[20:36] <tsimonq2> s/off/far off/
[20:36] <tsimonq2> xnox: But Qt 4 will be quicker than GTK 2 from what I can tell :P
[20:37] <acheronuk> libreoffice-kde is still Qt4 :(
[20:38] <tsimonq2> acheronuk: Maybe in the next year, something can be done to fix that...
[20:39] <acheronuk> yep. could get quite close to no KDE4 on our iso if not for that
[20:40] <tsimonq2> For sure
[20:48] <Ukikie> -1
[20:49] <tsimonq2> Ukikie: oh?
[21:20] <rbalint> slangasek: there is whatsnew-2.1.txt.gz but this change is not covered, i rely on git history to understand the change
[21:22] <rbalint> slangasek: if you haven't started fixing the affected package i will do it and don't wait for Debian maintainers
[21:26] <slangasek> rbalint: I hadn't made any progress, feel free to take it (watchdogd)
[21:29] <rbalint> slangasek: ok, i take it then
[21:31] <slangasek> rbalint: sorry, watchcatd not watchdogd :)
[21:33] <rbalint> slangasek: yes, i got it :-)
[21:55] <slangasek> grok upload fixed
[21:57] <cyphermox> picviz done
[21:57] <cyphermox> I'd do lldpd now
[22:01] <slangasek> mdeslaur, rbasak: any insights into the mysql-5.7/i386 autopkgtest failure?
[22:04] <rbasak> slangasek: I was going to ask someone upstream but he's on vacation until Monday.
[22:04] <slangasek> rbasak: k. do you have any more info beyond what's currently in the log?
[22:06] <rbasak> "Failing test(s): main.mysql_upgrade"
[22:06] <rbasak> I think that test has been unstable in the past.
[22:06] <slangasek> retrying it
[22:07] <slangasek> and yes, it does seem to be the same error seen previously with 5.7.18-0ubuntu1
[22:07] <rbasak> https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=b89cf68d7517c4400a4bd76b6d2a49d24518a8ed may be relevant. It'll be in the next merge.
[22:07] <slangasek> rbasak: hinted for now, thanks
[22:08] <rbasak> (which was actually blocked on my review, and I'd +1 but we got trumped by security because I was slow :-
[22:08] <rbasak> (
[22:08] <cyphermox> slangasek: has update-output-helper never been merged into ubuntu-archive-tools yet?
[22:09] <slangasek> cyphermox: no, I was never able to wrap my head around its usage to the point where I found it consistently helpful, so I haven't ever merged it
[22:15] <cyphermox> ok
[22:15] <cyphermox> well it was broken now anyway due to authenticating package sources
[23:16] <slangasek> acheronuk: thanks for cleaning up the qtwebengine-opensource-src mess.  There is a failing autopkgtest now, http://autopkgtest.ubuntu.com/packages/k/kdepim-addons/artful/armhf - is there any chance this is introduced by qtwebengine, or is it a false positive?  (And if it is a real regression, should we care or should we just hint it in knowing that 5.9 is around the corner?)
[23:21] <slangasek> qtwebengine is possibly the only package currently blocking wrt tests.  we also need gcc-7 ready to go again, webauth (available in the next run), watchcatd, hhvm (which could be removed), and then we might actually be done?
[23:22] <slangasek> that, and a kernel unblocked (apw?)
[23:26] -queuebot:#ubuntu-release- New binary: insighttoolkit4 [armhf] (artful-proposed/universe) [4.12.0-dfsg1-1ubuntu2] (no packageset)
[23:46] <mwhudson> so why the heck is python-urllib3 not migrating
[23:47] <mwhudson> ah it needs to migrate with requests i think
[23:48] <mwhudson> which is blocked by python-pydap tests failing
[23:49] <slangasek> mwhudson: because of some sort of s390x-specific breakage, AFAICS from update_output
[23:50] <mwhudson> slangasek: how do you get that?
[23:50] <slangasek> mwhudson: the uninstallables count is only increased for s390x
[23:50] <mwhudson> skipped: python-urllib3 (0, 23, 9)
[23:50] <mwhudson>     got: 92+0: a-7:a-7:a-7:i-59:p-6:s-6
[23:51] <mwhudson> ?
[23:51] <slangasek> mwhudson: ah, I refresh and I get a different list. so this is actually the funny business of reporting arch: all packages against a random arch
[23:52] <mwhudson> yeah i think so
[23:52] <mwhudson> i still don't understand update_output but it's definitely not going to migrate without requests also migrating
[23:53] <slangasek> right