[06:59] <LocutusOfBorg> uim is fixed, rebuilds issued
[06:59] <LocutusOfBorg> thanks doko for accepting them :)
[07:01] <LocutusOfBorg> can we please have freecad ignored on ppc64el and s390x? it is regressed in release since long time autopkgtest for freecad/0.16.6712+dfsg1-1build1: amd64: Pass, armhf: Always failed, i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻
[08:33] <LocutusOfBorg> apw, good morning, I syncd python-pathspec (from Debian). The ubuntu package was providing python-pathspec and python3-pathspec, the Debian one just provides the python3 binding. Do we need some NBS cleanup?
[08:43] <apw> LocutusOfBorg, perhaps indeed
[08:49] <LocutusOfBorg> thanks for having a look :)
[08:52] <LocutusOfBorg> hurray! yamllint finally fixed :)
[08:52]  * LocutusOfBorg looks hard at the transition :)
[10:06] -queuebot:#ubuntu-release- New binary: foolscap [amd64] (bionic-proposed/universe) [0.13.0-0ubuntu1] (no packageset)
[10:07] -queuebot:#ubuntu-release- New: accepted foolscap [amd64] (bionic-proposed) [0.13.0-0ubuntu1]
[10:10] <Laney> apw: slangasek: infinity: FYI autopkgtest-cloud-worker/3 is the new controller
[10:11] <apw> Laney, ack
[10:11] <Laney> if you want to rescue something off /0, do it today please because I'm going to delete it tomorrow
[10:11] <apw> Laney, have nothing on it that i know of
[10:12] <Laney> apw-banking-passwords.txt
[10:12] <xnox> lol
[10:12]  * Laney should extract some things from bash history
[10:17] <ginggs> apw would you bump the freecad hints for ppc64el and s390x to 0.16.6712+dfsg1-1build1 please?
[10:23] <ginggs> also, would you please consider ' force-badtest python-scipy/0.19.1-1ubuntu1/i386' it looks like precisions errors, but the tests pass for me in an i386 VM running bionic-proposed so i cannot test a patch
[10:29] <xnox> infinity, was https://launchpad.net/ubuntu/+source/diaspora-installer/+publishinghistory demoted to proposed incorrectly, managed to migrate this morning, blocking up postgresql/icu transition now. Could it be RM from the archive again?
[10:32] <LocutusOfBorg> infinity, https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/8503388/+listing-archive-extra if you want to take it (I'm interested in maven and qt5 fixes)
[10:33] <LocutusOfBorg> sigh libxml2...
[10:33] <LocutusOfBorg> CVE fixes out there but a lot of tests
[10:39] <apw> ginggs, hints kicked down the road some more, not had a achnage to look ath python-scipy
[10:39] <ginggs> apw: thanks
[10:41] <doko> apw: can pglogical be made expected to fail on armhf too? it's currently the only architecture where tests are not ignored
[10:44] <LocutusOfBorg> apw, as said, i386 is not a thing, and tests are just too flaky there, we never caught a regression on i386, but always patched tests to make it pass (by relaxing the bounds)
[10:45] <LocutusOfBorg> so, ignoring here is really something nice to do, and probably the new release is fine again, even if we don't want it right now (because it triggers a ton of stuff)
[10:45] <LocutusOfBorg> having them candidate will make more readable the britney output
[10:50] <Laney> LocutusOfBorg: If you're not going to use the results, why bother running the tests?
[10:52] <LocutusOfBorg> Laney, because we don't want to diverge more from Debian
[10:52] <LocutusOfBorg> and yes, we use them, and we decide if they are a bug in testsuite or a bug in code
[10:52] <LocutusOfBorg> I'm asking to ignore this specific version, not it forever
[10:53] <doko> xnox: diaspora-installer removed again
[10:53] <xnox> doko, thanks.
[10:53] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice-l10n [source] (artful-proposed) [1:5.4.2-0ubuntu0.17.10.1]
[10:53] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [source] (artful-proposed) [1:5.4.2-0ubuntu0.17.10.1]
[10:54] <Laney> LocutusOfBorg: That last statement doesn't sound the same as "i386 is not a thing"
[10:57] <LocutusOfBorg> I mean, what is the purpose of fixing a testsuite that fails from time to time, only on i386 by relaxing test bounds
[10:57] <Laney> I know what you mean, so why run it on i386 at all?
[10:58] <LocutusOfBorg> ask Debian, I hate deltas :)
[10:58] <Laney> please do
[10:58] <LocutusOfBorg> I don't even remember how to ignore it in one specific architecture lol
[10:59] <Laney> I hate multiple people having to spend their scarce time unproductively
[11:01] <LocutusOfBorg> Laney, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758022
[11:01] <LocutusOfBorg> seems the bug is there since only 3 years
[11:01] <xnox> LocutusOfBorg, still fresh =)
[11:02] <LocutusOfBorg> for debian ages, it is like "yesterday" :)
[11:02]  * LocutusOfBorg tries to disable testsuite on i386
[11:06] <doko> sil2100: "Grouped with PPA ~ci-train-ppa-service/+archive/ubuntu/3033" does this have any effect on migrations?
[11:21] <apw> doko, yes, it means that all of the things from that place need to get ready together before they migrate
[11:22] <doko> apw: does this include exact versions?
[11:23] <apw> doko, now i don't think i know the answer to that ... it could easily be floppy
[11:26] <doko> Laney: ^^^
[11:26] -queuebot:#ubuntu-release- New: rejected calamares-settings-ubuntu [source] (bionic-proposed) [1]
[11:26] <doko> just asking because some of these packages were updated again
[11:27] <doko> tsimonq2: ^^^ rejected, missing copyright holder
[11:27] <doko> tsimonq2: also some of the files are at least GPLv3, not v2
[11:41] <Laney> doko: I'm not sure, that was a robru thing
[11:42] <Laney> https://git.launchpad.net/~ubuntu-release/britney/+git/britney2-ubuntu/tree/britney2/policies/sourceppa.py
[11:43] <Laney> I think that probably you can search for the grouped PPA and any packages listed need to be candidates at the same time
[11:43] <Laney> in excuses
[11:43] <doko> output?
[11:44] <Laney> what?
[11:44] <doko> update_output?
[11:44] <Laney> what about it?
[11:45] <doko> libreoffice/1:5.4.1-0ubuntu3
[11:45] <doko> bahh, pasting not working
[11:45] <doko> what you said above: "in excused"  ?
[11:46] <Laney> that's where you see those Grouped by xxxxxxx things
[11:46] <sil2100> doko: I don't have much knowledge about this, never used it or worked on it
[12:09] <slashd> o/ sil2100 good Monday, could you please release cups in artful-updates for (LP: #1729910) ?
[12:09] <slashd> dgadomski, ^
[12:11] <sil2100> slashd: hey! Sure, let me take a look at it once I'm done with kernels
[12:11] <slashd> sil2100, ok thanks ;)
[12:13] <LocutusOfBorg> how to disable testsuite on a specific architecture? Laney ^
[12:15] <Laney> LocutusOfBorg: I don't know of a better way than looking at the architecture using dpkg-architecture or something
[12:16] <cjwatson> I'd use dpkg --print-architecture to avoid the dpkg-dev dependency, but yes
[12:16] <acheronuk> dpkg-architecture -e i386 && exit 0
[12:17] <acheronuk> I think?
[12:18] <cjwatson> again, that depends on dpkg-dev which isn't necessarily sensible in a testsuite
[12:18] <Laney> Sure
[12:18] <cjwatson> [ "$(dpkg --print-architecture)" = i386 ]
[12:18] <acheronuk> point taken
[12:21] -queuebot:#ubuntu-release- New: rejected hibagent [source] (bionic-proposed) [1.0.1-0ubuntu1]
 doko: hint just needs updating? https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/2652
