[00:11] I'm accustomed to having branches inside a project in bzr, say lp:~team/proj/kode [00:12] Suppose I have a project that has two unrelated git repositories. Can I upload Git branches lp:~team/proj/trunk and lp:~team/proj/proj-dependency ? [00:13] The second is hosted somewhere else altogether, upstream. [00:13] On LP, the second might also be a packaging branch or something. [00:14] Or the build-recipe skeleton. [00:14] qengho: lp:~OWNER/TARGET/+git/NAME is the full URL to a git repository. Similar to bzr, one can be given an lp:TARGET alias, but there is also the lp:~OWNER/TARGET alias. [00:15] Since most people only need one repo per project, they can just ignore that the long URLs exist at all. [00:15] But if you want multiple you can push them to a new full URL by tacking /+git/NAME on the end. [00:16] (but in git you can also just have multiple branches in the same repo, of course) [01:38] One can't make packaging recipes from git branches, can one? [01:39] I have a remote git branch that I want to automatically package. It has GPG-signed commits so I can't import to bzr branches. I can't seem to recipe-package if it's in git. [01:39] Le sigh. [01:40] qengho: They're currently in beta. [01:40] Ooo! beta team. [01:40] If you join the beta team you can use them. [01:40] Done! [01:40] There are some minor known bugs which I'm rolling out fixes for today, but the basics work fine. [01:41] wgrant: Upi [01:41] wgrant: You're pretty great. I'm glad you're with us. [01:41] Thank you. [01:41] Let me know if you run into any issues. === maclin1 is now known as maclin [11:17] ping any Launchpad admin please :) [11:19] bapoumba: Your account was probably caught in spam crossfire yesterday. #canonical-sysadmin can help you. [11:19] OK thanks wgrant :) [11:19] I thought so, next time I’ll leave the wiki spam alone ^^ [11:19] It's best not to remove spam yourself. [11:20] If it sticks around then let someone know, but if our automated scripts detect it after you've been playing with it, they might decide you look like the spammer yourself. [11:20] OK I’ll not remove any more, I just do not like people ruin community work .. [11:20] Yeah, it's not a good situation. [11:21] thanks again :) [14:34] hi, can anyone ban the user and remove the blueprint here https://blueprints.launchpad.net/mos/+spec/jhjg ? [19:16] on LP git import; is it possible for it to import all branches (from a project on github ie)... then write 3 recipes, one for each branch? [19:28] you can import to different bzr branches [19:29] or wait for git->git imports [19:29] or mirror to git manually [19:51] dobey, thank you....i'll just build one branch then.. [20:24] uhm... so a bit of a huge issue, i'm getting a lot of FTBFS on ppa uploads about ftpmaster.internal not being available [20:24] so it's causing a good portion of my PPA uploads jsut now to explode [20:24] also a chroot problem [20:25] ^ this, just came here to say it [20:25] seems to be transient [20:25] depends on the buildd, I think [20:25] cjwatson? [20:31] it's also hitting quite a lot of my PPA uploads for nginx 1.9.11 [20:31] so i'll have to rerun the builds that failed [20:31] (7 and counting) [20:31] yeah i just had some recipes fail because of it [20:34] teward, Logan, we're rebooting all our services due to the gcc bug announced [20:35] I'm raising this though in case it's not known [20:35] but there will be a bit of instability for a little while [20:35] thanks for the clarification! [20:41] beuno: thanks for the clarification. [21:17] teward: investigating, I don't think this is pure instability [21:19] cjwatson: yeah, it didn't appear to be [21:19] cjwatson: thanks [21:38] teward: should be fixed now, I'll give back failures [21:47] cjwatson: thanks; should I be OK to rerun the failed builds? [21:47] teward: I'll do it [21:48] thanks [21:48] prefer doing this kind of cleanup en masse [21:48] indeed :)