=== nudtrobert1 is now known as nudtrobert
=== fginther` is now known as fginther
=== xnox_ is now known as xnox
[16:50] <cyphermox> infinity: xnox: btw, looks like d-i FTBFS now due to findutils in -proposed
[16:50] <xnox> cyphermox, fun.
[16:50] <cyphermox> yeah.
[16:51] <cyphermox> so, just a fyi, I'll look into it now
[16:56] <infinity> Ugh, why do we have the experimental findutils in xenial at all?
[16:57] <xnox> infinity, someone thought it's a good idea to follow fedora & suse =)
[16:57] <xnox> but if d-i can be fixed for that and otherwise, it would be nice.
[16:57] <infinity> Well, findutils itself needs fixing first.
[16:59] <cyphermox> d-i does need to be fixed
[16:59] <cyphermox> -perm +$something was already a deprecated way of looking for permissions
[16:59] <cyphermox> looks like it just needs to be / instead of +
[16:59] <infinity> Not implying it doesn't need fixing, but I'm not keen on us leading the way on fixing everything else that might blow up too.
[17:00] <infinity> Plus, findutils' testsuite fails on ppc64el.
[17:00] <infinity> So, whee.
[17:01] <cyphermox> infinity: of course
[17:02] <cyphermox> wasn't findutils brought up in our last team meeting anyway though?
[17:02] <cyphermox> chiluk: ^
[17:02] <xnox> please bump https://launchpad.net/ubuntu/+source/ubuntu-core-meta/0.6.11/+build/8415572
[17:02] <xnox> it's behind all the silos, which will not migrate until we migrate qt+apt which needs above
[17:04] <infinity> cyphermox: Well, I've deleted it for now.  Feel free to fix d-i anyway to remove the deprecated usage, but it should be unnecessary today.
[17:04] <cyphermox> infinity: yeah, I'll push the change in a bit. It looks like it's already fixed in Debian too
[17:04] <infinity> xnox: Scored up a bit.
[17:04] <xnox> infinity, tah.
[17:07] <xnox> http://people.canonical.com/~ubuntu-archive/transitions/html/apt.html sigh.
[17:51] <flocculant> balloons: so looking at this task - https://codein.withgoogle.com/dashboard/tasks/5278083867213824/
[17:56] <flocculant> balloons: please make sure you check it for 'flocculant knows in his head what's required so might miss what someone else needs'  missing information :D
[17:57] <balloons> :-) I'm sure it will happen, but I will check
[17:57] <flocculant> :p
[17:58] <flocculant> I did wonder if it was too much for one task tbh
[17:58] <balloons> flocculant, the actions? 1 to add the bug to Critical bugs in the add a test result section and 1 to add the bug to Bugs. That's confusing and maybe too much? The bugs are sorted automatically now
[17:59] <flocculant> flocculant: omw - sorry -release :( wrong channel ...
[20:40] <sil2100> Hello! I need to disable the system-image importer again for a while, should be back soon
[20:46] <sil2100> Latest EOD today
[22:01]  * xnox ponders to introduce haskell-libqtapt just for giggles
[22:02] <xnox> libreoffice-kde/s390x unsatisfiable Depends: kde-runtime
[22:03] <infinity> xnox: Would be because kde-runtime is dep-wat...
[22:04] <xnox> snap
[22:05] <infinity> Which goes back to libqapt, and it's impressive list of dep-waits.
[22:05] <infinity> s/it's/its/
[22:07] <xnox> which goes to qtdeclarative which is done in my ppa.
[22:07] <xnox> Laney, i think i need the rest of qt on s390x, because we have so much built in release pocket already.
[22:07] <xnox> Mirv, ^
[22:07] <xnox> i'm uploading qtdeclarative, and then getting the rest of things built.
[22:11] <xnox> ok, be back in two hours.
[22:12]  * xnox ponders when will qt+apt+popler migrate
[22:18] <xnox> infinity, is it me, or is archive publisher slow. sometimes taking more than 30minutes to publish s390x builds. or is there some networking across a pond involved there?
[22:19] <infinity> xnox: It can be slow when it's publishing the release pocket too, though it could also just be that you're impatient.
[22:20] <xnox> infinity, i expect every 5 minutes -proposed publishing =) and instant autopkgtest triggers
[22:20] <infinity> xnox: You're not going to get that.
[22:20] <xnox> infinity, i shall take long coffee breaks then =)
[22:20]  * xnox off to tesocs
[22:20]  * xnox off to tesco's
[22:32] <doko> are debian imports currently delayed or off?
[22:39] <stgraber> ^ should be a straighforward package rename + transitional binary package (and yes, I realize the name is absolutely ridiculous)
[23:32] <cjwatson> doko: They're not intentionally switched off, and the fact that (at least) openssh just got auto-synced indicates that they're not in general broken either.
[23:33] <doko> cjwatson, ahh, ok. that must have changed within the last hour
[23:33] <cjwatson> doko: Not as far as I know.
[23:33] <cjwatson> doko: Maybe you could give an example of the problem you were seeing?
[23:34] <doko> cjwatson, I wasn't able to syncpackage polymake and python2.7, but both were synced automatically 19min ago
[23:36] <doko> I'm asking because I was able to get these packages in unstable about 15h ago
[23:40] <cjwatson> doko: It arrived in the mirror sync we performed at about 16:05 UTC.  However, at that point there was a Launchpad database schema upgrade in progress, so the usual database import step didn't happen then, and only happened at its next cronned time six hours later.
[23:40] <cjwatson> doko: (that's polymake, I didn't bother to investigate python2.7 as well since it'll be the same basic sequence of events)
[23:41] <doko> cjwatson, ta, all fine now. packages are building
[23:41] <cjwatson> doko: But nothing specific to Debian imports; all cron jobs that go anywhere near the DB are disabled during schema upgrades.
[23:42] <doko> must have missed any notive about the upgrade
[23:43] <cjwatson> doko: They're routine and not typically announced widely, since actual downtime (in the sense of the webapp being out of action) is measured in seconds.  It was mentioned on #is-outage though.
[23:43] <doko> ok, I'll join that channel ...
[23:44] <cjwatson> doko: (Although I requested it, even I didn't know it was happening until it was done :-) )
[23:45] <cjwatson> But that's fine, I didn't need to know.