=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
[07:57] <caraka> I see idle builders, and my packages have been in the queue for 5 hours.  :/
[07:58] <caraka> am I broken, or am I just stuck behind the zesty rebuild?
[09:09] <cjwatson> caraka: almost certainly the latter, and the only idle builders are on ppc64el/s390x; can't be sure without a ref to your build though
=== gkadam is now known as Guest61459
=== Guest61459 is now known as gkadam
[09:38] <caraka> thanks cjwatson. As per Murphy's law, the amd64 builds reached the front of their queue after I bitched about it. Go figure. I probably just caught the buiilder's page just as a few builders finished cleaning themselves before jumping back into the fray. Cheers
[09:39] <cjwatson> caraka: yeah, there's often a 15-second idle period
[09:40] <cjwatson> or thereabouts
[09:41] <caraka> :D Murphy working overtime
[09:41] <cjwatson> ah, bunch of builders stuck cleaning though, will poke
[09:42] <caraka> that's a pretty big refactor of the whole thing, eh? and I guess it kind of has to happen all at once the first time around
[09:42] <cjwatson> there, that should help finish draining the queue
[09:42] <cjwatson> caraka: what do you mean?
[09:42] <caraka> rebuilding all of zesty at once. At least that's what it looked like to me
[09:43] <cjwatson> not in the least
[09:43] <caraka> building out the whole proposed section on top of yakkety. that's how it works with a fresh release, right?
[09:43] <cjwatson> no
[09:44] <cjwatson> we auto-sync packages that have changed in Debian unstable
[09:44] <cjwatson> after being in import freeze for a couple of months there's generally a bit of a queue of these
[09:44] <caraka> right. that's ind of what I meant. and the first time that happens with a new release, it's big
[09:44] <cjwatson> but it's usually on the order of a couple of thousand source packages, rather than all of zesty
[09:45] <cjwatson> order of magnitude difference there :)
[09:45] <caraka> I guess so. :P
[09:45] <cjwatson> a full rebuild takes more like a week to clear; the initial auto-sync runs at around half a day or less these days
[09:46] <caraka> wow. I guess that hasn;t really had to happen since the Badger days or ssomething
[09:46] <cjwatson> what, a full rebuild?
[09:46] <caraka> yes
[09:47] <cjwatson> we never rebuild everything in Ubuntu proper
[09:47] <cjwatson> but we do full test rebuilds a few times per release cycle
[09:47] <caraka> learn something new every day.
[09:48] <caraka> Well thank your for help, and I'm sure some other folks in the queue are grateful a few builders have had a nudge
[09:49] <cjwatson> no problem, should all clear out pretty soon now
[09:49] <cjwatson> the build farm requires a lot less manual babysitting than it used to
[09:50] <caraka> Silly questiin if I might - when will wily builds start to fail/reject. It must be soon.
[09:51] <caraka> Or am I getting away with it because I'm not using a recipe
[09:52] <cjwatson> it's up to the Ubuntu release team when to mark that as obsolete - it's overdue but was being held off due to an abundance of caution about products built on it
[09:53] <cjwatson> you should definitely not rely on that happening any more though
[09:57] <caraka> I don;t, and I've warned my users repeatedly that they are on borrowed time. I'm looking forward to the rejection letter.  :D  Now its time to set up some zesty test builds.
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== icey-travel is now known as icey
=== gkadam is now known as Guest6010
=== Guest6010 is now known as gkadam
=== chihchun is now known as chihchun_afk
=== daniel is now known as Guest19937
=== Guest19937 is now known as Odd_Bloke
[15:16] <nacc> is there an API in launchpadlib to obtain an arbitrary orig tarball (given a srcpkg and an upstream version)? or whereabouts I might look for that
[15:17] <dobey> i think you'd probably need some more details; but the archive endpoints would be where to start i think
[15:21] <nacc> dobey: ok, thanks -- this is for a helper tool for the server team importer, which means the version we are currently building doesn't necessarily exist, so I can't pull() it. I can extract what the upstream part is, but I guess I'd just need to find a published version with the same upstream value and pull() that
[16:15] <Promille> Hi guys. I have written a comment on a bug-thread. Does this "bump" the bug so the relevant people can see it? Thread in question: https://bugs.launchpad.net/ubuntu/+source/translate-shell/+bug/1572035?comments=all
[16:15] <ubot5`> Ubuntu bug 1572035 in translate-shell (Ubuntu) "translate-shell outdated and broken" [Undecided,New]
[16:17] <dobey> Promille: people who are subscribed to the bug get e-mail, yes
[16:21] <Promille> dobey: Hm ok. Lets hope that thats enough. The comment has a link to new version from the developer which fixes a broken package in multiverse.
=== JanC is now known as Guest59232
=== JanC_ is now known as JanC
=== PaulW2U_ is now known as PaulW2U