[00:24] <doko> slangasek, infinity: uhd is entangled as well. now uploaded no-change rebuilds
[00:46] <doko> and oce ...
[00:53] <doko> openimageio too
[01:03] -queuebot:#ubuntu-release- New: accepted fscrypt [source] (bionic-proposed) [0.2.2-0ubuntu1]
[01:06] -queuebot:#ubuntu-release- New binary: fscrypt [i386] (bionic-proposed/none) [0.2.2-0ubuntu1] (no packageset)
[01:07] -queuebot:#ubuntu-release- New binary: fscrypt [arm64] (bionic-proposed/none) [0.2.2-0ubuntu1] (no packageset)
[01:07] -queuebot:#ubuntu-release- New binary: fscrypt [amd64] (bionic-proposed/none) [0.2.2-0ubuntu1] (no packageset)
[01:17] -queuebot:#ubuntu-release- New: accepted fscrypt [amd64] (bionic-proposed) [0.2.2-0ubuntu1]
[01:17] -queuebot:#ubuntu-release- New: accepted fscrypt [i386] (bionic-proposed) [0.2.2-0ubuntu1]
[01:18] -queuebot:#ubuntu-release- New: accepted fscrypt [arm64] (bionic-proposed) [0.2.2-0ubuntu1]
[01:18] -queuebot:#ubuntu-release- New: accepted fscrypt [source] (bionic-proposed) [0.2.2-0ubuntu2]
[01:27] -queuebot:#ubuntu-release- New binary: fscrypt [amd64] (bionic-proposed/none) [0.2.2-0ubuntu2] (no packageset)
[01:27] -queuebot:#ubuntu-release- New binary: fscrypt [i386] (bionic-proposed/none) [0.2.2-0ubuntu2] (no packageset)
[01:27] -queuebot:#ubuntu-release- New binary: fscrypt [arm64] (bionic-proposed/none) [0.2.2-0ubuntu2] (no packageset)
[01:28] -queuebot:#ubuntu-release- New: accepted fscrypt [amd64] (bionic-proposed) [0.2.2-0ubuntu2]
[01:28] -queuebot:#ubuntu-release- New: accepted fscrypt [i386] (bionic-proposed) [0.2.2-0ubuntu2]
[01:28] -queuebot:#ubuntu-release- New: accepted fscrypt [arm64] (bionic-proposed) [0.2.2-0ubuntu2]
[02:12] <infinity> xnox: Did you seriously entangle a mir transition with the rest of this mess? :(
[02:13] <infinity> xnox: Oh, mirclient didn't bump ABI.  Maybe I won't hunt you down.
[02:14] <tsimonq2> (mir has enough rdeps to manage a transition? *runs*)
[02:15] <infinity> tsimonq2: Still a few, and they're the sorts of things that trigger 3 days of tests.
[02:15] <infinity> (gtk, xorg, mesa...)
[02:16] <tsimonq2> infinity: Ah gotcha
[02:24] <slangasek> infinity: did step 44 from the checklist get done? (Open an RT to ask IS to create chroots on the porter boxes.)
[02:25] <infinity> slangasek: Nein.  Finishing the checklist was on my checklist after this (&!^%^ transition.
[02:25] <slangasek> infinity: (which might be relevant to trying to fix mrpt on armhf)
[02:26] <infinity> slangasek: But if someone (you?) was feeling the urge to investigate the SIGBUS in blender, I see how that would be a chicken and egg.
[02:26] <infinity> slangasek: Or mrpt.
[02:26] <slangasek> right
[02:26] <infinity> I'm hoping they're the same root cause.   Bug life's never that simple.
[02:26] <slangasek> if I manage to get a reproducer environment, I might be able to tell you
[04:31] <doko> looks like somebody shoved in all his merges for bionic ... ;p regardless of transitions
[04:32] <infinity> doko: I'm testing a fix for deal.ii right now.
[04:40] <doko> infinity: it's uploaded
[04:42] <infinity> doko: Oh, I was testing the upstream fix. :P
[04:42] <infinity> If it's good, I think I'll swap fixes with yours.
[07:24] <infinity> doko: Ooo, I think I have an openimageio/blender fix.  Just need a test build iteration of both to confirm.
[07:27] <doko> infinity: and that will be enough? it looks like some gnome stuff wants to transition as well ...
[07:28] <doko> jbicha: any gnome related soname bumps in -proposed?
[07:28] <infinity> doko: I dunno.  I've been staring at this for the last couple of hours, not britney.
[07:28] <infinity> doko: But once this is fixed, I'll go back to britney and see if we're done.
[07:28] <infinity> doko: vorlon fixed mrpt, I believe.
[07:29] <doko> osgearth autopkg test regression on armhf
[07:30] <doko> no, britney doesn't look good
[07:30] <infinity> Transient.
[07:30] <doko> but update-output-helper doesn't work for me, and Laney isn't here
[07:30] <infinity> Retrying.
[07:32] <infinity> output will be a mess because boost went back to not being a valid candidate, pending ceph tests.
[07:34] <doko> promoted some boost binaries again
[07:35] <infinity> ?
[07:35] <infinity> Ahh, for ceph and rados.
[07:35] <infinity> How fun.
[07:41] <infinity> Well, this is a fine time for autopkgtest.ubuntu.com to go away.
[07:49]  * LocutusOfBorg is not feeling alone anymore with the F5 key on that page
[08:06] <infinity> LocutusOfBorg: Hammering the F5 key wasn't helping.  At all.
[08:06] <infinity> LocutusOfBorg: It had a load in the hundreds.
[08:06]  * infinity murdered half of its processes, and now it seems happy.
[08:12] <apw> those rebuild on demand pages ...
[08:16] <infinity> apw: Yeah, that's not what was killing it.
[08:18] <infinity> apw: There was some cron-like job that appears to desperately want locking and had a few dozen running.  And that was eating the CPU hard enough that apache's request.cgi and browse.cgi were backed up to last week, and the whole thing just gave up and stopped talking to people.
[08:18] <apw> hmmm, i wonder if that is the one dropping the running summary (which is periodically generated)
[08:19] <infinity> Not if the name is accurate.
[08:19] <infinity> update-github-jobs is the thing that's chasing its own tail.
[08:20] <apw> oh, nasty, that thing should die in a pit of boiling oil
[08:20] <infinity> Not inclines to disagree.
[08:20] <infinity> Nor inclined.
[08:54] -queuebot:#ubuntu-release- Unapproved: libreoffice-l10n (artful-proposed/main) [1:5.4.1-0ubuntu1 => 1:5.4.2-0ubuntu1] (ubuntu-desktop)
[09:09] <Laney> doko: what you want brother
[09:14] <LocutusOfBorg> Laney, I guess armhf failing with ENOSPACE on autopkgtests
[09:14] -queuebot:#ubuntu-release- Unapproved: libreoffice (artful-proposed/main) [1:5.4.1-0ubuntu1 => 1:5.4.2-0ubuntu1] (kubuntu, ubuntu-desktop)
[09:15] <Laney> LocutusOfBorg: "update-output-helper doesn't work for me" would be a very weird way of expressing that question
[09:21] <infinity> LocutusOfBorg: That's been going on for a while now.  Retrying when they're less loaded works.
[09:21] <infinity> Just a PITA.
[09:23] <Laney> where is it visible right now?
[09:23] <Laney> quick!
[09:24] <infinity> Laney: A bunch of k* stuff failed on armhf with ENOSPCish issues just recently.
[09:24] <infinity> Where "recently" is in the last few hours.
[09:25] <infinity> It may be cleared up by now.
[09:25] <Laney> gosh darn it
[09:26] <infinity> Language.
[09:26] <Laney> ok, when you catch it in the act (since I never have), can you get onto the machine that's running it and see what else is going on?
[09:26] <infinity> Laney: I mean, I never really catch it "in the act", cause I tend to notice once the logs have been sucked up and britney's whining.
[09:26] <infinity> That's a pretty hefty delay for realtime debugging.
[09:28] <infinity> Laney: Speaking of things misbehaving.  Is that you editing update-github-jobs on juju-prod-ues-proposed-migration-machine-2 (wow, what a hostname)?
[09:28] <Laney> Guess we could reduce the parallelism and add some more nodes
[09:28] <Laney> Yeh
[09:28] <Laney> Thanks juju
[09:28] <Laney> that's autopkgtest-web/0 to me
[09:28] <infinity> Laney: Oh, excellent.  I was about to whine to you about that needing some locking, but because I'm ignorant of how this deploys, wasn't sure I would be able to make an edit that was sicky.
[09:28] <infinity> s/sicky/sticky/
[09:29] <Laney> do the thing in autopkgtest-cloud git and then do the same thing on that machine
[09:29] <infinity> (Also, 418 days uptime, while impressive, is also a bit wrong)
[09:29] <Laney> PRODUCTION!
[09:30] <Laney> it had a lot of stale files in the PENDING_DIR too
[09:30] <Laney> who even knows how they got there
[09:30] <infinity> pitti.
[09:30] <infinity> pitti knows.
[09:30] <Laney> well, I know how they *got* there
[09:30] <infinity> And he's not talking.
[09:30] <Laney> but I don't know why they stayed there
[09:30]  * infinity sends the blender/armhf build on its merry way and does a happy dance.
[09:32] <Laney> ubuntu@juju-prod-ues-proposed-migration-machine-2:/tmp/autopkgtest_webcontrol/github-pending$ time sudo flock -w 60 /run/lock/update-github-jobs.lock ~ubuntu/autopkgtest-cloud/webcontrol/update-github-jobs
[09:32] <Laney> real	0m0.541s
[09:32] <Laney> seems a bit happier
[09:32] <infinity> doko: britney seems to be telling me that once it's happy with mrpt, blender, and deal.ii, it'll all migrate.  And all of those are buildable/building/publishing.  So, we're close.
[09:33] <infinity> Laney: Excellent.  We'd had one running since May, so the job itself is clearly not super bright.
[09:34] <Laney> Well, the -w 60 should cause email if it fails now
[09:34] <Laney> I bet it's some case like the PR being deleted while the tests are running
[09:35] <Laney> I'll look when it happens next
[09:35] <Laney> wowzers, half of haskell got removed from testing
[09:36] <infinity> I'd be okay with all of haskell being removed entirely from the archive.
[09:36] <infinity> But, to be fair to the flavour-of-the-month gladiators, we'd also have to remove golang.
[09:36] <infinity> (aw, darn)
[09:38]  * infinity is going to prove how much he hates himself with a trip to McDonald's at 3:38am.
[09:44] <apw> infinity, can i suggest you turn the unapproved queue until you get this heap to migrate
[09:52] -queuebot:#ubuntu-release- Unapproved: sysdig (xenial-proposed/universe) [0.8.0-1ubuntu1 => 0.8.0-1ubuntu3] (no packageset)
[09:57] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-384 (zesty-proposed/universe) [384.90-0ubuntu0.17.04.1 => 384.90-0ubuntu0.17.04.2] (no packageset)
[10:01] <infinity> apw: Oh ye of little faith.
[10:01] <apw> heh, well it happened to you twice alresdy :)
[10:29] -queuebot:#ubuntu-release- Unapproved: accepted sysdig [source] (xenial-proposed) [0.8.0-1ubuntu3]
[10:34] <LocutusOfBorg> sorry Laney for forwarding the wrong question then :)
[10:37] <Laney> LocutusOfBorg: np :P
[10:39]  * LocutusOfBorg keeps fingers crossed
[10:40]  * LocutusOfBorg looks scary at britney output and see morse-simulator
[10:44] -queuebot:#ubuntu-release- New sync: node-gulp-newer (bionic-proposed/primary) [1.3.0-1]
[10:46] <LocutusOfBorg> ^^ this should finally unblock that node-foo
[10:47] <LocutusOfBorg> s/foo/babel/
[10:47] <LocutusOfBorg> so, britney, migration, autosync open?
[10:47] <LocutusOfBorg> or a little perl upload before the autosync?
[10:48] <doko> dans le lac, dans le lac, avec une pierre sur les pieds!
[10:53] <infinity> LocutusOfBorg: morse-simulator is only there because of blender.
[10:53] <infinity> Which is publishing in this cycle.
[10:54]  * infinity puts the publisher on manual to get the britney run in a single "transaction".
[11:24]  * LocutusOfBorg is unsure uploading ceph was a good idea
[11:25] <infinity> I won't hurt anything.
[11:25] <infinity> Cause I'm not letting anything publish until icu migrates.
[11:26] <LocutusOfBorg> so, migration in this run? http://people.canonical.com/~ubuntu-archive/proposed-migration/log/bionic/2017-10-31/11:25:01.log
[11:26] <LocutusOfBorg> ooh thanks infinity this is awesome :)
[11:26] <infinity> Obviously not the run you linked.
[11:26] <infinity> But the next one after this current publisher run settles.
[11:26] <LocutusOfBorg> oh ok, so half an hour
[11:26] <infinity> Or more.
[11:27] <LocutusOfBorg> yep, probably
[11:27] <apw> i doubt it will be that quick with 6 transitions in it
[11:27] <infinity> britney takes a while to think that hard.
[11:27] <infinity> Shame the ocaml transition won't make it, but oh well.
[11:27] <infinity> If someone wants to fix the plpot/ppc64el segv, that'd be lovely.
[11:27] <LocutusOfBorg> infinity, I'm stopped by that ppx, putting in -proposed 3 packages should be mostly ok
[11:28] <LocutusOfBorg> infinity, I tried on debian porterbox, and no segv, so I can't debug it further
[11:28] <LocutusOfBorg> ppx-core failure is obscure to me <-- xnox any idea?
[11:30] <xnox> LocutusOfBorg, last time it was hard too =/
[11:30] <LocutusOfBorg> but that error seems a failure related to ocaml missing files
[11:30] <xnox> infinity, why do we keep "maintaining" packages in ubuntu that have been RoQA in Debian?
[11:31] <infinity> xnox: Which package?
[11:31] <xnox> infinity, for example diet
[11:31] <infinity> xnox: Because no one noticed it was removed, I suppose.
[11:32] <LocutusOfBorg> https://bugs.launchpad.net/ubuntu/+source/diet/+bug/1728466
[11:32] <xnox> infinity, it seems like our removals take too long / are low priority / high overhead?
[11:32] <infinity> xnox: Or someone did notice indeed. :)
[11:32] <xnox> as in it is quicker for me to fix it, then to remove it, but i've been fixing same packages over and over and over again just to get boost moving
[11:32] <jbicha> https://bugs.launchpad.net/~ubuntu-archive/ < have fun
[11:33] <xnox> but in total, removing it years ago, would save my time over these past years.
[11:33] <infinity> xnox: To be fair, jbicha filed that bug all of two days ago.
[11:33] <xnox> infinity, sure, but it was removed from debian a while ago, no?
[11:33] <xnox> actually no
[11:33] <xnox> just in september
[11:34] <xnox> ah, removed from testing in 2014
[11:34] <infinity> Yes.  And I imagine we've been crap about manually checking those things.
[11:34] <jbicha> until a day or two ago, it had a reverse-recommends in Ubuntu from a debian-science metapackage too
[11:34] <xnox> but we have stopped following removals from testing / never done that
[11:34] <infinity> We've never followed testing removals.
[11:34] <xnox> hence me recalling diet for years.
[11:34] <infinity> And very much can't with auto-removals.
[11:34] <infinity> Because auto-removals punt things temporarily all the time.
[11:34] <xnox> and then i go and rant that debian doesn't remove crap from unstable either.
[11:34] <doko> tyhicks: fscrypt ftbfs on some archs, just in case you don't expect that ;p
[11:34] <xnox> because auto-removal from testing is good enough.
[11:35] -queuebot:#ubuntu-release- New: accepted node-gulp-newer [sync] (bionic-proposed) [1.3.0-1]
[11:35] <xnox> infinity, i wish these would be processed.... t that debian doesn't remove crap from unstable either.
 tyhicks: fscrypt ftbfs on some archs, just in case you don't expect that ;p
