[07:32] <KombuchaKip> Now that cia.vc is dead, does anyone want to suggest a replacement for updating my channel topic's Bzr revno?
[10:53] <thopiekar> hey ;) is it possible that recipe builds are broken? Since last weekend I still get failed builds :(
[13:13] <dobey> thopiekar: recipe builds work fine for me.
[14:43] <thopiekar> dobey: well I noticed that I'm also affected as I checked the launchpad builder page :/
[14:43] <thopiekar> but from the buildlog I still didn't get whats going wrong :(
[14:43] <thopiekar> It just says that the builder can't decode a character..
[14:44] <thopiekar> see https://code.launchpad.net/~thopiekar/+recipe/kivy-daily
[14:48] <mattyw> it appear that tarmac has a timeout of 300 seconds for running verify_commands?? Is this right, if so is it configurable?
[14:50] <dobey> mattyw: huh?
[14:50] <geser> thopiekar: it looks like it isn't possible to browse the code for lp:kivy either. Did perhaps upstream add a weirdly named file on which now everything stumbles?
[14:51] <dobey> geser: surprising it looks like the imports aren't failing though
[14:52] <thopiekar> geser: well lp:kivy hosts code imported from github..
[14:52] <thopiekar> is there a chance to get the name of this file?
[14:52] <mattyw> dobey, I'm very green when it comes to tarmac, but for our project it's suddenly stopped landing stuff, If I modify the verify command in tarmac.conf to run a shorted running test it seems to pass. otherwise it throws an error starting with: Connection Timeout: disconnecting client after 300.0 seconds
[14:52] <dobey> mattyw: this channel is #launchpad
[14:53] <mattyw> dobey, I was hoping someone here might be able to help - no idea where else to go
[14:54] <dobey> mattyw: tarmac is a user of launchpad, not part of launchpad itself. this channel is for help about the launchpad.net instance itself. tarmac channel is #tarmac
[14:54] <geser> thopiekar: have you tried if you can fetch lp:kivy with bzr? perhaps it helps you to find the problem as the recipe seems to fail at this stage
[14:55] <dobey> geser: i just branched it, and bzr didn't crash
[14:56] <geser> ok, then I'm out of ideas how to diagnose this remotely and someone from the LP staff needs to look at it
[14:57] <dobey> well, it's possible that file was removed in the last import too
[14:58] <thopiekar> geser: I'm at the moment in the university where bzr does not work.. well, ssh can't verify the connection..
[14:58] <dobey> though the version string in the recipe itself looks problematic has too many dashes in it
[14:58] <thopiekar> could someone test it for me maybe?
[15:05] <dobey> thopiekar: the recipe seems to have built fine locally for me.
[15:10] <thopiekar> well, thats what I get..
[15:10] <thopiekar> asked someone else to copy the branch and also no errors
[15:10] <thopiekar> well got to leave now, will be back in an hour..
[15:19] <dobey> though maybe it doesn't break on bzr 2.6, but does on 2.4
[15:20] <dobey> seems the builders are still on hardy :-/
[15:23] <czajkowski> dobey: aye it doesnt make wgrant happy either
[16:33] <thopiekar> i'm back ;) any news about my problem? :/
[17:12] <dobey> the date/time selector dialog thingy for changing the release time when creating a release seems to not work any more. clicking on the little green check icon in the dialog doesn't do anything :(
[17:21] <dobey> hrmm, and armel builds in PPAs are always failing with "Unrecognized character \xFA at /home/buildd/.sbuildrc line 1." now
[17:23] <thopiekar> :(
[18:12] <Laney> Curious PPA problem.
[18:12] <Laney> Take a look at https://launchpadlibrarian.net/141030320/buildlog_ubuntu-saucy-amd64.evolution-rss_0.3.93-0ubuntu1_FAILEDTOBUILD.txt.gz and see the build failure
[18:13] <Laney> As far as I can tell reproducing locally the build-dep should be satisfied from within the PPA.
[18:13] <Laney> Looking through that buildlog you can see "W: GPG error: http://ppa.launchpad.net saucy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BFF79C57E3B7B49D" which is the key of this PPA.
[18:14] <Laney> Pretty sure that should be trusted there.
[18:15] <Laney> 'sup wit dat?
[18:22] <dobey> Laney: what ppa?
[18:23] <Laney> ppa:laney/evolution-3.8
[18:24] <Laney> dobey: ↑
[18:24] <Laney> back in a bit
[18:26] <dobey> Laney: is libevolution installable? (also why doesn't that have a sonum in the package name like every other library package?)
[19:25] <Laney> yeah turns out to be pebcak I think
[19:26] <Laney> the GPG warnings were a red herring
[19:30] <dobey> right
[19:30] <geser> I think the builders don't check the GPG key at all (they trust the internal archive) and the warning is in every log
[20:36] <psusi> there seems to be something fubar with the ppa builders... my build shows that it is still building ( started 3 hours ago ), yet looking at the build log shows all kinds of whacky output then says it was terminated: https://launchpad.net/~psusi/+archive/ppa/+build/4619632
[20:48] <dobey> psusi: the "funky output" looks like tests
[20:49] <dobey> i don't know what the typical build time of grub2 is though
[20:49] <psusi> dobey: it doesn't take hours and that doesn't seem to be any sort of output from its build process
[20:50] <dobey> psusi: have you done a local sbuild from the same .dsc?
[20:51] <psusi> dobey: doing one now
[20:52] <dobey> psusi: maybe something created a sub-shell and isn't returning control back to the parent script perhaps? if you think it's taking too long and/or stuck, you should probably cancel the build, and try to debug locally
[20:53] <psusi> it doesn't seem to be doing the build at all is the thing... output doing a build looks nothing like that at all
[20:57] <geser> the "official" grub2 build took less than 15 minutes
[20:58] <geser> and those tests are also in the build log in the "official" build but not that verbose (only the PASS entries are there)
[20:58] <dobey> psusi: that isn't the entire build log
[20:58] <dobey> psusi: it's only the last N lines of output
[20:58] <psusi> sounds about right... and I've just added one quilt patch swapping a strncmp line for a strstr instead.. and yea, I am now seeing something about the PASS: grub_xxxx lines but there was a whole crapload of compiling and such before then and none of that weird f1 $@ and such
[20:58] <psusi> ohhh
[20:59] <psusi> is there a way to get the full log?
[20:59] <dobey> i don't recall if cancelling the build will result in a build log being available, but it seems like you should probably cancel it
[21:03] <psusi> canceling threw out the build log...
[21:04] <dobey> retry the build?
[21:05] <psusi> did that already
[21:05] <psusi> this was the second time
[21:06] <dobey> anyway, i haven't noticed anything particularly broken with PPA builds.