control: tags -1 +wontfix

Hi,
On Fri, Sep 07, 2018 at 03:05:35PM +0200, Raphaël Hertzog wrote:
> Package: git-buildpackage
> Version: 0.9.10
> Severity: normal
> User: [email protected]
> Usertags: origin-kali
> 
> I'm often sponsoring packages and I usually use "git clone" (and not "gbp
> clone") so that I only have the "master" or "debian/master" branch in my
> local repository, however the "upstream" and "pristine-tar" branches are
> in the remote repository ("origin").
> 
> pristine-tar copes just fine with this and fallsback to use the data from
> origin/pristine-tar but if the compression method is not the usual gzip, gbp
> buildpackage will fail. I have to tell it "--git-compresionn=xz" to make
> the call succeed. It would be nice if the code that looks up the compression
> method in the pristine-tar branch was smart enough to also fall back
> to looking into origin/pristine-tar.

What about debian/pristine-tar, salsa/pristine-tar, foo/pristine-tar and other
variants? What if these have different versions already to pick from? If
somebody comes up with a good heuristic and sane defaults this might be
an option but I consider using gbp clone way safer.

Cheers,
 -- Guido

Reply via email to