[11:35] <xnox> bah
[11:35] <xnox> infinity, https://bugs.launchpad.net/ubuntu/+bugs?field.tag=u8rm
[11:35] <doko> ?
[11:35] <xnox> doko, miss-paste
[11:36] <doko> and I thought you turned on echo mode for my comments ;)
[11:37] -queuebot:#ubuntu-release- New binary: node-gulp-newer [amd64] (bionic-proposed/none) [1.3.0-1] (no packageset)
[11:38] -queuebot:#ubuntu-release- New: accepted node-gulp-newer [amd64] (bionic-proposed) [1.3.0-1]
[11:42] <LocutusOfBorg> new run started
[11:43] <infinity> Won't be this one, I don't think.
[11:44] <infinity> Seems to have started 2 minutes before the archive was published. :P
[11:44] <doko> can that be better triggered?
[11:45] -queuebot:#ubuntu-release- New binary: diet [ppc64el] (bionic-proposed/none) [2.8.0-1ubuntu7] (no packageset)
[11:46] <infinity> It's not so much a triggering issue as it is that long runs delay the next.
[11:47] <infinity> (Yes, there's a TODO to also get faster triggering, but when britney is taking 14 minutes, as well as other archive reports adding to that, we get what we get)
[11:48] -queuebot:#ubuntu-release- New binary: diet [amd64] (bionic-proposed/none) [2.8.0-1ubuntu7] (no packageset)
[11:48] -queuebot:#ubuntu-release- New binary: diet [s390x] (bionic-proposed/none) [2.8.0-1ubuntu7] (no packageset)
[11:48] -queuebot:#ubuntu-release- New binary: diet [i386] (bionic-proposed/none) [2.8.0-1ubuntu7] (no packageset)
[11:48] <infinity> xnox: So, you complained about it and then fixed it?
[11:49] <xnox> infinity, yes because previously i've been told to fix things than demand their removal.
[11:50] <ginggs> infinity: slow removals are slow... if only there were people volunteering to join ubuntu-archive ;)
[11:50] <xnox> infinity, colin.... steve...
[11:50] <infinity> xnox: "Removed from Debian and no rdeps" has always been a valid reason to ask for removal.
[11:50] -queuebot:#ubuntu-release- New: rejected diet [amd64] (bionic-proposed) [2.8.0-1ubuntu7]
[11:50] -queuebot:#ubuntu-release- New: rejected diet [ppc64el] (bionic-proposed) [2.8.0-1ubuntu7]
[11:50] -queuebot:#ubuntu-release- New: rejected diet [i386] (bionic-proposed) [2.8.0-1ubuntu7]
[11:50] -queuebot:#ubuntu-release- New: rejected diet [s390x] (bionic-proposed) [2.8.0-1ubuntu7]
[11:50] <infinity> xnox: When those conditions aren't met is when we tell you to stop saying "let's just remove it".
[11:50] <xnox> thanks!
[11:50] <cjwatson> Yeah, I never told you to not remove things when they'd been removed from Debian and had no rdeps.
[11:51] <infinity> And I guarantee Steve didn't, cause he's more removal-happy than I like.
[11:51] <xnox> so how about these things then? https://bugs.launchpad.net/ubuntu/+bugs?field.tag=u8rm
[11:51] <jbicha> does removed from Debian sometimes mean "removed from Debian Testing" here?
[11:51] <infinity> I saw the paste the first time.
[11:51] <infinity> jbicha: No.
[11:51] <xnox> security team is begging to remove click =/
[11:52] <infinity> jbicha: Removed from testing is completely meaningless these days.
[11:52] <xnox> sometimes its real, but often it is not.
[11:52] <xnox> and will come back in a month or two.
[11:52] <infinity> xnox: I thought something was blocking click removal the last time we looked at this stack.
[11:53] <infinity> xnox: If that's no longer true, I'm happy to revisit.
[11:54] <infinity> xnox: Also, do you have some sort of sign-off from responsible parties for each of these?  I've been told a few times that we don't just get to decide "that was a phone tihng, no one cares anymore" all by ourselves.
[11:54] <infinity> (if we did, we'd remove mir too, for instance)
[11:54] <xnox> infinity, we will not remove mir, mir is stills upported.
[11:54] <xnox> i don't see how mir is entagled yet, one sec.
[11:54] <infinity> xnox: Yes.  I know.  But you see my point.
[11:55] <xnox> infinity, all the python3-click stuff is the real python-click, not our click packages.
[11:55] <jbicha> infinity: can we remove and see if anyone complains?
[11:55] <infinity> xnox: Where's your evidence, other than "xnox, who never worked on this stack, said so" that all of these packages are fair game?
[11:55] <xnox> infinity, and click-apparmor/click-systemd/click-bin-path are leaf things.
[11:55] <xnox> infinity, the bit of merge proposal signed off by wili cooke, laney, security team?
[11:56]  * xnox is not sure i spelled wil right
[11:56] <xnox> infinity, listing all the removals...?
[11:56] <infinity> xnox: Which isn't linked on the bugs, and you haven't FedExed me a hard copy.
[11:56] <infinity> xnox: I'm not big on doing things based on faith.
[11:57] <infinity> Maybe I missed some smoke signals?
[12:01] <xnox> infinity, but e.g. https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1713710 you do see jdstrand saying please nuke this, right?
[12:01] <xnox> infinity, asked for will cooke to comment again on all of these bugs, in plain sight....
[12:01] <infinity> xnox: Yeah, I'm not questioning click, but your bug search is a lot more than click.
[12:02] <infinity> xnox: For instance, while I would *love* to remove oxide-qt (and find a time machine, and remove it three years ago), people spent a lot of time telling me it was important, even post-post-phone.
[12:02] <infinity> xnox: So, I need people who aren't you to tell me it's not anymore.
[12:02] <jbicha> how recently was that, for oxide-qt?
[12:02] <infinity> jbicha: Like I said, post-post-phone, so in the last 6mo.
[12:04] <xnox> infinity, it's the stuff from https://code.launchpad.net/~xnox/ubuntu-seeds/unity8-removals/+merge/323615
[12:04] <xnox> infinity, there are conflicting singnals from conflicting groups.
[12:04] <xnox> infinity, hence e.g. i did add a kiosk seed to keep track of things we are committing to keep. like mir and miral stuff.
[12:06] <xnox> infinity, plus some people did not realise that removal from $dev doesn't remove things from xenial, or the snap store =/
[12:06] <infinity> xnox: So, for instance, the inline comments there state they want to keep content-hub, but you filed for removal.
[12:06] <xnox> infinity, correct, because that has changed later =/
[12:07] <xnox> infinity, they claimed they wanted it into the kiosk, seed, but then backed down from it.
[12:07] <xnox> infinity, they did land the massive merge that dropped content hub deps from qtubuntu / qtmir last cycle, no?
[12:07] <xnox> (they needed content hub, until that merge landed)
[12:08] <xnox> infinity, and content-hub is gone now, and nobody is screaming.
[12:08] <infinity> Err, yeah, I mixed up content-hub and media-hub there.
[12:08] <Laney> I asked for that merge proposal to be updated
[12:08] <xnox> infinity, there are no comments about media-hub it seems.
[12:08] <xnox> Laney, true.
[12:09] <infinity> Anyhow, this is helpful, but it also seems very lacking in some sort of final consensus.
[12:09] <xnox> Laney, is the format it was in previously good enough? just drop the lines that have been processed, and list only the things that are still to be removed?
[12:09] <infinity> Happy to whack click* though.
[12:09] <Laney> It was reasonably useful as a way to comment on individual items
[12:10] <xnox> infinity, well click-*, we still have things build-dep on libclick-dev. But without removing click itself, just yet, due to click-* rdeps
[12:10] <xnox> infinity, i do not want removals to increase uninstallable counts, because britney.
[12:10] <xnox> infinity, hence leaf-first removals.
[12:10] <infinity> Reverse-Build-Depends
[12:10] <infinity> [12:10] <infinity> * click-apparmor
[12:10] <infinity> * click-bin-path
[12:10] <infinity> * click-systemd
[12:10] <infinity> * unity-scopes-api
[12:11] <infinity> And unity-scopes-api is still elsewhere entangled, if I recall.
[12:11] <infinity> Which is where we were at last time we talked about this.
[12:11] <xnox> infinity, last one is a funny one....
[12:11] <infinity> Right, url-dispatcher hell.
[12:11] <infinity> xnox: So, no, I can't action this.  HTH, HAND.
[12:11] <xnox> Laney, is unity-scopes-api u8 or u7 thing? and will clicks be supported going forward?
[12:12] <xnox> infinity, HTH?
[12:12] <xnox> =)
[12:12] <infinity> Hope That Helps.
[12:12] <Laney> Dunno, sorry, I'm a bit busy right now
[12:12] <xnox> infinity, you can remove click-apparmor
[12:12] <xnox> no?
[12:12] <infinity> No point until it's all on the chopping block.
[12:12] <xnox> ok
[12:12] <infinity> Sort out the url-dispatcher mess.
[12:12] <infinity> Then come back.
[12:12] <xnox> infinity, my uploads removing url-dispatcher got reverted by seb128
[12:13] <xnox> infinity, so i need to what, raise it to the TC?
[12:13] <jbicha> xnox: was that intentional or was that just because you refuse to use the Vcs like we ask?
[12:13] <xnox> infinity, seb128 does not have time himself to remove url-dispatcher dependencies
[12:13] <infinity> Well, url-dispatcher itself may be good and wonderful, it's url-dispatcher linking libunity-scopes1.0 that's likely where the break needs to happen.
[12:14] <infinity> But maybe both need to go, I dunno.  Not my call.
[12:14] <xnox> jbicha, if that team doesn't like the work offered, that team can do the work themselves.
[12:15] <infinity> jbicha: "Didn't use the VCS" should never be an excuse for accidental reverts.  We don't build from the VCS, it's not authoritative.
[12:15] <infinity> Even bileto got this right. :P
[12:15] <xnox> infinity, it was not accidental. it was intentional. "revert xnox upload for not using vcs" that revert upload was also done not using vcs.
[12:15] <infinity> One of the few things it did right.
[12:15] <jbicha> oh come on, xnox blatanly refuses to use the bzr branch despite being asked politely many times
[12:16] <xnox> infinity, i like how url-dispatcher has a loop onto itself via unity-scopes-api
[12:17] <infinity> jbicha: Well, I can't speak to any ongoing feuds there, but while I don't "blatantly refuse", I often rapid-fire a fix at the archive and don't have time to go checking for and checking out everyone's pet VCS to make sure the changes aren't lost.
[12:17] <infinity> But I also live in some weird era all by myself, I guess, where I debdiff before I upload.
[12:18] <jbicha> infinity: we don't have a problem with you, xnox's words and actions went further
[12:18] <jbicha> and this is the second time recently that xnox brought this up so I thought I would respond this time
[12:18] <xnox> infinity, i was told to commit no change rebuilds for boost transitions before =)))))))
[12:19] <infinity> Mmm, look at all those tasty ACCEPTED mails.
[12:20] <seb128> xnox, you have been asked several time nicely to please use the vcs or hand a debdiff to us if you can't be bothered but to not cowboy uploads for that set without review or vcs use, it's not that much to ask is it?
[12:20] <seb128> anyway we had that discussion for hours and I doubt it leads to something this time so I'm not going to argue
[12:20] <xnox> seb128, please remove packages from the archive that are no longer maintained.
[12:20] <seb128> just re-state that for those who don't have context
[12:20] <xnox> seb128, however you like.
[12:21] <xnox> seb128, e.g. url-dispatcher dependency chains - either with removals, source code changes / conditionalising code, etc. as you wish. it's all yours.
[12:21] <infinity> Or unity-scopes-api.
[12:22] <infinity> Which I made even worse this cycle by making it build-dep on g++-6. :P
[12:22] <xnox> seb128, how do i escalate this request, as it has been overdue. It was due to remove u8 deps for artful release.
[12:22] <xnox> universe is not a graveyard, things we deprecate we must remove from the archive - for example old toolchains, upstart, etc.
[12:23] <xnox> seb128, infinity - last time i've asked seb128 to handle these removals, the way he wants them to be done, he refused to do so, citing the lack of time.
[12:23] <seb128> you can remove a good part of universe by that definition
[12:23] <xnox> seb128, i'm talking about canonical-upstream, never in debian, deprecated project.
[12:24] <seb128> xnox, stop being childish
[12:24] <seb128> it's not that hard to send us a debdiff or commit to a vcs you have commit access to
[12:24] <seb128> all those discussions are orthogonal to the point
[12:24] <seb128> you are just making a point of not wanting to respect our workflow for whatever reason
[12:25] <seb128> you could have done a commit by 10/10th of the efforts you are putting into arguing there
[12:25] <seb128> that said I go back to do work, if you are interested in working with others rather than being confrontational you are still welcome to send us  a patch or to commit to the vcs listed in control and dput
[12:27] <seb128> (1/10th)
[12:34] <infinity> Re-enabling the publisher to publish the icu transition to the release pocket.
[12:41] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-384 [source] (xenial-proposed) [384.90-0ubuntu0.16.04.2]
[12:43] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-384 [source] (zesty-proposed) [384.90-0ubuntu0.17.04.2]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-384 [source] (artful-proposed) [384.90-0ubuntu3.17.10.1]
[12:58] <jhodapp> xnox, infinity what about media-hub exactly?
[12:59] <xnox> jhodapp, is it a u8 thing and dead; or a useful thing stand alone; is it supported as part of u7 desktop? is it supported as part of gnome desktop? should it be removed? is it used by mir/kiosk?
[12:59] <xnox> general archeology
[13:00] <infinity> jhodapp: It's on xnox's "remove from the archive for 18.04" list.  Should it be?
[13:00] <xnox> yeah that ^
[13:01] <jhodapp> xnox, it can be useful with u7, u8 although I haven't actually seen someone take it up yet
[13:01] <jhodapp> it's more that it's potentially useful
[13:06] <jbicha> joedborg: could you give an answer that looks more like yes or no ? ;)
[13:06] <jbicha> jhodapp: ^
[13:07] <jhodapp> jbicha, depends, how much from u8's ecosystem are we keeping around in general?
[13:09] <jbicha> unity8 itself was removed from Ubuntu 17.10, what's left are some old dependencies
[13:10] <jhodapp> jbicha, which ones are you keeping around for example? I can better answer your question then
[13:11] <jbicha> mir is kept because of Canonical kiosk projects, I'm not aware of much else specifically from Unity8 that we still are explicitly keeping
[13:12] <jbicha> if you wanted to run Unity8 on Ubuntu 17.10, you would need dozens of packages that have been removed
[13:15] <jbicha> Unity7 is being kept around as long as it works although we did remove Ubuntu Online Accounts which makes Unity not as useful in 17.10 as Unity was in 17.04
[13:16] <jhodapp> jbicha, ok, so this is removing from the main archive and not universe? Or is this complete removal?
[13:16] <infinity> Complete.
[13:46] <jhodapp> ok, well it's probably worth removing then since you're doing 99% of the others
[14:14] <LocutusOfBorg> are britney/publisher running now?
[14:19] <LocutusOfBorg> infinity, your fpc fix, I'm going to try a force-sync, because the new upstream release (according to the fact that this was an upstream cherry-pick) should include it
[14:19] <LocutusOfBorg> even if that file is still untouched, I see some case-sensitiveness fixes somewhere around it
[14:33] <infinity> LocutusOfBorg: britney will be back on shortly.
[14:33] <infinity> LocutusOfBorg: And I don't even recall what fpc fix you're referring to. :)
[14:33] <LocutusOfBorg> infinity, I *think* this was some sort of testsuite fix
[14:34] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/fpc/3.0.2+dfsg-5ubuntu1 probably making autopkgtests sad, because the -5 plain upload was building on affected arches
[14:35] <LocutusOfBorg> history seems to agree with me http://autopkgtest.ubuntu.com/packages/f/fpc/artful/amd64
[14:35] <LocutusOfBorg> confirmed, lets try to drop and see what happens https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/f/fpc/20170914_190934_5f054@/log.gz
[14:35] <infinity> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875838
[14:36] <LocutusOfBorg> thanks for the britney restore
[14:36] <infinity> Yes, they claim it's fixed.  I didn't check to be sure.
[14:36] <LocutusOfBorg> debdiff looks promising TBH
[14:36] <LocutusOfBorg> btw I would upload perl since queues are empty
[14:41] <LocutusOfBorg> uploading in 30 minutes
[14:41] -queuebot:#ubuntu-release- Unapproved: broadcom-sta (xenial-proposed/multiverse) [6.30.223.271-3~16.04.1 => 6.30.223.271-3~16.04.3] (no packageset)
[14:48] <infinity> auto-sync enabled.
[14:49] -queuebot:#ubuntu-release- New binary: fpc [armhf] (bionic-proposed/universe) [3.0.4+dfsg-1] (no packageset)
[14:50] <acheronuk> \o/
[14:51] <acheronuk> but with the auto-sync and Qt transition, I may as well take a few days off!
[14:53] <LocutusOfBorg> uploading perl *now* then
[14:54] <acheronuk> uh oh
[14:55] -queuebot:#ubuntu-release- New binary: fpc [i386] (bionic-proposed/universe) [3.0.4+dfsg-1] (no packageset)
[14:56] <tsimonq2> infinity: Qt transition started
[14:56] -queuebot:#ubuntu-release- New binary: fpc [arm64] (bionic-proposed/universe) [3.0.4+dfsg-1] (no packageset)
[14:58]  * LocutusOfBorg sits on the river, waiting for the world to explode
[14:58]  * tsimonq2 joins LocutusOfBorg 
[14:58] -queuebot:#ubuntu-release- New sync: libayatana-appindicator (bionic-proposed/primary) [0.5.2-1]
[14:59]  * acheronuk finds a nice riverside pub with a beer garden
[14:59] -queuebot:#ubuntu-release- New binary: fpc [amd64] (bionic-proposed/universe) [3.0.4+dfsg-1] (no packageset)
[15:01] <LocutusOfBorg> node-babel seems to need bootstrapping
[15:01] <LocutusOfBorg> so, if anybody has the powers...
[15:04] -queuebot:#ubuntu-release- Unapproved: acpi-call (xenial-proposed/universe) [1.1.0-2 => 1.1.0-2ubuntu1] (no packageset)
[15:04] -queuebot:#ubuntu-release- Unapproved: dm-writeboost (xenial-proposed/universe) [2.2.6-1~16.04.1 => 2.2.6-1~16.04.2] (no packageset)
[15:05] <tsimonq2> Qt needs some moar poking, things should be syncing then depwait. QtBase is uploaded, and when I get home in ~ 5 hours I'll upload the rest with deltas.
[15:05] -queuebot:#ubuntu-release- Unapproved: ndiswrapper (xenial-proposed/universe) [1.60-3~ubuntu16.04.1 => 1.60-3~ubuntu16.04.2] (no packageset)
[15:06] <tsimonq2> For now, the queue goes to perl then :P
[15:06] -queuebot:#ubuntu-release- Unapproved: dahdi-linux (xenial-proposed/universe) [1:2.10.2~dfsg-1ubuntu1 => 1:2.10.2~dfsg-1ubuntu2] (no packageset)
[15:07] -queuebot:#ubuntu-release- New: accepted fpc [amd64] (bionic-proposed) [3.0.4+dfsg-1]
[15:07] -queuebot:#ubuntu-release- New: accepted fpc [armhf] (bionic-proposed) [3.0.4+dfsg-1]
[15:07] -queuebot:#ubuntu-release- New source: python-monasca-statsd (bionic-proposed/primary) [1.7.0-1ubuntu1]
[15:07] -queuebot:#ubuntu-release- New: accepted fpc [arm64] (bionic-proposed) [3.0.4+dfsg-1]
[15:07] -queuebot:#ubuntu-release- New: accepted fpc [i386] (bionic-proposed) [3.0.4+dfsg-1]
[15:08] <jbicha> flexiondotorg: do you know if those ayatana-indicator packages will cause any problems being synced to Ubuntu?
[15:09] <flexiondotorg> jbicha: I spoke to sunweaver about this last week.
[15:09] <flexiondotorg> My understanding is all the libraries have different namespaces.
[15:09] <flexiondotorg> So no collisions.
[15:10] <jbicha> ok, sounds fun 🤠
[15:11] <LocutusOfBorg> and remmina supports them both
[15:11] <LocutusOfBorg> which one to choose? right now it picked up the alternate dependency, just because ayatana is not available.
[15:12] <LocutusOfBorg> A no-change rebuild will make it pick the new one, should we MIR it? my goal is to include all the changes in Debian, the delta is near zero now
[15:12] <jbicha> LocutusOfBorg: Debian just switched the order, but I believe we'll need to revert that for Ubuntu for now
[15:13] <jbicha> I don't think any Ubuntu desktop supports the new ayatana-appindicator but several support the old one so we shouldn't change yet
[15:13] <sil2100> infinity, apw: I was fixing biometryd that's FTBFS with the new boost, had it fixed besides a qml unittest that just keeps failing - and now after a quick chat with kenvandine we noticed that it's just a leaf package that's not used anywhere, so...
[15:13] <LocutusOfBorg> ok so from the next merge I'll swap them
[15:14] <sil2100> infinity, apw: can we just remove it?
[15:14] <sil2100> Pretty please?
[15:14] <sil2100> No rdeps, not seeded anywhere, not caring (was for the turbo device for touch)
[15:15] <jbicha> biometryd is listed on LP: #1713076
[15:16] <sil2100> jbicha: thanks
[15:17] <sil2100> Let me comment there
[15:18] -queuebot:#ubuntu-release- New binary: qtbase-opensource-src [ppc64el] (bionic-proposed/main) [5.9.2+dfsg-4ubuntu1] (kubuntu, qt5, ubuntu-desktop)
[15:19] <apw> sounds reasonable to me
[15:23] <xnox> infinity, well done you =) the drop on http://people.canonical.com/~ubuntu-archive/proposed-migration/history.html looks really nice =)
[15:26] <sil2100> Well job, good done
[15:27] <bdmurray> sil2100: Could you release some SRUs I've done?
[15:28] <bdmurray> sil2100: update-manager, ubuntu-release-upgrader and cracklib2
[15:28] <sil2100> bdmurray: sure, you mean from -proposed to -updates?
[15:28] <bdmurray> sil2100: indeed
[15:30] <LocutusOfBorg> mapreri, sync opencv from experimental? (this is a joke)
[15:31] <LocutusOfBorg> but 3.3.1 in experimental is a sensible thing
[15:32] -queuebot:#ubuntu-release- New binary: qtbase-opensource-src [s390x] (bionic-proposed/main) [5.9.2+dfsg-4ubuntu1] (kubuntu, qt5, ubuntu-desktop)
[15:51] -queuebot:#ubuntu-release- Unapproved: unity-control-center (xenial-proposed/main) [15.04.0+16.04.20170214-0ubuntu1 => 15.04.0+16.04.20170214-0ubuntu2] (ubuntu-desktop)
[15:55] <xnox> infinity, i have dd'ed artful desktop iso onto a usb stick; booting it on lenovo idepad it offers me two options "uefi usb boot" and "usb hdd boot".
[15:55] <xnox> uefi works
[15:56] <xnox> usb hdd ends up with isolinux prompt no config found
[15:56] <xnox> is it normal, or do we expect isolinux / legacy boot of usb work? as far as i can tell, it works with xenial.iso
[16:04] <nacc> slangasek: sorry to bug you again, upstream php did another microrelease while my SRUs are in the unapproved queues. I think it makes sense to just update to those, can you reject src:php7.0 from xenial src:php7.1 from artful? I'll reupload both today after updating php7.1 in bionic.
[16:06] -queuebot:#ubuntu-release- Unapproved: rejected php7.0 [source] (xenial-proposed) [7.0.24-0ubuntu0.16.04.1]
[16:07] -queuebot:#ubuntu-release- Unapproved: rejected php7.1 [source] (artful-proposed) [7.1.10-0ubuntu0.17.10.1]
[16:07] <rbasak> nacc, slangasek: ^ done
[16:07] <nacc> rbasak: thanks!
[16:12] <Laney> xnox: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/c/clblas/20171031_154729_bfa18@/log.gz
[16:12] <Laney> that is the one
[16:13] <xnox> Laney, wow ^_^
[16:13] <xnox> i have seen a miracle now
[16:20] <Laney> a halloween present for you
[16:35] <tsimonq2> Laney: On a scale from no-change rebuild to merging debian-installer from Debian and losing all your work 10 times in a row, how much sp00k? :P
[16:37] <Laney> tsimonq2: New GHC upload when you've reached level 15 of a Haskell transition
[16:37] <Laney> <insert horror movie scream>
[16:38] <tsimonq2> Laney: damn that's spooky :P
[16:42] -queuebot:#ubuntu-release- New binary: qtbase-opensource-src [i386] (bionic-proposed/main) [5.9.2+dfsg-4ubuntu1] (kubuntu, qt5, ubuntu-desktop)
[16:43] <LocutusOfBorg> hey please don't make haskell jokes! they are too scary to me
[16:44] <tsimonq2> Can someone pretty please review qtbase in NEW so we can have a quick and easy Qt transition? <3
[16:44] <LocutusOfBorg> btw a good joke: perl takes longer on amd64 than armhf and arm64 lol
[16:44] <tsimonq2> LocutusOfBorg: loll
[16:44] <LocutusOfBorg> "quick and easy QT transition" <-- its a trap!
[16:45] -queuebot:#ubuntu-release- New binary: qtbase-opensource-src [armhf] (bionic-proposed/main) [5.9.2+dfsg-4ubuntu1] (kubuntu, qt5, ubuntu-desktop)
[16:45] <LocutusOfBorg> tsimonq2, unfortunately that slow amd64 makes the publisher sad because the arch:all aren't available
[16:45] <LocutusOfBorg> I remember britney showing sadness for this
[16:47] <tsimonq2> LocutusOfBorg: lol Qt 5.9.2 transition should be quick and painless now that I'm a MOTU
[16:47] <tsimonq2> And yeah, arch:all :/
[17:05] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (xenial-proposed) [2.408.22]
[17:07] -queuebot:#ubuntu-release- New binary: qtbase-opensource-src [arm64] (bionic-proposed/main) [5.9.2+dfsg-4ubuntu1] (kubuntu, qt5, ubuntu-desktop)
[17:07] <slangasek>  sbuild-build-depends-core-dummy : Depends: build-essential but it is not going to be installed
[17:07] <slangasek> that's not good
[17:07] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.21 => 2.408.22] (desktop-core)
[17:11] <sil2100> bdmurray: as for https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1725605, I see someone mentioned the fix 'didn't work' and I saw it being switched to verification-failed
[17:11] <sil2100> bdmurray: is this still good to go?
[17:26] <bdmurray> sil2100: the didn't work guy did have universe enabled
[17:26] <bdmurray> sil2100: and the v-failed autotagging was unrelated
[17:28] <xnox> LocutusOfBorg, hey, do you think we can build perl uploads via a bileto ppa? create a new ppa on bileto.ubuntu.com; then copy package from debian there; wait for it to build on all architectures; click finalise to land into bionic-proposed?
[17:28] <bdmurray> sil2100: There's been a bad bug triager of u-r-u bugs too
[17:28] <xnox> LocutusOfBorg, this way all architectures will see the new modules arch:all build at the same time as the binary builds.
[17:28] <xnox> LocutusOfBorg, our amd64 is one of the slower arches, and we have build-essentials uninstallable on ppc64le/s390x for a long time, until amd64 catches up =( and things are not nice.
[17:28] <xnox> LocutusOfBorg, what do you think about that?
[17:30] <slangasek> RAOF: hi, could I ask you to have a look today at the livecd-rootfs in xenial-proposed queue?  it fixes a remaining regression that was introduced when launchpad switched to containers for livefs builds
[17:30] <slangasek> RAOF: it also includes an unrelated but small change that I haven't bothered filing SRU paperwork for because livecd-rootfs
[17:50] -queuebot:#ubuntu-release- Unapproved: ubiquity (xenial-proposed/main) [2.21.63.4 => 2.21.63.5] (core)
[17:51] -queuebot:#ubuntu-release- Unapproved: network-manager-applet (xenial-proposed/main) [1.2.6-0ubuntu0.16.04.3 => 1.2.6-0ubuntu0.16.04.4] (kubuntu, ubuntu-desktop)
[18:18] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/lazarus/1.8.0~rc5+dfsg-1/+build/13649697
[18:18] <LocutusOfBorg> can you please hold on autosync? perl is probably making something look bad on dpkg side
[18:18] <LocutusOfBorg> I need to figure  it out
[18:18] <LocutusOfBorg> xnox, last time I tried, I failed in creating a bileto ppa :/
[18:18] <LocutusOfBorg> I created a ticket, I didn't find the way to create a ppa, and I closed it after some minutes of digging
[18:19] <LocutusOfBorg> or maybe the issue your are talking about is the lazarus one...
[18:25] <LocutusOfBorg> mehh, it is building now
[18:26] <LocutusOfBorg> so nevermind
[18:26] <LocutusOfBorg> I'll retry whatever failed after perl upload
[18:43] <sil2100> xnox: I'm looking at your xenial ubiquity upload, was wondering why did you remove the test_secure_ap_can_enter_password test? Is it no longer a valid test with the enterprise changes?
[18:56] <sil2100> xnox: ok, I see it's what happened to bionic/artful, so yeah, let me just agree that it's how it should be
[18:56] <LocutusOfBorg> perl, sweet per
[18:57] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (xenial-proposed) [2.21.63.5]
[19:05] -queuebot:#ubuntu-release- Unapproved: accepted network-manager-applet [source] (xenial-proposed) [1.2.6-0ubuntu0.16.04.4]
[19:11] <sil2100> xnox, doko: btw. I am building dbus-cpp for the boost transition in https://bileto.ubuntu.com/#/ticket/3019
[19:11] <sil2100> Might jam some additional touch-related packages there
[19:11] <sil2100> xnox, doko: I'll be ignoring those that we might potentially remove, as it's a waste of time then
[19:53] <jbicha> the logs look to me like the autosync is crashing? https://people.canonical.com/~ubuntu-archive/auto-sync/2017-10-31/
[19:56]  * jbicha bisects to figure out when it started
[19:58] <jbicha> https://people.canonical.com/~ubuntu-archive/auto-sync/2017-10-03/ before the 23:00 log
[20:19] -queuebot:#ubuntu-release- Unapproved: murano-dashboard (artful-proposed/universe) [1:4.0.0-0ubuntu1 => 1:4.0.0-0ubuntu1.1] (openstack)
[20:19] -queuebot:#ubuntu-release- Unapproved: murano-dashboard (zesty-proposed/universe) [1:3.2.0-0ubuntu1 => 1:3.2.0-0ubuntu2] (openstack)
[20:29] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [17.1-25-g17a15f9e-0ubuntu1~16.04.1 => 17.1-27-geb292c18-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[20:34] -queuebot:#ubuntu-release- Unapproved: accepted unity-control-center [source] (xenial-proposed) [15.04.0+16.04.20170214-0ubuntu2]
[20:34] -queuebot:#ubuntu-release- Unapproved: cloud-init (zesty-proposed/main) [17.1-25-g17a15f9e-0ubuntu1~17.04.1 => 17.1-27-geb292c18-0ubuntu1~17.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[20:39] -queuebot:#ubuntu-release- Unapproved: cloud-init (artful-proposed/main) [17.1-25-g17a15f9e-0ubuntu1~17.10.1 => 17.1-27-geb292c18-0ubuntu1~17.10.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[20:47] <smoser> hey. those are blackboxsw and i uploads for cloud-inti fix that is in -proposed. small change to what is there... woudl apprediate someone looking
[20:54] <tsimonq2> The Qt 5.9.2 transition is currently blocked on qtbase being in NEW.
[20:54] <tsimonq2> I'd appreciate it if someone could take a look.
[21:10] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (artful-proposed) [3:12.0.0-0ubuntu2.2]
[21:15] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (zesty-proposed) [3:11.0.3-0ubuntu3.1]
[21:33] <slangasek> tsimonq2: how painful will that transition be once it does clear new?
[21:59] <tsimonq2> slangasek: Minimal, it's a bugfix Qt release and I now have upload access to 75% of what I need to
[22:01] <tsimonq2> slangasek: In fact, I'll be surprised if it lasts until the weekend...
[22:02] <slangasek> tsimonq2: having access to upload is different than the packages building reliably.  how many packages have to be rebuilt, how many of those currently fail to build, etc?
[22:02] <tsimonq2> slangasek: (most if not all blockers were dealt with during the last transition)
[22:03] <tsimonq2> slangasek: Well at minimum I think there's ABI changes for qtbase and qtdeclarative. From the test rebuilds I've done with sbuild, every build that passed last transition passes this time as well.
[22:04] <tsimonq2> (when I say "I think" I'm saying that those are the packages I *know* have ABI changes, others *might* but I'm not entirely sure)
[22:05] <slangasek> tsimonq2: ok cool
[22:06] <slangasek> jbicha: has auto-sync really been failing consistently since the 3rd?  the few logs I've looked at all seem to have different errors
[22:16] <xnox> it will clog the autopkgtest infra which is running at reduced capacity due to lcy redeploy, no?
[22:18] <slangasek> xnox: is lcy not already back up?
[22:18] <slangasek> it looks up to me
[22:19] <xnox> i see red at https://launchpad.net/builders and not as many builders as usually, but i might be wrong
[22:19] <xnox> and many builders in "cleaning" state is not nice either
[22:21] <slangasek> xnox: otoh there are builds started within the past hour; and I see running autopkgtest VMs in lcy01.  I think we're just working through the backlog now
[22:25] <tsimonq2> slangasek: New qtbase upload incoming, accidentally forgot something.
[22:27] <tsimonq2> (well, as soon as my sponsor uploads it ;) )
[22:31] <jbicha> slangasek: I mean I didn't read all the logs but there are lots of failures since then
[22:35] <cjwatson> xnox: not especially bad, but I'm doing an autostab anyway
[22:35] <cjwatson> xnox: fewer builders is because there's an lcy01 redeployment in progress, so lcy01 has three fewer compute nodes than usual because they're part of the redeploy
[22:36] <cjwatson> xnox: hence 1/3 fewer vbuilders in lcy01 because otherwise they wouldn't fit
[22:36] <cjwatson> slangasek: ^-
[22:36] <slangasek> ok, so the redeploy is still in process
[22:36] <cjwatson> right, it just hasn't yet involved taking down all of lcy01
[22:36] <slangasek> ah
[22:37] -queuebot:#ubuntu-release- Unapproved: rejected lxcfs [source] (artful-proposed) [2.0.8-0ubuntu1]
[22:38] <slangasek> tsimonq2: is this accidentally forgotten thing in any way related to the circular build-dependency between qttools-opensource-src and qtbase-opensource-src/amd64?
[22:39] <slangasek> tsimonq2: it would probably be a bad idea to accept the binaries on !amd64 archs
[22:39] <tsimonq2> slangasek: Yeah
[22:40] <tsimonq2> slangasek: Hm, it's late on the side of $sponsor, could you please upload this? http://paste.ubuntu.com/25861608/
[22:41] <slangasek> y
[22:42] <tsimonq2> y = . or y = why ?
[22:43] <slangasek> y = gah
[22:43] <slangasek> I mean yes
[22:44] <tsimonq2> Ok, thanks
[22:44] <nacc> lol, I'm going to use that "y = gah"
[22:44] <tsimonq2> lol
[22:44] <slangasek> nacc: xnox-approved
[22:44] <nacc> slangasek: :)
[22:45] <tsimonq2> slangasek: My plan is to apply for PPU after this transition so there shall be no more "y"s :P
[22:47] -queuebot:#ubuntu-release- Unapproved: lxcfs (artful-proposed/main) [2.0.7-0ubuntu5 => 2.0.8-0ubuntu1~17.10.1] (edubuntu, ubuntu-server)
[22:50] -queuebot:#ubuntu-release- Unapproved: lxcfs (xenial-proposed/main) [2.0.7-0ubuntu1~16.04.2 => 2.0.8-0ubuntu1~16.04.1] (edubuntu, ubuntu-server)
[22:52] -queuebot:#ubuntu-release- Unapproved: lxcfs (zesty-proposed/main) [2.0.7-0ubuntu1~17.04.2 => 2.0.8-0ubuntu1~17.04.1] (edubuntu, ubuntu-server)
[23:03] -queuebot:#ubuntu-release- New source: rsplib (bionic-proposed/primary) [3.0.1-1ubuntu5]
[23:08] -queuebot:#ubuntu-release- New: accepted rsplib [source] (bionic-proposed) [3.0.1-1ubuntu5]
[23:21] -queuebot:#ubuntu-release- New binary: qtbase-opensource-src [ppc64el] (bionic-proposed/main) [5.9.2+dfsg-4ubuntu2] (kubuntu, qt5, ubuntu-desktop)
[23:26] -queuebot:#ubuntu-release- New binary: qtbase-opensource-src [s390x] (bionic-proposed/main) [5.9.2+dfsg-4ubuntu2] (kubuntu, qt5, ubuntu-desktop)
[23:28] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.22]
[23:34] -queuebot:#ubuntu-release- Unapproved: accepted percona-xtradb-cluster-5.6 [source] (xenial-proposed) [5.6.34-26.19-0ubuntu0.16.04.2]
[23:44] -queuebot:#ubuntu-release- Unapproved: accepted percona-xtradb-cluster-5.6 [source] (zesty-proposed) [5.6.34-26.19-0ubuntu1.1]