[11:34] <dupingping> hi, all
[12:04] <mitya57> Can someone please reject my libsignon-glib sync from binNEW (and maybe remove it from -proposed if possible)? We don't need the -dbg package in Ubuntu and I didn't intend to add new binaries without asking the current Ubuntu maintainer first.
[12:04] <mitya57> Err, s/libsignon-glib/libaccounts-glib/, the former is Ok
[12:05] <mitya57> (I will do a new upload based on current Ubuntu packaging to fix what I need, namely the s390x ftbfs.)
[12:06] <mitya57> Or, maybe, if mardy_ is online and says the sync is ok, accept it instead of rejecting :)
[13:00] <hjd> Hi all, could someone please rebuild r-bioc-genomicfeatures in Xenial? :) Looks like it failed to build because the required version of one of the dependencies hadn't been synced yet. Built without problems on my local Xenial vm.
[13:39] <szymon_g> hi
[13:39] <szymon_g> which version of python will be in the upcoming edition of ubuntu (which will be lts, won't it?)?
[13:40] <szymon_g> i.e. the one available in standard repositories, out of the box so to speak
[14:09] <hjd> Any suggestions what it means when a build failed without a log? (https://launchpad.net/ubuntu/+source/django-oauth-toolkit/0.10.0-1/+build/8760721)
[14:09] <hjd> Worked fine locally though, so will probably work if someone could trigger a rebuild of it.
[14:25] <mitya57> re my message above: nevermind, I resolved that myself
[14:26] <mitya57> hjd, retried both
[14:26] <mitya57> szymon_g, it will be 3.5
[14:26] <szymon_g> oh, thanks mitya57
[14:36] <hjd> mitya57: ty :)
[16:24] <cjwatson> hjd: When a build fails without a log, it means that LP was unable to retrieve the log from the builder at the end of the build, probably because the builder crashed.
[16:56] <hjd> cjwatson: I see. Has there been any particular issues like this recently? I've seen a couple of such failures.
[16:56] <hjd> For instance https://launchpad.net/ubuntu/+source/r-bioc-biovizbase/1.18.0-1/+build/8272916 and https://launchpad.net/ubuntu/+source/globus-xio-udt-driver/1.19-2/+build/8760547, where at least in the former case it built successfully on all other arches.
[16:59] <cjwatson> hjd: It happens now and again.  Not worth spending lots of time investigating unless it's pervasive, really.
[16:59] <cjwatson> hjd: Certainly not while LP staff are on vacation :)
[17:05] <hjd> cjwatson: Ok, sure. Just can't remember seeing it before and now I found three cases in a day.
[17:06] <cjwatson> hjd: You wouldn't notice it unless nobody has retried it already, so the chances of noticing it during a holiday are higher.
[19:42] <ari-tczew> is there something wrong with builders? I noticed some packages are waiting like never ending story
[19:51] <teward> ari-tczew: waiting to build, or waiting to migrate from proposed?
[19:51] <teward> ooo PPA builders are showing a ton as disabled...
[19:52] <teward> (but the actual repo builders seem OK according to the LP build farm page)
[19:54] <ari-tczew> teward: waiting to build
[19:54] <ari-tczew> exactly, packages on the PPA are stucked
[19:55] <ari-tczew> cjwatson: any news about that issue? ^^
[19:59] <cjwatson> ari-tczew: looks like they weretaken out by a brief swift outage earlier.  I've reset a handful to keep things moving, but I'm not at home right now and it's cumbersome from my phone.  will sort somemore later
[19:59] <ari-tczew> cjwatson: ok, thanks for your attention
[21:44] <ari-tczew> sbuild-build-depends-core-dummy : Depends: build-essential but it is not going to be installed
[21:44] <ari-tczew> on the xenial-proposed builders ???
[23:20] <cjwatson> ari-tczew: an example build would be most helpful
[23:24] <ari-tczew> cjwatson: https://launchpad.net/ubuntu/+source/capnproto/0.5.3-2ubuntu1
[23:25] <cjwatson> hm, I see a lot of recent failures but some successes oto
[23:25] <cjwatson> *too
[23:25] <ari-tczew> cjwatson: there is also another problem with 20-40 seconds builds, e.g. https://launchpad.net/~ari-tczew/+archive/ubuntu/testing/+build/8762787
[23:25] <ari-tczew> no buildlog, just ftbfs
[23:26] <cjwatson> oh, broken on everything that's not amd64
[23:26] <ari-tczew> cjwatson: build-essential problem on ppa, e.g.: https://launchpadlibrarian.net/231986500/buildlog_ubuntu-xenial-i386.xenomai_2.6.4%2Bdfsg-0.1~ppa01_BUILDING.txt.gz
[23:27] <cjwatson> ah, it's because the perl build crashed on amd64
[23:27] <cjwatson> I've retried https://launchpad.net/ubuntu/+source/perl/5.22.1-3/+build/8762672, should clear things up once it lands
[23:27] <cjwatson> in the absence of that build-essential is uninstallable
[23:30] <cjwatson> ari-tczew: builds without a buildlog are normally because the builder has crashed, but this case (and probably a lot of the other recent ones, actually) is because the swift instance that backs the LP librarian has been very flaky recently.  hard to work out what that might be when we only have skeleton sysadmin coverage
[23:30] <cjwatson> ari-tczew: it's fine to just retry those, I've done that for you in the case you gave
[23:31] <cjwatson> perl normally takes under an hour to build on amd64, so hopefully we'll be out of the woods in about an hour and a half
[23:32] <ari-tczew> cjwatson: thank you for the investigation, it's appreciated
[23:34] <cjwatson> I'll do some kind of partial mass give-back once perl is sorted
[23:35] <ari-tczew> not bad