Your message dated Sun, 17 Mar 2013 11:56:13 +0100
with message-id <[email protected]>
and subject line Re: Bug#703203: Has issues when upstream sources are in bzip2
format
has caused the Debian Bug report #703203,
regarding Has issues when upstream sources are in bzip2 format
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
703203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703203
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-buildpackage
Version: 0.6.0~git20130314
The following :
$ git clone git://git.debian.org/git/debian-science/packages/pynac.git
$ cd pynac
$ git-buildpackage -us -uc
fails with:
gbp:error: Couldn't checkout "pynac_0.2.6.orig.tar.gz":
/usr/bin/pristine-tar returned 128
and indeed:
$ pristine-tar checkout /home/jpuydt/Debian/build/pynac_0.2.6.orig.tar.gz
fatal: Path 'pynac_0.2.6.orig.tar.gz.delta' does not exist in
'refs/remotes/origin/pristine-tar'
pristine-tar: git show
refs/remotes/origin/pristine-tar:pynac_0.2.6.orig.tar.gz.delta failed
but:
$ pristine-tar checkout /home/jpuydt/Debian/build/pynac_0.2.6.orig.tar.bz2
pristine-tar: successfully generated
/home/jpuydt/Debian/build/pynac_0.2.6.orig.tar.bz2
So git-buildpackage didn't give the right directions to pristine-tar...
Hope it helps,
Snark on #debian-science
--- End Message ---
--- Begin Message ---
Hi,
On Sat, Mar 16, 2013 at 10:30:50PM +0100, Julien Puydt wrote:
> Package: git-buildpackage
> Version: 0.6.0~git20130314
>
> The following :
> $ git clone git://git.debian.org/git/debian-science/packages/pynac.git
> $ cd pynac
> $ git-buildpackage -us -uc
>
> fails with:
> gbp:error: Couldn't checkout "pynac_0.2.6.orig.tar.gz":
> /usr/bin/pristine-tar returned 128
>
> and indeed:
> $ pristine-tar checkout /home/jpuydt/Debian/build/pynac_0.2.6.orig.tar.gz
> fatal: Path 'pynac_0.2.6.orig.tar.gz.delta' does not exist in
> 'refs/remotes/origin/pristine-tar'
> pristine-tar: git show
> refs/remotes/origin/pristine-tar:pynac_0.2.6.orig.tar.gz.delta
> failed
>
> but:
> $ pristine-tar checkout /home/jpuydt/Debian/build/pynac_0.2.6.orig.tar.bz2
> pristine-tar: successfully generated
> /home/jpuydt/Debian/build/pynac_0.2.6.orig.tar.bz2
>
> So git-buildpackage didn't give the right directions to pristine-tar...
It does so if it can. If you use gbp-clone it will setup the correct
branch tracking, spot the pristine-tar branch and determine the source
tarball is bz2. If you don't use gbp-clone you have to setup the branch
tracking by hand. As soon as it can find the pristine-tar branch it will
work.
Cheers,
-- Guido
--- End Message ---
