[pkg-go] Bug#839748: ITP: golang-gopkg-flosch-pongo2.v3 -- Django-syntax like template-engine for Go

Clément Hermann nodens at nodens.org
Sun Dec 3 22:39:54 UTC 2017

On 03/12/2017 17:37, Clément Hermann wrote:
> On 21/11/2017 12:48, Clément Hermann wrote:
>> When I wanted to build the package, I realized it's not using
>> git-buildpackage, as the other Go packages do.
>> Is it intentional, or do you plan to use graft or something like that to
>> rewrite history and have the proper branches ? I had a look at it, and
>> I'm not really comfortable enough with git
>> to do it without messing things up, so I wonder what the options are.
> So, looking at it more closely, I found out that the initial commit is
> actually the upstream source, which means we can just branch from it for
> the upstream branch.
> While waiting for the workflow changes following DebConf17 BoF [0], I
> guess the best is to be as standard as possible, even if it's a bit
> painful in this case, since uscan doesn't allow arbitrary snapshots yet
> [1] and upstream stopped doing releases ages ago. So I guess manual
> snapshot and pristine-tar is the way to go.
> Of course if you have upstream and pristine-tar branch locally it would
> be great to push them ;)
> I asked to join the pkg-go project on alioth, because I have a couple
> commits ready locally for trivial nitpick, but I guess this package is
> not far from upload, and I'm preparing an ITP for
> golang-gopkg-lxc-go-lxc.v2-dev.
> Would anyone mind rewieving / uploading ? Jonathan, are you still
> working on this, or should I take over the ITP ?

I just uploaded my fixes and pushed the missing branches/tags.

All it needs now is rewiewing, signed tag and upload, hopefully.



More information about the Pkg-go-maintainers mailing list