[01:35] <smoser> hey.
[01:35] <smoser> https://launchpadlibrarian.net/337353000/buildlog.txt.gz
[01:35] <smoser> probably known ?
[01:36] <smoser> recipe build at https://code.launchpad.net/~smoser/+recipe/sm-xenial-daily produced that,
[01:36] <smoser> fails early with
[01:36] <smoser>    Could not connect to ftpmaster.internal:80 (91.189.89.99). - connect (111: Connection refused)
[01:40] <wgrant__> smoser: Sorry about that, we'd intended to pause builds during this quick maintenance, but that didn't quite work apparently.
[01:41] <wgrant> It'll be back in a few minutes, and all builds are probably paused now.
[01:41] <wgrant> s/probably/properly/
[02:46] <KeithW> Hi folks -- is Launchpad experiencing an unannounced outage? We're not seeing our uploads appear in PPAs (even after several hours).
[02:47] <wgrant> KeithW: We ran into some trouble with some maintenance this morning which is delaying processing of PPA uploads. Hopefully will be back within 15 minutes, and the backlog will be processed quickly.
[02:48] <KeithW> Thanks!
[03:34] <tsimonq2> Seems to be working again
[03:34] <tsimonq2> Thanks wgrant et al!
[13:51] <smoser> cjwatson, i saw you talking last week about 'make -f debian/rules clean'
[13:51] <smoser> generating files / being used for making templates
[13:52] <smoser> in cloud-init we have upstream branch with no packaging in debian/ and ubuntu/<release> branch with packaging that differs by release.
[13:53] <smoser> when i cherry pick a upstream patch in ubuntu/<release> and put it in debian/patches/series then my recipe for building trunk fails (as the cherry picked patch wont apply)
[13:53] <smoser>  https://code.launchpad.net/~cloud-init-dev/+recipe/cloud-init-daily-xenial
[13:53] <cjwatson> I don't want to discuss what should be done; I was merely observing what in practice sometimes is done.
[13:54] <smoser> so i was hoping that i could just do something simple and some way make my trunk recipe take a different path (commenting out cpick-* from debian/patches/series)
[13:54] <smoser> https://code.launchpad.net/~smoser/+recipe/sm-xenial-daily
[13:54] <smoser> (you're welcome to say "I'm sorry i dont have time")
[13:54] <cjwatson> I'm not sure how that's related to my clean observation.
[13:54] <smoser> well, i thought you were saying that 'debian/rules clean' woudl alwasy be called before building
[13:55] <cjwatson> Nope.
[13:55] <smoser> oh. hm. ok then.
[13:55] <smoser> how do people do that sort of thing ?
[13:57] <cjwatson> I think you just have to have different packaging branches depending on what you're applying them to, at least sometimes.
[13:57] <cjwatson> That's certainly what I'd do.
[13:58] <smoser> yeah. i was just trying to avoid the maintenance of N more branches where all they did was remove 'cpick-*' lines from debian/patches/series
[15:04] <kwmonroe> does anyone have lp builders building snaps from svn?  my builds are having trouble doing the svn checkout from lp builders:  http://paste.ubuntu.com/25565855/
[15:05] <nacc> kwmonroe: ew.
[15:05] <kwmonroe> heh
[15:05] <kwmonroe> queue the "boo svn"
[15:05] <nacc> kwmonroe: although that reads more like possibly a proxy issue?
[15:06] <kwmonroe> true dat nacc -- fwiw, the actual snap branch is a lp bzr -- it's just that the snap does an svn checkout for one of its parts.
[15:06] <nacc> kwmonroe: use https://github.com/apache/pig ?
[15:06] <nacc> kwmonroe: (which appears to be a mirror apache's git pig repo)
[15:07] <nacc> kwmonroe: so you could also use git://git.apache.org/pig.git
[15:07] <kwmonroe> yup nacc - using a git mirror ought to work.. just wondering if anyone was able to use svn on the builders (like maybe with a svn option to add --proxy=foo)
[15:09] <nacc> kwmonroe: good q, no idea myself, sorry
[15:17] <kwmonroe> np nacc - thx for the git mirror suggestion!  that'll get me where i need to go.
[15:19] <nacc> kwmonroe: np, that's been my general snap workarounnd :)
[15:19] <kwmonroe> heh
[16:06] <cjwatson> kwmonroe: https://bugs.launchpad.net/launchpad-buildd/+bug/1668358
[16:06] <cjwatson> need to work out some plausible proxy arrangement for that, but yeah, some kind of mirror would likely help