[00:44] -queuebot:#ubuntu-release- Unapproved: vmdk-stream-converter (xenial-updates/universe) [0.2-1 => 0.2-1] (no packageset) (sync)
[00:45] -queuebot:#ubuntu-release- Unapproved: rejected vmdk-stream-converter [sync] (xenial-updates) [0.2-1]
[00:46] -queuebot:#ubuntu-release- Unapproved: accepted vmdk-stream-converter [sync] (xenial-updates) [0.2-1]
[01:05] -queuebot:#ubuntu-release- Unapproved: docker.io (artful-proposed/universe) [1.13.1-0ubuntu6 => 17.03.2-0ubuntu1~17.10.1] (no packageset)
[01:06] -queuebot:#ubuntu-release- Unapproved: docker.io (zesty-proposed/universe) [1.13.1-0ubuntu1~17.04.1 => 17.03.2-0ubuntu1~17.04.1] (no packageset)
[01:08] -queuebot:#ubuntu-release- Unapproved: docker.io (xenial-proposed/universe) [1.13.1-0ubuntu1~16.04.2 => 17.03.2-0ubuntu1~16.04.1] (no packageset)
=== s8321414_ is now known as s8321414
=== s8321414_ is now known as s8321414
[02:24] -queuebot:#ubuntu-release- Packageset: 188 entries have been added or removed
[05:12] <tjaalton> bdmurray: thanks for reviewing libdrm and libclc for xenial. the latter needs llvm-5 from the new queue, though
[05:56] <tjaalton> who's handling the libva transition and what is it's status?
[06:23] <nacc> tjaalton: https://people.canonical.com/~ubuntu-archive/transitions/html/libva.html ?
[06:23] <nacc> tjaalton: dunno if it's current, tbh
[06:32] <tjaalton> nacc: ok, maybe it's some other transition blocking that then
[06:39] <jamespage> doko: oh sorry I thought bileto would dtrt - I'll recheck those headers and upload directly
[06:41] <jamespage> doko: updated and re-uploaded directly to bionic NEW
[07:01] <jamespage> doko: oh I see you did another upload with the xtra copyright holders - thanks!
[07:39] <acheronuk> nacc: qtav depends qtdeclarative-abi-5-9-2? which is blocked with the Qt 5.9.2 transition
[07:39] <acheronuk> tjaalton I meant
[07:47] <tjaalton> acheronuk: ok
[08:28] <LocutusOfBorg> hello "Not copying packages in dry-run mode." does this mean somebody stopped autosync?
[08:28] <LocutusOfBorg> http://people.canonical.com/~ubuntu-archive/auto-sync/current.log
[08:31] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (xenial-proposed) [4.13.0-1008.9]
[08:48] <infinity> LocutusOfBorg: Yes, it's disabled for a bit so we don't accidentally add any more transitions to the current mess.
[08:48] <infinity> LocutusOfBorg: I hope this goes without saying, but please don't play manual autosync bot.  It'll catch up when we turn it back on.
[08:55] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-5.0 [source] (xenial-proposed) [1:5.0-3~16.04.1]
[08:56] -queuebot:#ubuntu-release- New: accepted libdrm [amd64] (xenial-proposed) [2.4.83-1~16.04.1]
[09:03] <Laney> slangasek: wendigo s390x.conf> no idea what that is, get rid of it
[09:04] <Laney> slangasek: ssh-setup> output from it seems to end up at the end of autopkgtest logs
[09:04] -queuebot:#ubuntu-release- Unapproved: accepted wayland-protocols [source] (xenial-proposed) [1.10-1~16.04.1]
[09:06] <Laney> slangasek: I think outputting the $OS_REGION_NAME from ssh-setup/nova would be good
[09:17] <LocutusOfBorg> sure infinity, maybe an email to the list would be appreciated, just to avoid people complaining about broken stuff?
[09:18] <LocutusOfBorg> for sure I'll sync only stuff that doesn't entangle and fixes issues :) and no, no new transitions
[09:22] <infinity> LocutusOfBorg: If by "fixes issues", you mean "fixes issues with the current set of packages trying to migrate", go nuts.
[09:23] <infinity> LocutusOfBorg: (And Steve was going to mail u-d-a, guess he forgot?)
[09:23] <LocutusOfBorg> of course, I don't want to start new transitions, e.g. right now I'm trying some hammer to fix qscintilla2 and make qt5 ready to go
[09:24] <infinity> Although, I argued for not mailing, so people wouldn't read the email and start doing exactly what it asked them not to (manual syncs).
[09:24] <LocutusOfBorg> somebody should debug ffmpeg on s390x :/
[09:24] <LocutusOfBorg> maybe if somebody ignores test results for python-scipy on i386 we get nearer
[09:25] <infinity> What's wrong with ffmpeg on s390x?
[09:25] <LocutusOfBorg> so far, what we do, is to relax the testsuite on i386 to make the test pass. but this is not a bug, upstream acked it
[09:25] <LocutusOfBorg> infinity, testsuite hangs or whatever
[09:25] <oSoMoN> doko, slangasek, seb128: there's a tentative upstream patch for building LO with ICU 60 at https://gerrit.libreoffice.org/#/c/44665/4/i18npool/source/breakiterator/breakiterator_unicode.cxx , I'll test it in a PPA and will keep you posted
[09:25] <LocutusOfBorg> infinity, http://autopkgtest.ubuntu.com/packages/f/ffmpeg/bionic/s390x
[09:25] <LocutusOfBorg> maybe a rebuild with -O2 might work, or whatever
[09:45] <seb128> oSoMoN, thanks
[09:58] -queuebot:#ubuntu-release- Unapproved: libsdl2 (zesty-proposed/universe) [2.0.5+dfsg1-2ubuntu3 => 2.0.5+dfsg1-2ubuntu3.17.04.1] (kubuntu)
[10:03] -queuebot:#ubuntu-release- New binary: llvm-toolchain-5.0 [s390x] (xenial-proposed/main) [1:5.0-3~16.04.1] (no packageset)
[10:07] -queuebot:#ubuntu-release- New binary: llvm-toolchain-5.0 [ppc64el] (xenial-proposed/main) [1:5.0-3~16.04.1] (no packageset)
[10:17] <doko> jamespage: yep, but please subscribe to the bug reports
[10:18] <jamespage> doko: ack
[10:18] <jamespage> doko: done
[10:59] -queuebot:#ubuntu-release- New binary: llvm-toolchain-5.0 [amd64] (xenial-proposed/main) [1:5.0-3~16.04.1] (no packageset)
[11:27] -queuebot:#ubuntu-release- New binary: llvm-toolchain-5.0 [powerpc] (xenial-proposed/main) [1:5.0-3~16.04.1] (no packageset)
[12:26] -queuebot:#ubuntu-release- New binary: llvm-toolchain-5.0 [i386] (xenial-proposed/main) [1:5.0-3~16.04.1] (no packageset)
[13:10] <Laney> hmm, I suppose switching to lxd for livefs build has broken https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/auto/config#L10
[13:10] <Laney> https://launchpadlibrarian.net/346132173/buildlog_ubuntu_bionic_amd64_ubuntu_BUILDING.txt.gz uses archive.u.c instead of ftpmaster
[13:15] <cjwatson> hmm, possibly
[13:15] <cjwatson> I thought we tried to inject the hostname though
[13:15] <Laney> it says "Building on lp-bionic-amd64"
[13:15] <Laney> printed a couple of lines up in auto/config from the line I linked to
[13:16] <cjwatson> ah, did it previously have .buildd on the end maybe?
[13:16] <cjwatson> actually have you checked whether this worked a few months back?  it's possible it was broken by starting to build in scalingstack
[13:16] -queuebot:#ubuntu-release- New source: hibagent (bionic-proposed/primary) [1.0.1-0ubuntu1]
[13:17] <Laney> yakkety's last build https://launchpadlibrarian.net/289351411/buildlog_ubuntu_yakkety_i386_ubuntu_BUILDING.txt.gz says "Building on lcy01-12.buildd"
[13:17] <Laney> is that good evidence?
[13:17] <cjwatson> reasonably
[13:17] <cjwatson> all right, can I have a bug on launchpad-buildd please?
[13:18] <Laney> okely dokely
[13:18] <cjwatson> ta
[13:21] <Laney> https://bugs.launchpad.net/launchpad-buildd/+bug/1732913
[13:22] <ubot5> Launchpad bug 1732913 in launchpad-buildd "livefs builds are using archive.ubuntu.com instead of ftpmaster.internal" [Undecided,New]
[13:29] <doko> Laney: looking at http://autopkgtest.ubuntu.com/running I see two binutils tests which seem to be finished, or is this transitional?
[13:32] -queuebot:#ubuntu-release- Unapproved: snapcraft (xenial-proposed/universe) [2.34 => 2.35] (no packageset)
[13:35] <Laney> doko: has it been stuck for a long time?
[13:35] <doko> I just noticed it, can't say
[13:36] <Laney> ok, well it does some more stuff after that so not quite finished yet
[13:49] -queuebot:#ubuntu-release- Unapproved: snapcraft (zesty-proposed/universe) [2.34+17.04 => 2.35+17.04] (no packageset)
[13:57] <LocutusOfBorg> Laney, you aware of the recent failures? http://autopkgtest.ubuntu.com/packages/o/ovito/bionic/ppc64el
[13:58] <LocutusOfBorg> also, lots of dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate memory
[13:58] <LocutusOfBorg> e.g. http://autopkgtest.ubuntu.com/packages/s/swift/bionic/i386 since this morning
[14:00] <Laney> probably going to re-deploy onto a larger machine
[14:00] <Laney> you retry them for now
[14:00] <Laney> you can*
[14:00] <Laney> stuff is getting OOM killed
[14:00] <Laney> annoying
[14:08] -queuebot:#ubuntu-release- New binary: llvm-toolchain-5.0 [arm64] (xenial-proposed/main) [1:5.0-3~16.04.1] (no packageset)
[14:13] -queuebot:#ubuntu-release- New binary: llvm-toolchain-5.0 [armhf] (xenial-proposed/main) [1:5.0-3~16.04.1] (no packageset)
[14:14] <apw> Laney, don't our instances have any swap ?
[14:15] <apw> Laney, you could consider adding a swap file in the instance and see if htat helps any
[15:06] <Laney> apw: it's the controller
[15:22] <slangasek> Laney: yeah, with ssh-setup I mean I have a hard time working out how to set a break point and debug why it takes so long
[15:23] <slangasek> infinity: u-d-a, I didn't forget I just ran out of time
[15:30] <Laney> slangasek: Right, OK, well I've never done it with a breakpoint but you can make a copy of the file and pass it to test runs of autopkgtest
[15:31] <Laney> Anyways, I think it's probably resource starvation on the controller
[15:31] <Laney> let's see shortly when I get the new box up
[16:24]  * Laney begins moving jobs over to the new machine
[16:24] <Laney> might see an interruption in autopkgtest throughput if you're watching closely
[16:30] <tsimonq2> infinity: Hypothetical question for you. Let's say a flavor wanted to ship with an installer other than Ubiquity. Would anyone object to a flavor doing so? Is this something that needs to be discussed with the TB?
[16:45] <xnox> tsimonq2, note we currently have: d-i, ubiquity gtk, ubiquity kde, subiquity, curtin as the supported set of installers. Adding more or less should be no problem, as long as it is free software and shipped in ubuntu. (note subiquity is a snap, not even in the archive, but said snap is built in launchpad against ubuntu archive)
[16:45] <xnox> tsimonq2, what do you have in mind as the installer? anaconda? =)
[16:46]  * xnox kind of wishes we could make desktops be installable with a graphical subiquity/curtin based, with mostly first boot experience to configure the instances.
[16:46] <xnox> and yes that does mean support for cloud-init on the desktop too, which imho makes a lot of sense!
[16:47] <tsimonq2> xnox: I'm still scoping out things, but Calamares seems fitting.
[16:48] <tsimonq2> xnox: Thanks :)
[16:48] <xnox> tsimonq2, uploading that to debian may make sense.
[16:48] <tsimonq2> xnox: It already is in Debian.
[16:49] <tsimonq2> !info calamares
[16:49] <ubot5> Package calamares does not exist in zesty
[16:49] <xnox> tsimonq2, maybe one can do plugings to make it reusable with e.g. liveisntaller generated squashfs and/or "d-i hook backend plugin integration bridge" and/or "curtin spagehti mess" some such.
[16:49] <tsimonq2> !info calamares bionic
[16:49] <ubot5> calamares (source: calamares): distribution-independent installer framework. In component universe, is optional. Version 3.1.7-2 (bionic), package size 1960 kB, installed size 4844 kB (Only available for linux-any)
[16:49] <xnox> nice
[16:51] <xnox> tsimonq2, if you need/want we can start making experimental images with that installer instead of ubiquity. E.g. i think we did have various "desktop-next" "kubuntu-mobile" "qt5-before-qt5-was-good" etc desktop images. some of them graduated to be the normal onces; others got abandoned. It's all flexible, as long as there are people who want to do the work =) test milestones, fix regressions, etc =)
[16:51] <tsimonq2> xnox: Lubuntu Next is already experimental :P
[16:51] <xnox> lubuntu-the-one-after
[16:52] <tsimonq2> Lubuntu Qt, I mean
[16:52]  * xnox is trolling
[16:52] <tsimonq2> :P
[16:53]  * tsimonq2 goes to class, be back in <= 30 mins
[16:57] <Laney> load average: 0.52, 1.96, 23.52
[16:57] <Laney> autopkgtest box is happier now I killed all the workers off :-)
[16:58] -queuebot:#ubuntu-release- New: rejected hibagent [source] (bionic-proposed) [1.0.1-0ubuntu1]
[16:59] <Laney> No work -> no stress
[17:02] <balloons> sil2100, I have one more attempt in the queue now for the juju-core adt tests. The previous change was using a cidr expansion feature that isn't in the version we're trying to ship, so we did it manually instead.
[17:04] -queuebot:#ubuntu-release- New source: hibagent (bionic-proposed/primary) [1.0.1-0ubuntu1]
[17:39] <tsimonq2> So could you give more details as to those plugins you were referring to, xnox?
[17:46] <tsimonq2> xnox: I don't know a lot about the Ubiquity internals so any tips with that would be appreciated as well.
[17:46] <tsimonq2> Meaning, what I would have to bend Calamares to do.
[17:52] <mitya57> Laney: somehow I did not notice your Wednesday’s ping about qscintilla2 tests, sorry. It should be fixed now :)
[17:55] <Laney> mitya57: no worries, and thanks!
[18:06] <Laney> I've stolen lcy01 for some testing of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717
[18:06] <ubot5> Launchpad bug 1730717 in linux (Ubuntu Bionic) "Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"" [High,In progress]
[18:06] <Laney> I'll come back later or tomorrow and put it back on for general use
[18:11] <xnox> tsimonq2, what details? that's the stuff i made up on the spot, which somebody will need to "figute out, learn details, study internals, and write code"
[18:11] <xnox> tsimonq2, as far as i understand none of that exists, even remotely.
[18:27] <xnox> slangasek, autopkgtest for pglogical/2.1.0-1: amd64: Always failed, armhf: Regression ♻ , i386: Always failed, ppc64el: Always failed, s390x: Always failed -> please make it "always failed" on armhf too, or bad test it?
[18:27] <xnox> and the postgresql should be migratable once psqlodbc ADT is sorted out
[19:08] <jbicha> xnox: there are still several postgresql-common autopkgtest regressions
[20:06] <tsimonq2> xnox: Oh gotcha
[20:28] <tsimonq2> xnox: Oh, one thing worth mentioning is that Calamares being the installer for a flavor is that we'll need some settings... Neon has these in a separate source package, do you think we could do something similar for us?
[20:35] <tsimonq2> In fact, there's an ITP open for calamares-settings-debian. I think we should blacklist syncing that and have src:calamares-settings-ubuntu. I think it should be a separate source package because Lubuntu's not the only flavor looking at using Calamares so it would make it fairly trivial for them to just add a binary package.
[20:38] <infinity> xnox: Except the failure is pretty clearly a bug.
[20:42] <infinity> xnox: Oh, well, maybe I should have read all the logs.  The first regression was fixed to expose more.  Hrm.
[21:11] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-5.0 [amd64] (xenial-proposed) [1:5.0-3~16.04.1]
[21:11] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-5.0 [armhf] (xenial-proposed) [1:5.0-3~16.04.1]
[21:11] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-5.0 [powerpc] (xenial-proposed) [1:5.0-3~16.04.1]
[21:11] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-5.0 [s390x] (xenial-proposed) [1:5.0-3~16.04.1]
[21:11] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-5.0 [arm64] (xenial-proposed) [1:5.0-3~16.04.1]
[21:11] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-5.0 [ppc64el] (xenial-proposed) [1:5.0-3~16.04.1]
[21:11] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-5.0 [i386] (xenial-proposed) [1:5.0-3~16.04.1]
[21:37] <Laney> http://autopkgtest.ubuntu.com/packages/python-aodhclient/bionic/amd64 run times are back down to much more sane levels
[22:02] <tsimonq2> So nodejs is now waiting on icu to migrate
[22:03]  * tsimonq2 wonders why it hasn't migrated yet
[22:06] <LocutusOfBorg> entangled transitions
[22:06] <LocutusOfBorg> they need to go all together
[22:07] <tsimonq2> LocutusOfBorg: How can I help?
[22:07] <nacc> tsimonq2: update_output.txt implies it's waiting on a bunch of stuff
[22:07] <tsimonq2> nacc: Sure, but I'm scratching my head because nothing's on https://people.canonical.com/~ubuntu-archive/transitions/html/icu.html , which is why I'm asking the question.
[22:07] <tsimonq2> Because that should show relevant rdeps that need building, no?
[22:08] <LocutusOfBorg> yes, but some of the icu rdeps are waiting for other new transitions, e.g. perl/gdal/numpy/scipy
[22:08] <LocutusOfBorg> haskell, xerces-c grass sip4, qt
[22:08] <nacc> tsimonq2: right, but just because everything has been rebuilt, does not mean it has all migrated
[22:09] <LocutusOfBorg> ffmpeg
[22:09] <nacc> or is ready to migrate
[22:09] <nacc> they all have to go through excuses and be ready to migrate *with* icu
[22:09] <nacc> (afaict)
[22:13] <tsimonq2> Is there an easy way to figure out what's entangled or do you sort of have to look at it package by package?
[22:14] <LocutusOfBorg> fixing ffmpeg/scipy/numpy is a trivial starting point
[22:14] <tsimonq2> Alright
[22:14]  * tsimonq2 can start helping those
[22:15] <LocutusOfBorg> pyqt4 needs testsuite to become green
[22:15] <LocutusOfBorg> erm pyqt5
[22:15] <tsimonq2> Whoever turned off the autosyncer deserves a beer :P
[22:15] <LocutusOfBorg> :)
[22:16] <LocutusOfBorg>     * amd64: libapache2-mod-shib2, libcegui-mk2-dev, libsaml2-dev, libsaml9, libshibresolver-dbg, libshibresolver-dev, libshibresolver1, libshibsp-dev, libshibsp-plugins, libshibsp7, libxmltooling-dev, libxmltooling7, moonshot-gss-eap, moonshot-gss-eap-dbg, moonshot-trust-router, opensaml2-tools, shibboleth-sp2-utils, sumo, uim, uim-chewing, uim-qt5, wordpress-shibboleth, z-push-backend-carddav
[22:17] <LocutusOfBorg> fixing them might help your transition finish I guess (from notest, the big hint that tries to make nodejs migrate)
[22:21] <tsimonq2> I thought doko was going to merge anthy because it's blocking uim
[23:21] -queuebot:#ubuntu-release- Unapproved: lxd (xenial-backports/main) [2.18-0ubuntu3~16.04.2 => 2.20-0ubuntu4~16.04.1] (edubuntu, ubuntu-server)
[23:23] -queuebot:#ubuntu-release- Unapproved: lxd (artful-backports/main) [2.18-0ubuntu6 => 2.20-0ubuntu4~17.10.1] (edubuntu, ubuntu-server)
[23:23] -queuebot:#ubuntu-release- Unapproved: lxd (zesty-backports/main) [2.18-0ubuntu3~17.04.2 => 2.20-0ubuntu4~17.04.1] (edubuntu, ubuntu-server)
[23:28] -queuebot:#ubuntu-release- Unapproved: rejected lxd [source] (zesty-backports) [2.20-0ubuntu4~17.04.1]
[23:29] -queuebot:#ubuntu-release- Unapproved: rejected lxd [source] (artful-backports) [2.20-0ubuntu4~17.10.1]
[23:29] -queuebot:#ubuntu-release- Unapproved: rejected lxd [source] (xenial-backports) [2.20-0ubuntu4~16.04.1]
[23:29] <tumbleweed> win 32
[23:30] <tsimonq2> irssi ftw
[23:31] -queuebot:#ubuntu-release- Unapproved: lxd (xenial-backports/main) [2.18-0ubuntu3~16.04.2 => 2.20-0ubuntu4~16.04.1] (edubuntu, ubuntu-server)
[23:32] -queuebot:#ubuntu-release- Unapproved: lxd (zesty-backports/main) [2.18-0ubuntu3~17.04.2 => 2.20-0ubuntu4~17.04.1] (edubuntu, ubuntu-server)
[23:33] -queuebot:#ubuntu-release- Unapproved: lxd (artful-backports/main) [2.18-0ubuntu6 => 2.20-0ubuntu4~17.10.1] (edubuntu, ubuntu-server)
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (artful-backports) [2.20-0ubuntu4~17.10.1]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-backports) [2.20-0ubuntu4~16.04.1]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (zesty-backports) [2.20-0ubuntu4~17.04.1]
[23:40] <stgraber> would be great if someone from the SRU team could take a look at that lxd 2.0.11 upload, it's been sitting in the xenial-proposed queue for a bit now and my understanding is that it's needed to clean some of the kernel updates ADT (on top of including 6 months of LXD bugfixes we'd like to get to our users)