[12:57] <doko> Laney: any reason about the limited set of versions?
[13:12] <LocutusOfBorg> so, you mean inside the test, not in the test/control file
[13:18] <LocutusOfBorg> ginggs, maybe you want to try the patch? I'm not quite confortable in blindly uploading it and triggering a a lot of autopkgtests
[13:22] <ginggs> LocutusOfBorg: i thought blindly uploading was your thing :p  what patch do you want me to try?
[13:26] <acheronuk> can someone please ignore test fails for libkf5eventviews on ppc64el and s390x? binaries to test have not been buildable on those architectures since May (QtWebEngine), so it makes no sense to suddenly have the tests try to run now!
[13:28] <acheronuk> ^^^ same for akonadi-calendar
[13:28] <acheronuk> those 2 are spuriously blocking abi-compliance-checker
[13:31] <Laney> doko: Probably because we expected that kernel regression to not be around for many months
[13:31] <Laney> Feel free to change it
[13:31] <Laney> acheronuk: Someone manually requested those tests
[13:31] <Laney> and then people have been blindly retrying them for some reason
[13:31] <doko> Laney: I can't
[13:32] <Laney> ok
[13:39] <acheronuk> Laney: I think I may have retried one or two in error before I realised, but didn't make the initial wrong request as far as I can see. I recall a week ago meaning to mention they should not be rune, but with one thing and another I forgot to bring it up
[13:43] <LocutusOfBorg> [11:23:58] <ginggs> also, would you please consider ' force-badtest python-scipy/0.19.1-1ubuntu1/i386' it looks like precisions errors, but the tests pass for me in an i386 VM running bionic-proposed so i cannot test a patch
[13:43] <LocutusOfBorg> the one mentioned here :)
[13:43] <LocutusOfBorg> btw you can also run testsuite from ppa if you have one with the package published
[13:47] <Laney> acheronuk: It doesn't matter about the delay - that someone requested it in the first place, and then people kept on retrying afterwards without reading the log ... yeah, to me that's a bit of a problem
[13:47] <Laney> laney@snakefruit:/home/ubuntu-archive/proposed-migration/log/bionic$ zgrep -e "Requesting.*akonadi-calendar.*(s390x|ppc64el)" 2017-11-*/*.gz
[13:47] <Laney> laney@snakefruit:/home/ubuntu-archive/proposed-migration/log/bionic$
[13:52] <Laney> anyways, added the hint for the current versions
[13:54] <doko> Laney: please could you ignore the python-scipy/i386 fail triggered by python-numpy? I'd like to avoid a new upload and triggering autopkg tests again
[13:54] <Laney> I'm doing something else now, sorry, maybe someone else can help you (ap_w mentioned that one earlier I think)
[13:56] <doko> apw: ^^^
[14:02] <bdrung> doko, as you probably saw, i fixed the build failure of rdma-core on armhf
[14:03] <doko> bdrung: you probably saw that it needs promotion
[14:03] <bdrung> yes
[14:04] <bdrung> anything that should be added from by side?
[14:12] <ginggs> doko: dropping freecad ppc64el and s390x binaries stills requires hinting :(
[14:12] <ginggs> same happens when debian stops running autopkgtests
[14:13] <ginggs> if they've passed once, they have to pass forever (or get hinted)
[15:03] -queuebot:#ubuntu-release- New source: hibagent (bionic-proposed/primary) [1.0.1-0ubuntu1]
[15:11] <slashd> thanks for cups sil2100
[15:16] <apw> doko, looking at python-scipy/i386
 doko: i *think* this patch to scipy will do it: https://paste.ubuntu.com/25998603/ - i can't test it because i can't reproduce the failure in my VM
[15:18] <doko> $ fgrep pglogical *
[15:18] <doko> adconrad:force-badtest pglogical/2.0.0-1
[15:19] <doko> add that one should be updated to 2.1.0-1
[15:20] <apw> python-scipy looks reasonable, applid
[15:20] <xnox> doko, yes please about pglogical.
[15:22] <apw> doko, pglogical done ...
[15:23] <doko> apw: and please remove the freecad ppc64el and s390x test results. the package is not built anymore on these archs
[15:25] <apw> trying to work out if i know how to do that :)
[15:25] <doko> well, or add an ignore for now
[15:30] <xnox> testing a fix for pgagent/ppc64el
[15:30] <xnox> and after that we need to kick out postgresql-mysql-fdw/2.3.0-1 and all should be well.
[15:30] <doko> xnox: is there a bug report for that?
[15:31] <xnox> doko, https://github.com/EnterpriseDB/mysql_fdw/issues/150
[15:31] <xnox> they added opportunistic support for 10.0, but it's not working with 10.1
[15:32]  * xnox opens a bug
[15:34] <xnox> apw, could you please remove postgresql-mysql-fdw, but keep the one in bionic-proposed around?
[15:34] <xnox> or like remove all of it all together? or hint a badtest?
[15:34] <xnox> https://bugs.launchpad.net/ubuntu/+source/postgresql-mysql-fdw/+bug/1733341
[15:34] <doko> I'll remove it
[15:39] <apw> doko, it seems they are only being tested because we had packages on those arches in -release at the time of the test
[15:39] <apw> doko, we can ignore those two now, and it should be fine next time round
[15:40] <doko> that should be sufficient for the current transitions, yes
[15:41] <apw> and hinted ... lets see if that does the do
[15:42] <doko> and now waiting for the just uploaded lo build :-/
[15:42] <Laney> is this the big migration?
[15:43] <doko> yes
[15:43] <doko> https://bugs.launchpad.net/ubuntu/+bug/1732742
[15:43] <Laney> nice work
[15:44] <doko> well, then at least we'll see what we are missing ...
[15:45] <doko> I fear there is more qt stuff
[15:45] <apw> doko, that is a beast, feels like half the archive
[15:46] -queuebot:#ubuntu-release- Unapproved: accepted util-linux [source] (artful-proposed) [2.30.1-0ubuntu4.1]
[15:49] <Laney> The following packages have unmet dependencies. libsaml9 : Depends: libxerces-c3.1 but it is not installable libxmltooling7 : Depends: libxerces-c3.1 but it is not installable
[15:49] <Laney> E: Unable to correct problems, you have held broken packages.
[15:49]  * Laney tries rebuilding those
[15:50] -queuebot:#ubuntu-release- New: accepted hibagent [source] (bionic-proposed) [1.0.1-0ubuntu1]
[15:50] <apw> is that "all" of the remaining brokeness ?
[15:50] <Laney> I'm not sure
[15:50] <Laney> I just looked at some random stuff on update_output_notest
[15:50] <Laney> most of it is liberoffice
[15:51]  * xnox has one more package to publish for postgresql-common - the pgagent fix, refreshing silo ppa to publish to then copy those into the archive
[15:51] <xnox> and publishing
[15:53] -queuebot:#ubuntu-release- New binary: hibagent [amd64] (bionic-proposed/none) [1.0.1-0ubuntu1] (no packageset)
[15:56] -queuebot:#ubuntu-release- New: accepted hibagent [amd64] (bionic-proposed) [1.0.1-0ubuntu1]
[16:56] -queuebot:#ubuntu-release- New source: hibagent (trusty-proposed/primary) [1.0.1-0ubuntu1~14.04.1]
[16:57] -queuebot:#ubuntu-release- New source: hibagent (xenial-proposed/primary) [1.0.1-0ubuntu1~16.04.1]
[17:07] -queuebot:#ubuntu-release- New: accepted hibagent [source] (xenial-proposed) [1.0.1-0ubuntu1~16.04.1]
[17:10] -queuebot:#ubuntu-release- New binary: hibagent [amd64] (xenial-proposed/none) [1.0.1-0ubuntu1~16.04.1] (no packageset)
[17:18] <xnox> Laney, apw - even thought postgresql-mysql-fdw got kicked out of bionic-release, it appears to still be londing up postgresql-common, can you badtest postgresql-mysql-fdw? it will need source fixes to get it working with postgresql-10 again.
[17:18] <xnox> autopkgtest for postgresql-mysql-fdw/2.3.0-1: amd64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
[17:18] <xnox> or maybe remove it from bionic-proposed too.
[17:18] <xnox> ..
[17:19] <xnox> retried pgagent with postgresql-common as trigger, should pass with the new pgagent.
[17:20] <apw> so we just want to ignore its tests for the moment, and block it in proposed so it doesn't migrate; then once teh rest does retun its tests and unblock it ?
[17:20] <xnox> apw, correct.
[17:20] <xnox> https://bugs.launchpad.net/ubuntu/+source/postgresql-mysql-fdw/+bug/1733341
[17:32] <apw> xnox, except nothing is depending on it ..
[17:38] <xnox> apw, i see postgresql-common triggering tests of postgresql-mysql-fdw, still, even after it was removed from -release. not sure if update_excuses is out of date, or buggy.
[17:39] <xnox> oh it's gone
[17:39] <apw> its not there now, i suspect since it has been removed in -release finally caught up
[17:39] <xnox> all is good =) i must have been looking at stale update_excuses.
[17:40] <xnox> pgagent is now green with postgresql-common; so maybe the next run will show us what's left for migration of doom.
[17:54] <xnox> boo, my retries did not make into this run either. hopefully next one then.
[17:59] <apw> xnox, there still seems to be pyqt junk on there
[18:12] -queuebot:#ubuntu-release- Unapproved: django-tastypie (xenial-proposed/universe) [0.12.0-1build1 => 0.13.3-1~16.04.1] (no packageset)
[18:21] <doko> Laney: is update-output-helper currently working for you?
[18:27] -queuebot:#ubuntu-release- Unapproved: ipxe (xenial-proposed/main) [1.0.0+git-20150424.a25a16d-1ubuntu1 => 1.0.0+git-20150424.a25a16d-1ubuntu1.2] (ubuntu-desktop, ubuntu-server)
[18:28] -queuebot:#ubuntu-release- Unapproved: nova (xenial-proposed/main) [2:13.1.4-0ubuntu4.1 => 2:13.1.4-0ubuntu4.2] (openstack, ubuntu-server)
[18:28] -queuebot:#ubuntu-release- Unapproved: ipxe (zesty-proposed/main) [1.0.0+git-20150424.a25a16d-1ubuntu2 => 1.0.0+git-20150424.a25a16d-1ubuntu2.1] (ubuntu-desktop, ubuntu-server)
[19:18] <tsimonq2> infinity: Any chance you're around?
[19:25] <infinity> tsimonq2: There's a chance.
[19:26] -queuebot:#ubuntu-release- New: accepted hibagent [amd64] (xenial-proposed) [1.0.1-0ubuntu1~16.04.1]
[19:27] <tsimonq2> infinity: Have you seen my MP to lp:ubuntu-cdimage?
[19:28] <tsimonq2> infinity: Lubuntu made a QA mistake and I'm wondering if it's at all possible to get new images for 17.10
[19:28] <doko> looks like I hadn't finished the xerces-c transition ...
[19:30] <tsimonq2> infinity: We missed LVM packages and UEFI packages because the share seed wasn't included.
[19:31] <LocutusOfBorg> doko, what is missing?
[19:31] <tsimonq2> infinity: (I'd like to know how to fix it)
[19:31] <infinity> tsimonq2: Yeah, I see that.  I'm not really a big fan of respinning a release a month after a release.
[19:34] <tsimonq2> infinity: Right, and neither am I. But I'm also getting annoyed at people poking me about it. Ofc they had to wait until after the release, but that's besides the point.
[19:34] <tsimonq2> The fix is simple but tedious.
[19:35] -queuebot:#ubuntu-release- New: accepted hibagent [source] (trusty-proposed) [1.0.1-0ubuntu1~14.04.1]
[19:36] <infinity> tsimonq2: Well, one thing at a time, I'll merge this and you can see if bionic looks how you think it should.
[19:37] <tsimonq2> infinity: Sure. Is there a delay between ubuntu-cdimage revisions being merged and actually being deployed?
[19:37] -queuebot:#ubuntu-release- New binary: hibagent [i386] (trusty-proposed/none) [1.0.1-0ubuntu1~14.04.1] (no packageset)
[19:38] <slangasek> only if the person merging doesn't follow up with deploying
[19:38] <Laney> doko: yes, but I might have some local modifications
[19:38] <doko> LocutusOfBorg: uploads done.
[19:38] <Laney> what's wrong with it for you?
[19:38] <doko> that seems to be open: http://autopkgtest.ubuntu.com/packages/r/ruby-em-http-request/bionic/amd64
[19:38] <doko> Laney: let me check
[19:39] <doko> is this a proxy problem?
[19:39] <tsimonq2> slangasek: ack
[19:39] <infinity> tsimonq2: What Steve says.  The delay is anywhere between seconds and "until the end of time", as it relies on a manual pull on nusakan.  But most of us remember that step. :P
[19:40] <doko> Laney: http://paste.ubuntu.com/26007342/
[19:41] <LocutusOfBorg> thanks doko, do you need some more work? I fail to see what is missing for the big one
[19:41] <infinity> tsimonq2: Done and done.
[19:47] <tsimonq2> infinity: And rebuilt. Thanks.
[19:49] <doko> LocutusOfBorg: see above, the ruby autopkg test failure
[19:52] <Laney> doko: here's my version http://paste.debian.net/996753/
[19:53] <Laney> poor connection atm, sorry
[19:54] <doko> Laney: yes that one works :)
[19:57] <doko> oSoMoN: LO build failure on amd64 :-/
[19:58] <doko> segfault in a unit test
[20:05] <doko> oSoMoN: I pasted the tail of the log, and gave it back. http://paste.ubuntu.com/26007473/
[20:22] <Schyken> Heyo
[20:26] <slangasek> xnox: yes, please stop using nested KVM with the next systemd upload, given its not-support status.
[20:56] <oSoMoN> doko, mmm, that's weird, thanks for retrying, let's see how it goes this time
[22:50] -queuebot:#ubuntu-release- New: accepted hibagent [i386] (trusty-proposed) [1.0.1-0ubuntu1~14.04.1]
[23:10] -queuebot:#ubuntu-release- Unapproved: fwupdate-signed (artful-proposed/main) [1.14ubuntu0.2 => 1.14.1] (core)
[23:10] -queuebot:#ubuntu-release- Unapproved: fwupdate-signed (zesty-proposed/main) [1.13ubuntu0.1 => 1.13.1] (core)
[23:42] <tsimonq2> infinity: Testers have confirmed that the tooling change fixed the problem.
[23:42] <tsimonq2> (in Bionic)
[23:43] <tsimonq2> infinity: Would you be able to spin up some 17.10 ISOs for us to test the changes?
[23:43] <xnox> slangasek, ok, i will force not using nested kvm, but the defaults should be changed too, nonetheless. Currently it checks of the presence of /dev/kvm but makes use of it, if found, but it doesn't itself load kvm modules and/or specifies kvm.nesting=1 at all.
[23:44] <slangasek> xnox: ah, of course; makes sense, and yes I agree the default should be changed, I think cpaelzer is planning to follow up on that
[23:44] <xnox> slangasek, i will add an etra check to systemd-virt-detect --vm and thus ignore /dev/kvm presense (* unless z/vm, cause althought that's nested virtualisation, it's not linux-kvm-nesting)
[23:44] <xnox> cpaelzer, ^^^
[23:45] <tsimonq2> infinity: Also, irt naming, would they be called 17.10.1 or would they overwrite the existing ISO?