[05:11] -queuebot:#ubuntu-release- New binary: x265 [s390x] (bionic-proposed/universe) [2.6-2] (kubuntu)
[05:12] -queuebot:#ubuntu-release- New binary: writerperfect [amd64] (bionic-proposed/universe) [0.9.5-2] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: writerperfect [s390x] (bionic-proposed/universe) [0.9.5-2] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: writerperfect [ppc64el] (bionic-proposed/universe) [0.9.5-2] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: x265 [i386] (bionic-proposed/universe) [2.6-2] (kubuntu)
[05:12] -queuebot:#ubuntu-release- New binary: writerperfect [i386] (bionic-proposed/universe) [0.9.5-2] (no packageset)
[05:13] -queuebot:#ubuntu-release- New binary: x265 [arm64] (bionic-proposed/universe) [2.6-2] (kubuntu)
[05:13] -queuebot:#ubuntu-release- New binary: x265 [ppc64el] (bionic-proposed/universe) [2.6-2] (kubuntu)
[05:13] -queuebot:#ubuntu-release- New binary: x265 [armhf] (bionic-proposed/universe) [2.6-2] (kubuntu)
[05:13] -queuebot:#ubuntu-release- New binary: x265 [amd64] (bionic-proposed/universe) [2.6-2] (kubuntu)
[05:14] -queuebot:#ubuntu-release- New binary: writerperfect [arm64] (bionic-proposed/universe) [0.9.5-2] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: writerperfect [armhf] (bionic-proposed/universe) [0.9.5-2] (no packageset)
[05:49] <wxl> slangasek: tsimonq2 had me cherry pick a patch from upstream in the bionic kdepim-runtime in order to fix autopkgtests, apparently by your suggestion. looks like it fixed 1 of 2 failing tests, but do you have any suggestions regarding the second?
[05:49] <wxl> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/k/kdepim-runtime/20171207_053307_20e20@/log.gz
[06:33] <slangasek> wxl: not specifically, but I would wonder about that test being racy since it's a client-server test, and retry it
[06:38] <wxl> slangasek: alright, i'll see if tsimonq2 has any ideas.
[07:13] -queuebot:#ubuntu-release- New: accepted go-dep [amd64] (bionic-proposed) [0.3.2-2]
[07:13] -queuebot:#ubuntu-release- New: accepted go-dep [armhf] (bionic-proposed) [0.3.2-2]
[07:13] -queuebot:#ubuntu-release- New: accepted go-dep [ppc64el] (bionic-proposed) [0.3.2-2]
[07:13] -queuebot:#ubuntu-release- New: accepted go-dep [arm64] (bionic-proposed) [0.3.2-2]
[07:13] -queuebot:#ubuntu-release- New: accepted go-dep [s390x] (bionic-proposed) [0.3.2-2]
[07:13] -queuebot:#ubuntu-release- New: accepted go-dep [i386] (bionic-proposed) [0.3.2-2]
[07:14] -queuebot:#ubuntu-release- New: accepted writerperfect [amd64] (bionic-proposed) [0.9.5-2]
[07:14] -queuebot:#ubuntu-release- New: accepted writerperfect [armhf] (bionic-proposed) [0.9.5-2]
[07:14] -queuebot:#ubuntu-release- New: accepted writerperfect [ppc64el] (bionic-proposed) [0.9.5-2]
[07:14] -queuebot:#ubuntu-release- New: accepted writerperfect [arm64] (bionic-proposed) [0.9.5-2]
[07:14] -queuebot:#ubuntu-release- New: accepted writerperfect [s390x] (bionic-proposed) [0.9.5-2]
[07:14] -queuebot:#ubuntu-release- New: accepted writerperfect [i386] (bionic-proposed) [0.9.5-2]
[07:15] -queuebot:#ubuntu-release- New: accepted willow [amd64] (bionic-proposed) [1.1-2]
[07:15] -queuebot:#ubuntu-release- New: accepted x265 [arm64] (bionic-proposed) [2.6-2]
[07:15] -queuebot:#ubuntu-release- New: accepted x265 [i386] (bionic-proposed) [2.6-2]
[07:15] -queuebot:#ubuntu-release- New: accepted x265 [s390x] (bionic-proposed) [2.6-2]
[07:15] -queuebot:#ubuntu-release- New: accepted x265 [amd64] (bionic-proposed) [2.6-2]
[07:15] -queuebot:#ubuntu-release- New: accepted x265 [ppc64el] (bionic-proposed) [2.6-2]
[07:15] -queuebot:#ubuntu-release- New: accepted x265 [armhf] (bionic-proposed) [2.6-2]
[08:02] <cpaelzer> slangasek: http://autopkgtest.ubuntu.com/packages/casync all green on bionic now :-)
[08:18] <acheronuk> slangasek: that kdepim-runtime akonadi_sqlite_pop3test is failing for some time now on KDE's own CI tests, with no fix yet I can see
[09:52] <LocutusOfBorg> cpaelzer, ping for the MIR?
[10:06] <cpaelzer> hi LocutusOfBorg
[10:07] <cpaelzer> still a block on systemd autopkgtest
[10:07] <cpaelzer> I'm testing the MIR from a ppa and the actual change looks good
[10:07] <cpaelzer> it is more to get former curl out of the way
[10:09] <cpaelzer> a rerun is in the queue - the issue certainly isn't due to curl
[10:09] <cpaelzer> we can ask for an override here as well, but I usually prefer to get it green if a rerun does it
[10:11] <cpaelzer> LocutusOfBorg: I see your trigger of the same even is in the queue above me
[10:12] <cpaelzer> It seems the tests atm take quite long and the queue is full of retriggers for it
[10:12] <cpaelzer> I also see slangasek for adduser&lsb just as you a bit down the queue as well
[10:13] <cpaelzer> as a glimpse of hope at least casync tests fine now :-)
[10:18] <LocutusOfBorg> yep, I want it migrate too
[10:18] <LocutusOfBorg> but I don't want to enable nghttp2 before it gets promoted
[10:19] <LocutusOfBorg> this is why I'm asking: can you please promote so I can push once it goes in release?
[10:19] <LocutusOfBorg> btw the new release is just about bugfixes, so maybe we can upload it only once?
[10:19] <LocutusOfBorg> I have a merge ready in my ppa btw
[10:19] <cpaelzer> for curl you mean?
[10:19] <LocutusOfBorg> yep
[10:19] <LocutusOfBorg> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/8550553/+listing-archive-extra
[10:20] <cpaelzer> I thought it bumped libcurl-gnutls from 4.4 to 4.5 and was unsure if that means a huge rebuild excercise
[10:20] <LocutusOfBorg> with a libssh2 MIR we can sync
[10:20] <cpaelzer> I can't provide that
[10:20] <LocutusOfBorg> https://launchpadlibrarian.net/348311136/curl_7.55.1-1ubuntu2.1_7.57.0-1ubuntu1.diff.gz
[10:20] <LocutusOfBorg> there is no bump, at least to my diff
[10:20] <cpaelzer> I have tested enabling http2 in curl (and apache) and it works for curl fine in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3070/+packages
[10:20] <cpaelzer> I had the merge in my ppa and it changed the version
[10:21] <cpaelzer> but I deletde and stepped back to just enabling http2 so I have no logs anymore since LP cleans them
[10:21] <cpaelzer> the mir for http2 is https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1687454
[10:21] <LocutusOfBorg> yep I know the mir
[10:21] <cpaelzer> feel free to combine the enabling with your merge
[10:21] <cpaelzer> I agree that one upload is better than two
[10:21] <LocutusOfBorg> I already did it :)
[10:21] <cpaelzer> thanks
[10:22] <cpaelzer> yet for any of that we would want the former one to promote
[10:22] <LocutusOfBorg> I mean, it was "removing some delta from debian" rather than enabling stuff
[10:22] <cpaelzer> and I have no powers to do so
[10:22] <LocutusOfBorg> oh ok
[10:23] <LocutusOfBorg> BTW the curl currently in bionic seems just wrong
[10:23] <LocutusOfBorg>  # do not add patches below and then CVE-2017-1000254.patch
[10:23] <LocutusOfBorg> cpaelzer, can you please test the curl in my ppa?
[10:24] <cpaelzer> on the merge you drop 1000254 anyway
[10:24] <cpaelzer> sure, I can use your ppa for my tests with enabling apache2
[10:24] <LocutusOfBorg> oh actually the Ubuntu3 is fine http://launchpadlibrarian.net/347530733/curl_7.55.1-1ubuntu2.1_7.55.1-1ubuntu3.diff.gz
[10:24] <cpaelzer> I have seen the reshuffle
[10:28] <cpaelzer> LocutusOfBorg: I know - I really had a merge ready https://git.launchpad.net/~paelzer/ubuntu/+source/curl?h=lp1687454-bionic-merge
[10:28] <cpaelzer> LocutusOfBorg: until I saw the so bump, let me check your ppa for that one
[10:31] <LocutusOfBorg> I can see new symbols, yes
[10:31] <LocutusOfBorg> but no old symbols changed, and no soname bump
[10:32]  * LocutusOfBorg has always the feeling to get the ABI changes wrong, so he is surely wrong here
[10:32] <cpaelzer> oh well, I didn't go into that detail
[10:32] <cpaelzer> but that is good to be confirmed
[10:32] <LocutusOfBorg> I looked at debian/control and no bump, and libcurl3-gnutls.symbols shows a lot of "+" but no "-" :)
[10:32] <LocutusOfBorg> if you confirm, I upload once britney lets this one go
[10:36] <cpaelzer> well dh_makeshlibs doesn't punch you in your build and it would otherwise
[10:36] <cpaelzer> so ok
[10:38] <cpaelzer> LocutusOfBorg: do you know - can we overrride systemd just for curl?
[10:39] <cpaelzer> or would that unblock all of the others as well - of wich some might want to sort something out?
[10:41] <LocutusOfBorg> xnox, ^^^
[10:41] <LocutusOfBorg> maybe we can wait for the current tests to finish and see what happened
[12:15] <cjwatson> jamespage: I imagine these were just boilerplate messages on bug 1736454, but FWIW I am not likely to have time to test this for the cloud archive
[12:16] <jamespage> cjwatson: yep - I've got those covered
[12:16] <cjwatson> cool
[12:58] <cpaelzer> LocutusOfBorg: the last two systemd tests (those re-triggered by slangasek) failed due to bug 1730717
[12:59] <cpaelzer> I hade hoped if those go well they give us confidence to epxect a pass once your trigger of it for curl hits the top of the queue
[12:59] <cpaelzer> Laney: you recycled workers for this right ? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20171206_035945_add64@/log.gz
[12:59] <cpaelzer> any need to poke somebody to do so?
[13:00] <cpaelzer> or is that done on a regular base anyway?
[13:01] <Laney> not me, Steve did I think, and no it's not done automatically
[13:01] <Laney> no good way to tell that from a real failure
[13:02] <Laney> join us in praying for that bug to be fixed soon
[13:03] <Laney> well I guess we could add some code to find that string in the log and reject the result
[13:36] -queuebot:#ubuntu-release- Unapproved: neutron (zesty-proposed/main) [2:10.0.4-0ubuntu1 => 2:10.0.4-0ubuntu2] (openstack, ubuntu-server)
[14:26] <ahasenack> hi guys, systemd has a failing dep8 test on s390 which was fixed in bionic: https://git.launchpad.net/~usd-import-team/ubuntu/+source/systemd/commit/?id=bc28ba569ef1ecdbc028512dd24b32907212e5cc
[14:26] <ahasenack> but not in artful
[14:26] <ahasenack> I have an iproute2 SRU migration failing in artful because of this (and other packages, but I'm debugging this one now)
[14:26] <ahasenack> here is the systemd autopkg test history on artful/s390: http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x
[14:27] <ahasenack> it started to fail when the s390 tests started to run in a vm, which liberated that particular systemd-fsck test to finally run instead of being skipped
[14:27] <ahasenack> what's usually done in such a case? mark it as always-fail? sru the dep8 fix?
[14:38] <ahasenack> I filed a bug about this particular case, tasking artful: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1736955
[14:39]  * ahasenack -> lunch
[15:29] <smb> Is someone working on adt queue/workers for artful/arm64? There are two tests which claim to be running (without runtime changing) and right now the queue appears to be no longer there. Which is not that bad as alot of it was me hitting retry
[15:29] <Laney> The images have disappeared, and I reported a ticket to IS to get it fixed
[15:31] <smb> oh dear.... thanks
[16:06] -queuebot:#ubuntu-release- Packageset: Added linux-azure-edge to kernel in bionic
[16:06] -queuebot:#ubuntu-release- Packageset: Added linux-euclid to kernel in bionic
[16:06] -queuebot:#ubuntu-release- Packageset: Added linux-meta-azure-edge to kernel in bionic
[16:06] -queuebot:#ubuntu-release- Packageset: Added linux-meta-euclid to kernel in bionic
[16:06] -queuebot:#ubuntu-release- Packageset: Added linux-meta-oem to kernel in bionic
[16:06] -queuebot:#ubuntu-release- Packageset: Added linux-oem to kernel in bionic
[16:06] -queuebot:#ubuntu-release- Packageset: Added linux-signed-oem to kernel in bionic
[16:06] -queuebot:#ubuntu-release- Packageset: Added linux-euclid to kernel in xenial
[16:06] -queuebot:#ubuntu-release- Packageset: Added linux-meta-euclid to kernel in xenial
[16:19] <Laney> om nom kernels
[17:01] <slangasek> acheronuk: if akonadi_sqlite_pop3test is a broken test, how about disabling the test?
[17:03] <acheronuk> slangasek: we are thinking of doing that. just doing some due diligence, as it actually looks a bit more broken in our runs than the upstream results.
[17:13] -queuebot:#ubuntu-release- New binary: brotli [ppc64el] (bionic-proposed/universe) [1.0.2-2] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: brotli [s390x] (bionic-proposed/universe) [1.0.2-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: node-locate-path [amd64] (bionic-proposed/none) [2.0.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: brotli [i386] (bionic-proposed/universe) [1.0.2-2] (no packageset)
[17:24] <ahasenack> hi, can someone please "force-badtest" (I think that's the term) the s390x systemd artful and zesty dep8 test, it has been failing since the s390x tests moved to a vm due to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1736955
[17:24] <ahasenack> it's fixed in bionic
[17:24] <ahasenack> s390x artful systemd tests: http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x
[17:24] <ahasenack> zesty: http://autopkgtest.ubuntu.com/packages/s/systemd/zesty/s390x
[17:24] -queuebot:#ubuntu-release- New binary: brotli [amd64] (bionic-proposed/universe) [1.0.2-2] (no packageset)
[17:30] -queuebot:#ubuntu-release- New binary: brotli [arm64] (bionic-proposed/universe) [1.0.2-2] (no packageset)
[17:30] -queuebot:#ubuntu-release- New binary: brotli [armhf] (bionic-proposed/universe) [1.0.2-2] (no packageset)
[17:32] -queuebot:#ubuntu-release- Unapproved: maas (trusty-proposed/main) [1.9.5+bzr4599-0ubuntu1~14.04.2 => 1.9.5+bzr4599-0ubuntu1~14.04.3] (ubuntu-server)
[18:03] <dpb1> rbasak: can you do what ahasenack is asking? ^
[18:48] -queuebot:#ubuntu-release- Unapproved: accepted libinput [source] (artful-proposed) [1.8.4-0ubuntu0.17.10.1]
[18:51] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (artful-proposed) [1.3+17.10ubuntu1]
[18:52] -queuebot:#ubuntu-release- New: accepted brotli [amd64] (bionic-proposed) [1.0.2-2]
[18:52] -queuebot:#ubuntu-release- New: accepted brotli [armhf] (bionic-proposed) [1.0.2-2]
[18:52] -queuebot:#ubuntu-release- New: accepted brotli [ppc64el] (bionic-proposed) [1.0.2-2]
[18:52] -queuebot:#ubuntu-release- New: accepted brotli [arm64] (bionic-proposed) [1.0.2-2]
[18:52] -queuebot:#ubuntu-release- New: accepted brotli [s390x] (bionic-proposed) [1.0.2-2]
[18:52] -queuebot:#ubuntu-release- New: accepted brotli [i386] (bionic-proposed) [1.0.2-2]
[18:52] -queuebot:#ubuntu-release- New: accepted node-locate-path [amd64] (bionic-proposed) [2.0.0-1]
[18:54] -queuebot:#ubuntu-release- Unapproved: accepted percona-xtradb-cluster-5.6 [source] (artful-proposed) [5.6.34-26.19-0ubuntu4.17.10.1]
[18:58] -queuebot:#ubuntu-release- Unapproved: accepted uvp-monitor [source] (artful-proposed) [2.2.0.316-0ubuntu1~17.10.1]
[19:05] -queuebot:#ubuntu-release- Unapproved: lxd (xenial-proposed/main) [2.20-0ubuntu4~16.04.1 => 2.0.11-0ubuntu1~16.04.3] (edubuntu, ubuntu-server)
[19:08] -queuebot:#ubuntu-release- Unapproved: accepted gnome-user-docs [source] (artful-proposed) [3.26.2.1-0ubuntu0.1]
[19:12] <stgraber> any sru person around (other than myself)?
[19:13] -queuebot:#ubuntu-release- Unapproved: rejected lxd [source] (xenial-proposed) [2.0.11-0ubuntu1~16.04.3]
[19:13] -queuebot:#ubuntu-release- Unapproved: lxd (xenial-proposed/main) [2.20-0ubuntu4~16.04.1 => 2.0.11-0ubuntu1~16.04.3] (edubuntu, ubuntu-server)
[19:13] <stgraber> we have a bit of an annoying regression in LXD 2.0.11 which we need fixed ASAP. The upload is about to hit the queue and I'm intending on releasing to -updates immediately after manual testing is done. ^
[19:15] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (zesty-proposed) [1.3+17.04ubuntu1]
[19:15] <stgraber> infinity, bdmurray, slangasek: any of you around who could do a quick review of that upload? (diff is small)
[19:17] <bdmurray> stgraber: just for xenial?
[19:17] <stgraber> bdmurray: yep, that's the only place where we have LXD 2.0.11
[19:18] <bdmurray> stgraber: I'll do it
[19:18] <stgraber> bdmurray: thanks!
[19:18] <stgraber> I'll test it on a clean system as soon as it's published
[19:28] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-proposed) [2.0.11-0ubuntu1~16.04.3]
[19:35] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (zesty-proposed) [3.22.7-0ubuntu3.17.04.8]
[19:43] <bdmurray> Can somebody fix perms on sru-review in the ubuntu-archive-tools tree?
[19:44] <stgraber> done
[19:49] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (xenial-proposed) [3.20.5-0ubuntu0.16.04.7]
[19:53] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.25]
[19:58] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (xenial-proposed) [1.3+16.04ubuntu1]
[20:00] <tsimonq2> infinity: Your kdepim-runtime armhf hint can be safely dropped. There are now no real differences in failures from other arches.
[21:18] <mwhudson> is there a good way to do upgrade testing in autopkgtest?
[21:21] <stgraber> bdmurray: looks like we'll have a follow-up fix, noticed another problem with lxd init while doing more testing... sorry
[21:21] <stgraber> bdmurray: running the upstream testsuite against that fix now, will push upstream and cherry-pick next
[21:25] -queuebot:#ubuntu-release- Unapproved: rejected nova [source] (xenial-proposed) [2:13.1.4-0ubuntu4.2]
[21:35] -queuebot:#ubuntu-release- Unapproved: lxd (xenial-proposed/main) [2.20-0ubuntu4~16.04.1 => 2.0.11-0ubuntu1~16.04.4] (edubuntu, ubuntu-server)
[21:35] -queuebot:#ubuntu-release- Unapproved: accepted iscsitarget [source] (trusty-proposed) [1.4.20.3+svn499-0ubuntu2.4]
[21:38] <stgraber> bdmurray: ready for review in the queue (queuebot seems a bit slow today)
[21:52] -queuebot:#ubuntu-release- Unapproved: networking-l2gw (artful-proposed/universe) [1:10.1.0~a2~git20170831.a8ae0e3-0ubuntu1 => 1:11.0.0-0ubuntu1] (no packageset)
[21:54] <ahasenack> autopkg test failures do not block migrations for srus?
[21:54] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-proposed) [2.0.11-0ubuntu1~16.04.4]
[21:54] <ahasenack> initramfs-tools has more reds than greens in http://people.canonical.com/~ubuntu-archive/proposed-migration/trusty/update_excuses.html, but it's in trusty-proposed
[21:55] <ahasenack> my iproute2 upload to trusty also has reds, but it's also in proposed already
[22:10] <cjwatson> well, firstly, -proposed is the source for migrations, not the target; tests don't generally happen at all until they're in -proposed
[22:11] <cjwatson> secondly, at the moment autopkgtest results are only informative to SRU team members deciding whether to promote SRUs to -updates, and don't block; although we've talked about changing that at various times in the past
[22:15] <rbasak> I was just about to look at force-badtest for ahasenack
[22:15] <rbasak> Though we can ignore the results
[22:24] <rbasak> Let's see if that works.
[22:24]  * rbasak hasn't done this before