[09:37] <HeOS> cjwatson and wgrant, thank you, guys, for your works!
[10:07] <cjwatson> HeOS: you're welcome
[10:08]  * cjwatson confirms that that fuel milestone page works now
[13:45] <jgdx> cjwatson, hey, I don't know if I discussed the go get failure with you, but I filed bug 1521628 in any case.
[13:46] <jgdx> woops, I am wrong though, infra does not use the make script.
[14:36] <cjwatson> jgdx: and yet
[14:36] <cjwatson> $ curl -s https://launchpad.net/godeps | grep -A1 go-import
[14:36] <cjwatson>     <meta name="go-import"
[14:36] <cjwatson>           content="launchpad.net/godeps bzr https://launchpad.net/~godeps-maintainers/godeps/trunk" />
[14:38] <cjwatson> jgdx: do you have a version of go new enough to have the changes in https://github.com/golang/go/issues/11436 ?
[14:40] <jgdx> cjwatson, I'll check. It was xenial, so > 1.5
[14:45] <cjwatson> 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] <cjwatson> 0.080  hpss call:   'hello',
[14:45] <cjwatson> 0.080               (to https://launchpad.net/~godeps-maintainers/godeps/trunk/)
[14:45] <cjwatson> 2.138  hpss call:   'hello',
[14:45] <cjwatson> 2.139               (to http://bazaar.launchpad.net/~godeps-maintainers/godeps/trunk/)
[14:46] <cjwatson> ... which I'm not going to dig into on my afternoon off :-)
[14:48] <jgdx> cjwatson, yeah, it's currently a risk, but not a very big one. So no hurry. :)
[15:10] <jgdx> cjwatson, why is that hpss removing the s?
[15:11] <jgdx> is it an anti-s-ite?
[15:22] <cjwatson> 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] <cjwatson> I haven't traced it through in full detail
[15:23] <jgdx> ookok
[21:46] <wgreenberg> is there any concept of "forking" a project in launchpad?
[21:46] <wgreenberg> 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] <xnox> ppa is per team/person, and not connected to projects at all.
[22:01] <xnox> and so are the recipes if you want to use that.
[22:01] <xnox> just build it for your ppa and that's it...
[22:01] <xnox> you can push any bzr branches you want to e.g. lp:~/foo/my-branch, or use lp:foo in your recipes.
[22:03] <wgrant> Right, in LP you don't "fork" a project. You just push your own branch into the existing project.
[22:03] <wgrant> So you can get an overview of what everyone's doing, rather than having to click around through a hundred separate projects.
[22:21] <wgreenberg> 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] <cjwatson> That should be fine, yes
[22:24] <cjwatson> (And as xnox implies, you don't actually have to use recipes; but you may find it easier)
[22:25] <wgreenberg> 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] <teward> probably
[22:26] <wgreenberg> anywho looks like it's working. thanks!