[01:35] hey. [01:35] https://launchpadlibrarian.net/337353000/buildlog.txt.gz [01:35] probably known ? [01:36] recipe build at https://code.launchpad.net/~smoser/+recipe/sm-xenial-daily produced that, [01:36] fails early with [01:36] Could not connect to ftpmaster.internal:80 (91.189.89.99). - connect (111: Connection refused) [01:40] smoser: Sorry about that, we'd intended to pause builds during this quick maintenance, but that didn't quite work apparently. === wgrant__ is now known as wgrant [01:41] It'll be back in a few minutes, and all builds are probably paused now. [01:41] s/probably/properly/ [02:46] Hi folks -- is Launchpad experiencing an unannounced outage? We're not seeing our uploads appear in PPAs (even after several hours). === G_ is now known as G [02:47] 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] Thanks! [03:34] Seems to be working again [03:34] Thanks wgrant et al! === hrybacki|ptg is now known as hrybacki [13:51] cjwatson, i saw you talking last week about 'make -f debian/rules clean' [13:51] generating files / being used for making templates [13:52] in cloud-init we have upstream branch with no packaging in debian/ and ubuntu/ branch with packaging that differs by release. [13:53] when i cherry pick a upstream patch in ubuntu/ and put it in debian/patches/series then my recipe for building trunk fails (as the cherry picked patch wont apply) [13:53] https://code.launchpad.net/~cloud-init-dev/+recipe/cloud-init-daily-xenial [13:53] I don't want to discuss what should be done; I was merely observing what in practice sometimes is done. [13:54] 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] https://code.launchpad.net/~smoser/+recipe/sm-xenial-daily [13:54] (you're welcome to say "I'm sorry i dont have time") [13:54] I'm not sure how that's related to my clean observation. [13:54] well, i thought you were saying that 'debian/rules clean' woudl alwasy be called before building [13:55] Nope. [13:55] oh. hm. ok then. [13:55] how do people do that sort of thing ? === chihchun_afk is now known as chihchun [13:57] I think you just have to have different packaging branches depending on what you're applying them to, at least sometimes. [13:57] That's certainly what I'd do. [13:58] 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 === JanC_ is now known as JanC [15:04] 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] kwmonroe: ew. [15:05] heh [15:05] queue the "boo svn" [15:05] kwmonroe: although that reads more like possibly a proxy issue? [15:06] 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] kwmonroe: use https://github.com/apache/pig ? [15:06] kwmonroe: (which appears to be a mirror apache's git pig repo) [15:07] kwmonroe: so you could also use git://git.apache.org/pig.git [15:07] 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] kwmonroe: good q, no idea myself, sorry [15:17] np nacc - thx for the git mirror suggestion! that'll get me where i need to go. [15:19] kwmonroe: np, that's been my general snap workarounnd :) [15:19] heh [16:06] kwmonroe: https://bugs.launchpad.net/launchpad-buildd/+bug/1668358 [16:06] Ubuntu bug 1668358 in launchpad-buildd "Snap Builds using SVN Unable to Access Internet" [Undecided,Confirmed] [16:06] need to work out some plausible proxy arrangement for that, but yeah, some kind of mirror would likely help