[07:17] <cpaelzer> hi, the current bionic apache2 upload https://launchpad.net/ubuntu/+source/apache2/2.4.29-1ubuntu2 is blocked in proposed for a component mismatch to libnghttp2-14 - the MIR for that is complete in bug 1687454
[07:17] <ubot5> bug 1687454 in curl (Ubuntu) "[MIR] nghttp2" [Undecided,Triaged] https://launchpad.net/bugs/1687454
[07:19] <cpaelzer> OTOH I do not see it in https://people.canonical.com/~ubuntu-archive/component-mismatches.txt , so maybe I fail to see something else missing in this case
[07:20] <cpaelzer> So I either need an AA to promote that through the mismatch or some guidance on what I overlook in this case
[07:21] <cpaelzer> I'd have expected the autopkgtests to run and then be a component mismatch, but the tests block on "unsatisfiable Depends: libnghttp2-14"
[07:22] <cpaelzer> But other than being in universe it is there as far as I can see
[07:36] <infinity> cpaelzer: http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.txt is what you're after.  Fixing.
[07:41] <cpaelzer> infinity: thanks for the link but I'm puzzled
[07:41] <infinity> cpaelzer: By?
[07:41] <cpaelzer> is that telling me something else than the expected component mismatch?
[07:41] <infinity> cpaelzer: It's telling you what you thought you wanted to see on the other page.
[07:41] <cpaelzer> lol
[07:42] <infinity> cpaelzer: The other page, of course, won't list the mismatch because it doesn't include -proposed, and thus nothing is pulling nghttp2 into main there.
[07:42] <infinity> cpaelzer: Anyhow, it's promoted now.
[07:42] <cpaelzer> thank you
[07:42] <cpaelzer> I had the link from https://wiki.ubuntu.com/MainInclusionProcess
[07:42] <cpaelzer> would it be reasonable if I added the one you gave me there as well?
[07:43] <infinity> cpaelzer: Sure.  Maybe s/show up in the component-mismatches list/show up in the component-mismatches list, or if the dependency is only in proposed, the component-mismatches-proposed list/
[07:45] <cpaelzer> done
[07:45] <cpaelzer> checking the autopkgtests in a few hours then ...
[08:01] <cpaelzer> Can someone cancel https://launchpad.net/ubuntu/+source/iproute2/4.14.1-0ubuntu1 from bionic-proposed
[08:01] <cpaelzer> other than tests before upload suggested this needs a bigger cleanup for ubuntu-fan
[08:01] <cpaelzer> I want to prepare a proper ..ubuntu2 for that, but that needs some time
[08:01] <cpaelzer> so cancelling the current one would be kind to interfer less with others
[08:02] <infinity> cpaelzer: Is it interfering in some way?
[08:02] <infinity> It builds no libraries, so the only way it could be causing issues if it it's actually broken somehow.
[08:03] <cpaelzer> infinity: it works in general but not with ubuntu fan
[08:03] <infinity> Mmkay.  I can delete it.
[08:03] <cpaelzer> thank you
[08:04] <infinity> cpaelzer: Gone.
[11:32] <doko> $ fgrep gvfs *
[11:32] <doko> vorlon:force-badtest gvfs/1.34.1-1ubuntu3/s390x
[11:32] <doko> please add ppc64el, tired about giving that back for every package multiple times ...
[11:33] <doko> or better disable the flaky tests, but that should be a task for the package owners ...
[11:37] <Laney> doko: done
[12:25] <acheronuk> Could someone please 'force-badtest kdepim-runtime/all/ppc64el kdepim-runtime/all/s390x' ?
[12:27] <acheronuk> that is another that seems to want to run tests on those architectures against itself, despite no binaries building
[12:30] <doko> infinity, slangasek, apw, Laney: please don't work on python-gobject-dev in NBS, using that as an example package mentoring Lucasz
[12:32] <apw> doko, ack
[12:43] <LocutusOfBorg> apw, hinting systemd/amd64 badtest will make a lot of stuff migrate, e.g. curl with security fixes inside...
[12:44] <apw> LocutusOfBorg, that on the face of it is a terrifying idea ... letting a systemd which is not passing its tests out
[12:45] <LocutusOfBorg> I'm running systemd against itself right now
[12:46] <LocutusOfBorg> apw, I know, but we are stuck with curl because of that, I pinged xnox above, I don't really know what to do
[12:46] <apw> LocutusOfBorg, oh but that looks like the reboot issue ... bah
[12:46] <LocutusOfBorg> we discussed this above already yesterday with cpaelzer and somebody else
[12:46] <LocutusOfBorg> I would like to upload the curl merge with new release and http2 support :)
[12:47] <LocutusOfBorg> somebody mentioned a race condition on the bug, but retrying the test is not helping too much
[12:47] <Laney> yet there are 4 more retries running right now
[12:48] <apw> Laney, did you make things smarter that we now see the dmesg bits in the logs ?
[12:48] <Laney> if it errors
[12:48] <apw> Laney, ahhh only if it is _your_ reboot which triggers it i assume
[12:48] <Laney> doesn't appear to be happening there
[12:49] <Laney> the test carries on, if that bug happens the machine dies forever
[12:49] <apw> oh yeah, so that specific instance isn't it, though the one on lsb _is_
[12:49] <apw> Laney, ^5 for adding that info, that is awsome
[12:50] <Laney> lsb is the same bug, right
[12:50] <Laney> but the others aren't AFAICS
[12:51] <LocutusOfBorg> I did run it against itself, lets see what happens
[12:52] <LocutusOfBorg> cpaelzer, libvirt merge ping? :)
[12:53] <Laney> right, but the 4 other retries aren't very helpful I don't think
[12:58] <coreycb> bdmurray: we have a few stable uploads that could use a review. nova for xenial and neutron for zesty. would you or someone else on the team be able to take a look?
[14:31] <LocutusOfBorg> can we have systemd forced bad then? curl is still waiting his cve fixes :(
[14:50] <bdmurray> coreycb: Its slangasek's day but if he can't I will.
[14:59] <jbicha> please consider badtesting pinentry/s390x, it's always-failed on most architectures (holding up gtk+2.0 and others today)
[15:02] <coreycb> bdmurray: thanks, much appreciated
[15:11] <LocutusOfBorg> apw, you ignored linux block, but I think there is a little NBS in proposed cleanup needed
[15:11] <LocutusOfBorg> old binaries left on arm64: linux-headers-4.4.0-1080-snapdragon, linux-image-4.4.0-1080-snapdragon, linux-snapdragon-headers-4.4.0-1080, linux-snapdragon-tools-4.4.0-1080, linux-tools-4.4.0-1080-snapdragon (from 4.4.0-1080.85)
[15:11] <apw> LocutusOfBorg, indeed, they would have appeared in the last hour or so, i'll sort them out
[15:12] <LocutusOfBorg> also raspi2 needs it :)
[15:13] <LocutusOfBorg> btw the new mainline vboxvideo seems to work great
[15:32] -queuebot:#ubuntu-release- Unapproved: sysstat (artful-proposed/main) [11.5.7-1ubuntu1 => 11.5.7-1ubuntu2] (kubuntu, ubuntu-server)
[15:33] -queuebot:#ubuntu-release- Unapproved: sysstat (zesty-proposed/main) [11.4.3-1 => 11.4.3-1ubuntu1] (kubuntu, ubuntu-server)
[15:37] -queuebot:#ubuntu-release- Unapproved: sysstat (xenial-proposed/main) [11.2.0-1ubuntu0.1 => 11.2.0-1ubuntu0.2] (kubuntu, ubuntu-server)
[15:37] <slashd> dgadomski, ^
[16:43] <LocutusOfBorg> cpaelzer, uploading curl, the current one won't easily migrate soon
[16:56] <cpaelzer> really
[16:56] <cpaelzer> ok LocutusOfBorg
[16:56] <cpaelzer> I decoupled apache anyway so it is not dpeending on each other
[16:57] <cpaelzer> the tests no more need the enabled curl
[16:57] <cpaelzer> and the MIR is done, so you won't hit the component mismatch
[16:57] <LocutusOfBorg> I see apache is good yes
[16:57] <cpaelzer> LocutusOfBorg: and btw fro libvirt - target is 3.11 wihch released mid Jan
[16:58] <cpaelzer> I'll play with 3.10 which released like a few days ago, but just to work with qemu 2.11 which releases next week
[16:58] <cpaelzer> this is all intertwined and none works well without the other
[16:58] <cpaelzer> but TL;DR it is under control :-)
[17:11] -queuebot:#ubuntu-release- New binary: libical3 [ppc64el] (bionic-proposed/none) [3.0.1-1] (no packageset)
[17:12] <LocutusOfBorg> thanks, the python binding is dep-waiting on it, this is why I care
[17:12] <LocutusOfBorg> btw, speaking on qemu, let me ask a question
[17:12] -queuebot:#ubuntu-release- New binary: libical3 [amd64] (bionic-proposed/none) [3.0.1-1] (no packageset)
[17:13] <LocutusOfBorg> long short story: pbuilder-dist bionic arm64 create fails since artful or so
[17:13] <LocutusOfBorg> somewhat it can't install bash, and fails there
[17:13] <LocutusOfBorg> same command, works with sid
[17:14] <LocutusOfBorg> cpaelzer, did you ever experienced that?
[17:14] -queuebot:#ubuntu-release- New binary: libical3 [i386] (bionic-proposed/none) [3.0.1-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: libical3 [s390x] (bionic-proposed/none) [3.0.1-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: libical3 [arm64] (bionic-proposed/none) [3.0.1-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: libical3 [armhf] (bionic-proposed/none) [3.0.1-1] (no packageset)
[17:20] <LocutusOfBorg> W: Failure while unpacking required packages.  This will be attempted up to five times.
[17:20] <LocutusOfBorg> W: See //debootstrap/debootstrap.log for details (possibly the package /var/cache/apt/archives/bash_4.4-5ubuntu1_arm64.deb is at fault)
[17:23] <LocutusOfBorg> this is a paste http://paste.ubuntu.com/26140607/ of the file
[18:44] -queuebot:#ubuntu-release- New: accepted libical3 [amd64] (bionic-proposed) [3.0.1-1]
[18:44] -queuebot:#ubuntu-release- New: accepted libical3 [armhf] (bionic-proposed) [3.0.1-1]
[18:44] -queuebot:#ubuntu-release- New: accepted libical3 [ppc64el] (bionic-proposed) [3.0.1-1]
[18:44] -queuebot:#ubuntu-release- New: accepted libical3 [arm64] (bionic-proposed) [3.0.1-1]
[18:44] -queuebot:#ubuntu-release- New: accepted libical3 [s390x] (bionic-proposed) [3.0.1-1]
[18:44] -queuebot:#ubuntu-release- New: accepted libical3 [i386] (bionic-proposed) [3.0.1-1]
[18:51] <doko> please could somebody override the falcon/s390x autopkg test? it's always-failed on the other archs, not sure why it succeeded on s390x. or maybe better mark it as always-failed for s390x
[19:01] <jbicha> similar for pinentry/s390x
[19:10] <doko> now disabled the test in falcon, was disabled in the package build as well
[19:18] <slangasek> jbicha: the pinentry/s390x test regression does not appear to have happened as part of the move from lxd to kvm; I don't think this looks appropriate to override
[19:18] <jbicha> it's not appropriate for it to block gtk2 either, right?
[19:19] <slangasek> jbicha: you can trigger a baseline re-test of pinentry against the release pocket to show that it's not a regression in -proposed
[19:20] <jbicha> it feels odd for a test that doesn't pass on amd64 to block migration…
[19:20] <slangasek> ah
[19:20] <slangasek> pinentry fails on all kvm archs and only passes on lxd archs?
[19:21] <slangasek> ok, I overlooked that specialness
[19:22] <jbicha> oh, that's a neat trick :|
[19:22] <slangasek> spectacularly lame that a tty-related test would work in a container and fail on a host
[19:22] <slangasek> ok, overriding
[19:22] <jbicha> thanks
[20:04] -queuebot:#ubuntu-release- Unapproved: resolvconf (zesty-proposed/main) [1.79ubuntu4 => 1.79ubuntu4.1] (core)
[20:18] <acheronuk> slangasek:  Could you please 'force-badtest kdepim-runtime/all/ppc64el kdepim-runtime/all/s390x' ?
[20:19] <acheronuk> another that wants to run tests on those architectures against itself despite no binaries building
[20:19] <acheronuk> ^^^^ that should make the last of PIM migrate
[20:31] <slangasek> acheronuk: done
[20:31] <slangasek> coreycb: this neutron SRU is missing paperwork on LP: #1731595; test case, regression potential
[20:31] <ubot5> Launchpad bug 1731595 in neutron (Ubuntu Zesty) "L3 HA: multiple agents are active at the same time" [High,Triaged] https://launchpad.net/bugs/1731595
[20:32] <slangasek> bdmurray: ^^ though I see you accepted it into artful-proposed without?
[20:33] <coreycb> slangasek: filling that in now
[20:34] <bdmurray> Oh, I thought I'd added a comment about accepting it but needing that info
[20:39] <coreycb> slangasek: bdmurray: updated with SRU details. thanks.
[20:39] <slangasek> bdmurray: "never read the comments" ;-)
[20:42] <slangasek> coreycb: nova is uploaded with the wrong -v option, -0ubuntu4.2 is not accepted into the archive but -0ubuntu4.3 doesn't include the link to LP: #1692397 in its .changes file; rejecting, this will need a reupload
[20:42] <ubot5> Launchpad bug 1692397 in nova (Ubuntu Xenial) "hypervisor statistics could be incorrect" [Low,Triaged] https://launchpad.net/bugs/1692397
[20:42] <slangasek> coreycb: also, it's unclear why this wasn't simply uploaded as 4.2, there is no 4.2 anywhere in LP's history
[20:42] <coreycb> slangasek: yeah that was a mistake. the old version was in the queue for a while and forgotten.
[20:43] <coreycb> slangasek: i'll fix that up
[20:43] <slangasek> ok
[20:44] -queuebot:#ubuntu-release- Unapproved: rejected nova [source] (xenial-proposed) [2:13.1.4-0ubuntu4.3]
[20:52] -queuebot:#ubuntu-release- Unapproved: nova (xenial-proposed/main) [2:13.1.4-0ubuntu4.1 => 2:13.1.4-0ubuntu4.2] (openstack, ubuntu-server)
[20:54] <coreycb> slangasek: i've uploaded a new nova to xenial
[20:55] <slangasek> thanks, will re-review shortly
[20:55] <coreycb> slangasek: thanks much
[21:09] <acheronuk> slangasek: thank you
[21:25] <slangasek> coreycb: ah; and what about LP: #1736149? seems there is already an openstack in zesty-proposed, awaiting verification
[21:25] <ubot5> Launchpad bug 1736149 in nova (Ubuntu Zesty) "[SRU] ocata stable releases" [Undecided,Fix committed] https://launchpad.net/bugs/1736149
[21:34] <coreycb> slangasek: i'm on a roll here :/
[21:34] <slangasek> coreycb: sorry, I blindly paged through that warning message when I reviewed it earlier, I should've flagged it to you the first time around
[21:34] <coreycb> slangasek: could we replace the version in proposed with the new one?
[21:36] <coreycb> slangasek: probably not, they'd need to have the bugs referenced in the same version of the changelog
[21:37] <slangasek> coreycb: you could upload /nova/ with -v, and then do the SRU verification of 1736149 and the new bug at the same time
[21:37] <slangasek> coreycb: but that only makes us happy if the SRU verification actually takes place
[21:40] <coreycb> slangasek: i think i'll just verify the one that is in proposed and that will be 7 days in proposed on monday at which point we could promote it to updates and accept the new one
[21:42] <slangasek> ok
[23:13] -queuebot:#ubuntu-release- New binary: polyml [i386] (bionic-proposed/universe) [5.7.1-1] (no packageset)
[23:13] -queuebot:#ubuntu-release- New binary: polyml [s390x] (bionic-proposed/universe) [5.7.1-1] (no packageset)
[23:13] -queuebot:#ubuntu-release- New binary: polyml [ppc64el] (bionic-proposed/universe) [5.7.1-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: polyml [amd64] (bionic-proposed/universe) [5.7.1-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: polyml [arm64] (bionic-proposed/universe) [5.7.1-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: polyml [armhf] (bionic-proposed/universe) [5.7.1-1] (no packageset)