=== Guest67307 is now known as RAOF
[02:33] <tsimonq2> slangasek: afair it was something along the lines of ubuntu-ui-toolkit (not sure if the first word is correct, it was ui-toolkit
[02:33] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (xenial-proposed) [0.90ubuntu0.7]
[02:33] <tsimonq2> )
[02:33] <tsimonq2> slangasek: So let me look
[02:34] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (zesty-proposed) [0.93.1ubuntu2.3]
[02:34] <tsimonq2> slangasek: Nope, still need ubuntu-ui-toolkit to be removed :)
[02:36] <tsimonq2> slangasek: In any case, I'll get back to you in a bit about what else (if there is anything else)
[02:41] -queuebot:#ubuntu-release- Unapproved: accepted linux [amd64] (artful-proposed) [4.11.0-12.18]
[05:00] -queuebot:#ubuntu-release- New binary: ruby-retriable [amd64] (artful-proposed/universe) [3.0.1-2] (no packageset)
[05:01] -queuebot:#ubuntu-release- New binary: sphinxcontrib-websupport [amd64] (artful-proposed/universe) [1.0.1-1] (no packageset)
[05:24] <slangasek> tsimonq2: ubuntu-ui-toolkit has a substantial number of revdeps still
[05:27] <tsimonq2> slangasek: Looking at these reverse dependencies, all of them seem to be Unity 8-related.
[05:28] <slangasek> possibly, but they still need to be gone through one at a time
[05:29] <tsimonq2> What would be the best way to proceed? File a removal bug against each package?
[06:42] -queuebot:#ubuntu-release- New: accepted ruby-retriable [amd64] (artful-proposed) [3.0.1-2]
[06:42] -queuebot:#ubuntu-release- New: accepted sphinxcontrib-websupport [amd64] (artful-proposed) [1.0.1-1]
[07:03] <slangasek> tsimonq2: ultimately, yes; please coordinate with xnox on this
[07:05] <tsimonq2> slangasek: sure, thanks
[07:06] <tsimonq2> xnox: What would you like to do irt ubuntu-ui-toolkit revdep removal (because we need ubuntu-ui-toolkit removed for Qt to successfully migrate)
[07:07] <tsimonq2> ?
[07:07] <tsimonq2> (that's a question, it gets a question mark :P)
=== klebers_ is now known as klebers
[07:41] <Saviq> xnox: AFAIK, we don't need content-hub, we should get rid of it across the board, but might wanna confirm with willcooke as to what the plan is for secure data transfer between snaps
=== santa is now known as Guest62238
[09:10] -queuebot:#ubuntu-release- Unapproved: xorg-server (xenial-proposed/main) [2:1.18.4-0ubuntu0.3 => 2:1.18.4-0ubuntu0.4] (desktop-core, xorg)
[09:20] <xnox> tsimonq2, i do not have confirmation about a number of things in that rev-deps list. Last time I discussed them, they have been requested to be kept in the archive.
[09:20] <xnox> Saviq, i shall write an email about it, to have an email confirmation.
[09:20] <Saviq> kk
[09:22] <infinity> xnox: Oh good, you're awake.  Can you verify that unattended-upgrades thing?
[09:23] <xnox> infinity, yes.
[09:23] <infinity> xnox: My hero.
[09:28] <tsimonq2> xnox: Ok, I'll look into seeing how hard it would be to update ubuntu-ui-toolkit for the new Qt
[09:49] <xnox> infinity, it did the right thing on xenial. will check zesty now.
[09:49] <xnox> bug updated w.r.t. tags for xenial.
[09:53] <infinity> xnox: xenial's all I care about right now, so thanks. :P
[09:54] <sil2100> ;p
[09:55] <infinity> xnox: Though you seem to have lied about the tags. ;)
[10:00] <infinity> xnox: Anyhow, released for xenial, you can fix the tags to match reality. :P
[10:01] <xnox> bah
[10:01] <xnox> infinity, it was pending me to click the green tick. seems to have edited the tags but didn't submit them.
[10:01]  * xnox goes to find coffee
[10:02] <infinity> Heh.
[10:02] <xnox> also maintainer scripts generated by deb-systemd-invoke shit is broken in zesty.
[10:02] <xnox> and/or systemd.
=== pietroalbini_ is now known as pietroalbini
[10:40] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.11.0-12.17~16.04.1] (kernel)
[10:45] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.11.0-12.17~16.04.1]
[11:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Xenial 16.04.3] (20170801) has been added
[11:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Xenial 16.04.3] (20170801) has been added
[11:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Xenial 16.04.3] (20170801) has been added
[11:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Xenial 16.04.3] (20170801) has been added
[11:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base powerpc [Xenial 16.04.3] (20170801) has been added
[11:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Xenial 16.04.3] (20170801) has been added
[11:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Xenial 16.04.3] (20170801) has been added
[11:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Xenial 16.04.3] (20170801) has been added
[11:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Xenial 16.04.3] (20170801) has been added
[11:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Xenial 16.04.3] (20170801) has been added
[11:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Xenial 16.04.3] (20170801) has been added
[11:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Xenial 16.04.3] (20170801) has been added
[11:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Xenial 16.04.3] (20170801) has been added
[11:41] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Xenial 16.04.3] (20170801) has been added
[11:41] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Xenial 16.04.3] (20170801) has been added
[11:49] -queuebot:#ubuntu-release- Builds: Mythbuntu Desktop amd64 [Xenial 16.04.3] (20170801) has been added
[11:49] -queuebot:#ubuntu-release- Builds: Mythbuntu Desktop i386 [Xenial 16.04.3] (20170801) has been added
[11:54] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Xenial 16.04.3] (20170801) has been added
[11:55] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Xenial 16.04.3] (20170801) has been added
[11:59] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Xenial 16.04.3] (20170801) has been added
[11:59] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Xenial 16.04.3] (20170801) has been added
[12:04] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Xenial 16.04.3] (20170801) has been added
[12:04] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Xenial 16.04.3] (20170801) has been added
=== alan_g is now known as alan_g|lunch
[12:12] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Xenial 16.04.3] (20170801) has been added
[12:17] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Xenial 16.04.3] (20170801) has been added
[12:17] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Xenial 16.04.3] (20170801) has been added
[12:26] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Xenial 16.04.3] (20170801) has been added
[12:26] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Xenial 16.04.3] (20170801) has been added
[12:26] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Xenial 16.04.3] (20170801) has been added
[12:26] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Xenial 16.04.3] (20170801) has been added
[12:33] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Xenial 16.04.3] (20170801) has been added
[12:33] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Xenial 16.04.3] (20170801) has been added
=== alan_g|lunch is now known as alan_g
[14:16] <LocutusOfBorg> seriously? new perl?
[14:16] <teward> LocutusOfBorg: where have you been the past month lol
[14:16] <teward> that's been causing hellish things for a while now heh
[14:17] <LocutusOfBorg> teward, where have you been?
[14:17] <LocutusOfBorg> I *did* sync it
[14:17] <LocutusOfBorg> I'm talking about the -5 autoimported update
[14:17] <teward> ah, ok.
[14:17] <LocutusOfBorg> :)
[14:17] <teward> LocutusOfBorg: i'm not awake, sue me.
[14:17]  * teward chugs his fifth coffee of the day
[14:18] <LocutusOfBorg> lol no problem dear, I wasn't really clear in the first sentence
[14:19] <LocutusOfBorg> and having thousand of tests rerun makes me sad and grumpy :p
[14:20] <LocutusOfBorg> btw I did sync it less than a week ago :)
[14:20] <LocutusOfBorg> doko, what happens with gcc switch now?
[14:22] <doko> what should happen?
[14:22] <LocutusOfBorg> will you wait for perl to transition or will you pull the trigger?
[14:22] <LocutusOfBorg> (to finish I mean)
=== sergiusens_ is now known as sergiusens
[14:31] <LocutusOfBorg> Laney, sorry but I see lots of "test in progress" and no test running (or queued) what is that?
[14:41] <teward> LocutusOfBorg: ah, well a couple weeks ago nginx updates got hung by the Perl stuff, was that your sync/upload as well?
[14:51] <LocutusOfBorg> yep
[14:59] <LocutusOfBorg> we tried to make that transition smooth, but I/we apparently failed
[15:37] <LocutusOfBorg> hopefully somebody will have a look at autopkgtests not running
[15:37]  * LocutusOfBorg leaves
[15:59] <jdstrand> fyi tyhicks and sbeattie> the apparmor upload fixes the autopkgtest issues and update_excuses is fine for it (no regressions), but it isn't (yet) being considered because of the perl in -proposed that hasn't migrated yet
[16:00] <tyhicks> jdstrand: that should be fine because, IIRC, the kernel tests enable -proposed
[16:00] <infinity> Not without some trickery, no.
[16:01] <infinity> But that can be done where needed.
[16:01] <jdstrand> infinity: it isn't needed. it's fine if it flows in whenever perl does
[16:01] <jdstrand> infinity: thanks though
[16:02] <jdstrand> well, for some definitionof 'whenever' :)
[16:04] <tyhicks> -proposed is enabled for the kernel tests
[16:05] <tyhicks> Get:45 http://ftpmaster.internal/ubuntu artful-proposed/main amd64 apparmor amd64 2.11.0-2ubuntu10 [495 kB]
[16:05] <tyhicks> (from https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20170729_223227_2ecb4@/log.gz)
[16:06] <jdstrand> yeah. I looked at the logs apw gave and saw I needed to have proposed enabled, which brought in a more sensitive podchecker, etc, etc
[16:10] <apw> tyhicks, isnt that because apparmor is updated and a trigger on the test?
[16:12] <tyhicks> apw: ah, that is probably true
[16:12] <apw> though in that log it seems that all-proposed is enabled, which seems unexpected to me
[16:15] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Xenial 16.04.3] (20101020ubuntu451.14) has been added
[16:15] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Xenial 16.04.3] (20101020ubuntu451.14) has been added
[16:15] -queuebot:#ubuntu-release- Builds: Netboot armhf [Xenial 16.04.3] (20101020ubuntu451.14) has been added
[16:16] -queuebot:#ubuntu-release- Builds: Netboot i386 [Xenial 16.04.3] (20101020ubuntu451.14) has been added
[16:16] -queuebot:#ubuntu-release- Builds: Netboot powerpc [Xenial 16.04.3] (20101020ubuntu451.14) has been added
[16:16] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Xenial 16.04.3] (20101020ubuntu451.14) has been added
[16:16] -queuebot:#ubuntu-release- Builds: Netboot s390x [Xenial 16.04.3] (20101020ubuntu451.14) has been added
[16:47] <sergiusens_> apw: if you are around, mind looking at snapcraft 2.33 waiting to be approved into {xenial|zesty}-proposed ?
[16:51] <apw> sergiusens_, sure
[17:22] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (zesty-proposed) [2.33+17.04]
[17:24] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (xenial-proposed) [2.33]
[17:30] <apw> sergiusens_, ^
[17:34] <slangasek> yay, autopkgtests for mariadb-10.1 fixed themselves upstream in Debian
[17:34] <slangasek> xnox: new systemd upload still pending?
[17:35] <xnox> slangasek, preparing, and it should resolve snapd not starting in lxd containers.
[17:36] <xnox> (and maybe even fix systemd->snapd autopkgtests on armhf/s390x)
[17:36] <xnox> slangasek, are you desparate to unblock migrations?
[17:36] <slangasek> xnox: not desperate, just wondering about timeline
[17:37] <xnox> ok. also it seemed to have lost test results for amd64/i386 - it claimed still running without any results recorded anywhere, and nothing in running. I retriggered that by hand.
[17:37] <xnox> is that normal to loose results and claim they are still running?
[17:37] <xnox> and that did not seem to work.
[17:38] <slangasek> aaaaand perl got a new revision uploaded in Debian.  yay.
[17:38] <xnox> slangasek, why it says "autopkgtest for systemd/234-2ubuntu1" triggered by systemd/234-2ubuntu1 claims to be "Test in progress" but it is nowhere on amd64 and i386.
[17:38] <xnox> unless it just got around to do them
[17:38] <xnox> http://autopkgtest.ubuntu.com/running#pkg-systemd
[17:38] <xnox> says that i requested it.
[17:38] <xnox> but running for 1h34m that cannot be right.
[17:39] <xnox> You are in emergency mode. After logging in, type "journalctl -xb" to view
[17:39] <xnox> system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to boot
[17:39] <xnox> into default mode.
[17:39] <xnox> Press Enter for maintenance
[17:39] <xnox> (or press Control-D to continue):
[17:39] <xnox> that does not seems right =(
[17:39] <apw> xnox, systemd broken again perhaps ?
=== sergiusens_ is now known as sergiusens
[17:40] <slangasek> yes maybe the reason you're not getting systemd test results is because you broke everything ;)
[17:40] <xnox> lovely
[17:41] <xnox> it did pass on the one architecture that matters - ppc64el =)
[18:00] <xnox> so on s390x NetworkManager-wait-online.service fails to complete, within 10s, after 5 reboots.
[18:01] <xnox> but that has timeout 30.
=== beisner_ is now known as beisner
[19:27] <slangasek> Laney: could you document on https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure how to remove tests from the queue?
[19:30] <slangasek> ... also, what happened to all of the perl-triggered tests that britney thinks are "in progress" :P
[19:30] <Laney> slangasek: ok, on thursday, but for now - filter-amqp on autopkgtest-cloud-worker/0; see shell history
[19:30] <slangasek> Laney: cool,t hanks
[19:31] <Laney> if you want to document it based on that, feel free
[19:31] <Laney> no clue what happened to the tests
[19:31] <Laney> bos01 had a sad but that seems to have sorted itself
[19:31] <Laney> can't explain lcy01/lgw01
[19:32] <slangasek> yeah, I'll requeue the lot
[19:33] <Laney> mmm
[19:33] <Laney> there was a rabbitmq upload around the time
[19:33] <Laney> that's suspicious
[19:33] <Laney> update applied*
[19:33] <slangasek> applied on the runners?
[19:33] <Laney> on the rabbitmq server
[19:34] <Laney>    Active: active (running) since Tue 2017-08-01 11:27:48 UTC; 8h ago
[19:36] <apw> oh man, they can't have flushed the lot, can they?
[19:38] <Laney> I can't prove it but the timing is interesting at least
[19:38] <Laney> the queues are durable so the messages should have survived a restart
[19:39] <slangasek> so I have retry-autopkgtest-regressions running, it says a lot of things, and http://autopkgtest.ubuntu.com/running doesn't show any queues filling up
[19:40] <slangasek> Laney: how do you know about the rabbitmq server upgrade?
[19:40] <slangasek> (i.e. which thread should I pull for details)
[19:43] <slangasek> now for comparison, the one test I queued using run-autopkgtest from snakefruit apparently *did* start
[19:44] <Laney> I just triggered apt/zesty using request.cgi
[19:44] <Laney> it's there
[19:44] <slangasek> oh
[19:44] <slangasek> I should read my wget output
[19:44] <slangasek> expired token, lalala
[19:46] <Laney> so, sounds like a bug on rabbitmq-server might be in order maybe
[19:46] <Laney> would be nice if someone could try to reproduce that
[19:47] <slangasek> Laney: bug for having dropped the queue?
[19:47] <Laney> nod
[19:47] <slangasek> right
[19:47] <Laney> 'durable' queues (of which these are) are supposed to survive restarts of the broker
[19:47] <slangasek> where can I see details about the upgrade that happened?
[19:47] <Laney> unit rabbitmq-server/0
[19:48] <slangasek> ah so this was unattended-upgrades, not IS
[19:48] <slangasek> got it
[19:48] <Laney> yeah
[19:48] <Laney> IS-mandated unattended upgrade though ;)
[19:49] <Laney> (it was a security update, so applying it is fair enough)
[19:49] <Laney> seems like queues are filling up again - got a train to catch a flight to Montreal in ~12h, so I'm going to duck out
[19:49] <Laney> see you on the other side
[19:49]  * slangasek waves
[19:56] <slangasek> /var/lib/rabbitmq/mnesia/rabbit@juju-prod-ues-proposed-migration-machine-1 looks like cruft (Sep 7 2016)
[20:08] <slangasek> hngh, retry-autopkgtest-regressions does not order its requests very sensibly.  apparently we are going to completely fill the s390x queue before looking at any other archs. :P
[22:48] <apw> slangasek, it has also dropped them all on the ubuntu queue rather than the original huge
[22:49] <slangasek> apw: yeah, I know; retry-autopkgtest-regressions doesn't have a twiddle for that
[22:50] <slangasek> apw: but also my carefactor is low because almost everything in p-m is currently blocked behind the perl migration anyway
[22:50] <slangasek> apw: if you're going to tell me that I've broken linux migration I'll probably have a sad about that
[22:51] <apw> slangasek, well i assume we are still queueing things, but there is no way now to get results for anything without perl clearing the queues, kernel included
[22:51] <apw> i suspect we want those bulk retries to always go to huge, but as you say no twiddle
[22:54] <slangasek> apw: I've just finished the queuing.  According to my browser's string count on http://people.canonical.com/~ubuntu-archive/proposed-migration/artful/update_excuses.html there should be about 13k all told
[22:56] <apw> slangasek, lets see how much of this mess clears over night i guess
[22:56] <apw> slangasek, and i will look to add the --huge twiddle in the morning, as i think as that queue is clear i could use it
[22:56] <slangasek> apw: based on the last perl upload, I'd guess only about a third :P
[22:56] <slangasek> apw: quite so :)
[22:59] <xnox> the most well tested perl ever.
[23:00] <xnox> is there actually any point in perl adt tests? i thought it all runs unit tests, and all of them run during build too, no?
[23:01] <slangasek> xnox: the first time around certainly caught a number of regressions w/ 5.26
[23:01] <xnox> ok.
[23:01] <slangasek> and there were still a handful of outstanding regressions that needed handled, which now I need to wait for a queue to see again what their status is
[23:11] -queuebot:#ubuntu-release- New binary: libglvnd [ppc64el] (artful-proposed/universe) [0.2.999+git20170201-4] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: libglvnd [s390x] (artful-proposed/universe) [0.2.999+git20170201-4] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: libglvnd [amd64] (artful-proposed/universe) [0.2.999+git20170201-4] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: libglvnd [i386] (artful-proposed/universe) [0.2.999+git20170201-4] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: libglvnd [armhf] (artful-proposed/universe) [0.2.999+git20170201-4] (no packageset)