Bug#739104: debcheckout: should create a local tracking branch for pristine-tar

Andreas Beckmann anbe at debian.org
Sat Feb 15 20:55:42 UTC 2014


Package: devscripts
Version: 2.14.1
Severity: normal

Hi,

if debcheckout clones a git repository, if should create a local
tracking branch for pristine-tar (if that exists in the remote
repository). Otherwise git-buildpackage --git-pristine-tar fails because
it cannot find the pristine-tar branch. It tries to access the remote,
but somehow this fails. Also a local pristine-tar branch is needed to
import a new upstream release.

$ debcheckout qgis
[...]
$ cd qgis
$ git-buildpackage --git-export-dir=../build-area --git-pristine-tar [...]
[...]
gbp:warning: Pristine-tar branch "pristine-tar" not found
fatal: Path 'qgis_2.0.1.orig.tar.gz.delta' does not exist in 'refs/remotes/origin/pristine-tar'
pristine-tar: git show refs/remotes/origin/pristine-tar:qgis_2.0.1.orig.tar.gz.delta failed
gbp:error: Couldn't checkout "qgis_2.0.1.orig.tar.gz": /usr/bin/pristine-tar returned 128

There may be an additional bug in pristine-tar that makes it only look
for .tar.gz in refs/remotes/origin/pristine-tar while we have an
..tar.bz2 in this case.
After checking out pristine-tar locally once, gbp succeeds:

[...]
pristine-tar: successfully generated /tmp/rebuild/build-ares/qgis_2.0.1.orig.tar.bz2
[...]


Andreas



More information about the devscripts-devel mailing list