Re: Git repository of htslib is lacking pristine-tar

[Ghislain Vaillant <ghisvail@gmail.com>]

On 28/07/15 11:19, Andreas Tille wrote:
> Hi Charles,
>
> $ gbp clone ssh://git.debian.org/git/debian-med/htslib.git
> $ cd htslib
> $ gbp buildpackage
> gbp:info: Orig tarball 'htslib_1.2.1.orig.tar.gz' not found at '../tarballs/'
> gbp:error: Pristine-tar couldn't checkout "htslib_1.2.1.orig.tar.gz": fatal: Path 'htslib_1.2.1.orig.tar.gz.delta' does not exist in 'refs/heads/pristine-tar'
> pristine-tar: git show refs/heads/pristine-tar:htslib_1.2.1.orig.tar.gz.delta failed
>
> I tried:
>
> $ pristine-tar commit ../htslib_1.2.1.orig.tar.gz v1.2.1
> pristine-tar: failed to find ref using: git show-ref v1.2.1
>
> which I took from bedtools debian/README.source.  It seems that the 'v'
> in front of the version number in the end needs to be left our here.  I
> commited an according README.source.
>
> I admit I'm not yet convinced that the chance to enable upstream pull
> requests are worth the drawback that other team members have trouble
> to follow an undocumented workflow.
>
> Kind regards
>
>         Andreas.


You can normally do:

gbp buildpackage --git-upstream-tag=v1.2.1 \
	--git-debian-branch=debian/unstable \
	--git-no-pristine-tar \
	--git-pristine-tar-commit

The last 2 options explicitly tell gbp that a pristine-tar commit does 
not exist yet for this tag and that is should generate a tarball and 
commit one.

In case the tarball for the current tag already exist in pristine-tar, 
these options are simply ignored.

This is a beginning of a documented workflow following DEP-14:
http://blog.mycre.ws/articles/git-packaging-workflow-for-py-lmdb/

Ghis