[00:00] <kyrofa> wgrant, ah okay, the granularity is what I was wondering about. Sometimes I push and don't notice a build starting up
[00:02] <kyrofa> But you're right, now that I've waited for about 10 minutes I see builds starting. Very good
[00:03] <wgrant> kyrofa: The 20 minute thing is just a cronjob schedule, but the 60 minute thing is to avoid swamping the build farm too much.
[00:03] <kyrofa> Yeah that makes sense
[00:04] <kyrofa> wgrant, it's allowed me to setup a little travis-powered deployment. When I push to a branch, travis pushes to an LP branch, and builds start and get automatically published. Pretty handy!
[00:06] <wgrant> kyrofa: You can also trigger a build directly through the API pretty easily, if need be.
[00:06] <kyrofa> wgrant, yeah, that might be rev 2, since then I figure I could poll the process and wait for it to complete, failing if the build fails, etc.
[00:06] <kyrofa> wgrant, but I needed the quick and dirty 5-minute hack
[00:06] <kyrofa> You know how it goes
[00:07] <wgrant> Yup
[08:41] <ulm> https://answers.launchpad.net/launchpad/+question/355999
[08:41] <ulm> ^^ does this take long because there is a principal problem with the request?
[08:42] <ulm> or because of a shortage of manpower?
[10:11] <ricotz> cjwatson, hi, could you retry those builds? https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/10689734 and https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/10689775
[10:16] <cjwatson> ricotz: done
[10:18] <ricotz> cjwatson, thanks!
[10:20] <cjwatson> ulm: Sorry for the delay.  Passed to sysadmin for action now; one of us will update the ticket when done.
[13:31] <ulm> cjwatson: thanks
[15:17] <chrisccoulson> any idea why all of my builds are failing like this? https://launchpad.net/~oxide-builds/+archive/ubuntu/oxide-next-for-stable-phone-overlay/+build/10693743
[15:17] <chrisccoulson> No logs
[15:19] <cjwatson> There was a network event recently, could be that
[15:19] <chrisccoulson> cjwatson, thanks
[15:20] <cjwatson> Let me bulk-retry stuff
[15:21] <cjwatson> should all be retrying now
[15:22] <chrisccoulson> excellent, thanks
[19:32] <caraka> Greetings! My bzr imports are failing because one of our devs started signing his PRs over on github. Is there an easy workaround, or am I better to switch to git on launchpad?
[19:37] <caraka> We have no submodules, just a stray gpgsig
[19:46] <cjwatson> I'm afraid there's no workaround
[19:47] <cjwatson> Once I'm done with my current urgent project the tentative plan is to do git-to-git imports next; in the meantime you can do periodic git pull/push by hand to create an LP git mirror
[19:47] <cjwatson> (which isn't great, I know, but shouldn't be utterly horrible and is closer to what we'll end up with)
[19:48] <caraka> thanks cj, that's what my reading had suggested, I wanted to check that I hadn't missed something. Cheers
[19:50] <cjwatson> It's a bit of a FAQ at the moment, but that's useful because it means there's clear pressure to get it done
[19:51] <caraka> No doublt I'm just one more squeak of the wheel.  :P
[19:51] <caraka> It's all good becuase the recipes are sorted already.