Bug#839748: ITP: golang-gopkg-flosch-pongo2.v3 -- Django-syntax like template-engine for Go
On 21/11/2017 12:48, Clément Hermann wrote:
> On Sun, 19 Nov 2017 18:45:21 +0100 <clement.hermann@virtua.ch> wrote:
>> Hi !
>>
>> On Tue, 4 Oct 2016 15:30:00 +0100 Jonathan Dowland <jmtd@debian.org>
> wrote:
>
>>> This is a dependency for LXD and is being packaged via the pkg-go team.
>>
>> It's actually the last one beside golang-gopkg-lxc-go-lxc.v2-dev.
>>
>> Any ETA ? I saw the repository under pkg-go, is there any way I can help ?
>
> 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 ?
Cheers,
nodens
[0] https://pkg-go.alioth.debian.org/workflow-changes.html
[1] https://bugs.debian.org/811565
Reply to: