=== maclin1 is now known as maclin === caraka_ is now known as caraka [09:37] cjwatson and wgrant, thank you, guys, for your works! [10:07] HeOS: you're welcome [10:08] * cjwatson confirms that that fuel milestone page works now [13:45] cjwatson, hey, I don't know if I discussed the go get failure with you, but I filed bug 1521628 in any case. [13:45] bug 1521628 in Launchpad itself "go get fails when trying to download something from launchpad.net" [Undecided,New] https://launchpad.net/bugs/1521628 [13:46] woops, I am wrong though, infra does not use the make script. [14:36] jgdx: and yet [14:36] $ curl -s https://launchpad.net/godeps | grep -A1 go-import [14:36] content="launchpad.net/godeps bzr https://launchpad.net/~godeps-maintainers/godeps/trunk" /> [14:38] jgdx: do you have a version of go new enough to have the changes in https://github.com/golang/go/issues/11436 ? [14:40] cjwatson, I'll check. It was xenial, so > 1.5 === maclin1 is now known as maclin [14:45] jgdx: ah, right, I think the problem is that "bzr branch https://launchpad.net/~godeps-maintainers/godeps/trunk" gets turned into http://bazaar.launchpad.net/... [14:45] 0.080 hpss call: 'hello', [14:45] 0.080 (to https://launchpad.net/~godeps-maintainers/godeps/trunk/) [14:45] 2.138 hpss call: 'hello', [14:45] 2.139 (to http://bazaar.launchpad.net/~godeps-maintainers/godeps/trunk/) [14:46] ... which I'm not going to dig into on my afternoon off :-) [14:48] cjwatson, yeah, it's currently a risk, but not a very big one. So no hurry. :) [15:10] cjwatson, why is that hpss removing the s? [15:11] is it an anti-s-ite? [15:22] jgdx: I think it's more likely that it's asking the LP webapp for the URL, and that the relevant bit of webapp code was written a long time ago and returns an http URL [15:22] I haven't traced it through in full detail [15:23] ookok [21:46] is there any concept of "forking" a project in launchpad? [21:46] I've got a development branch of a project that exists, and I'd like to build it as a package in my ppa [22:01] ppa is per team/person, and not connected to projects at all. [22:01] and so are the recipes if you want to use that. [22:01] just build it for your ppa and that's it... [22:01] you can push any bzr branches you want to e.g. lp:~/foo/my-branch, or use lp:foo in your recipes. [22:03] Right, in LP you don't "fork" a project. You just push your own branch into the existing project. [22:03] So you can get an overview of what everyone's doing, rather than having to click around through a hundred separate projects. [22:21] ok, makes sense. So if I wanted my PPA to build packages with my unmerged customizations of some project, I'd just push a bzr branch of the main project and use it in the recipe? [22:23] That should be fine, yes [22:24] (And as xnox implies, you don't actually have to use recipes; but you may find it easier) [22:25] gotcha. in our case, we store debian files in a separate branch for *reasons*, so I think we need a recipe to pull in both branches [22:26] probably [22:26] anywho looks like it's working. thanks!