Hi Gert,
On Thu, Nov 29, 2012 at 01:44:02PM +0100, Gert Wollny wrote:
> > debcheckout git://git.debian.org/debian-med/libvistaio.git
> --git-track '*'
> declared git repository at git://git.debian.org/debian-med/libvistaio.git
> git clone git://git.debian.org/debian-med/libvistaio.git libvistaio ...
> Cloning into 'libvistaio'...
> remote: Counting objects: 123, done.
> remote: Compressing objects: 100% (102/102), done.
> remote: Total 123 (delta 13), reused 118 (delta 13)
> Receiving objects: 100% (123/123), 178.90 KiB, done.
> Resolving deltas: 100% (13/13), done.
> Branch pristine-tar set up to track remote branch pristine-tar from origin.
> Branch upstream set up to track remote branch upstream from origin.
>
> git-buildpackage -us -uc
> dh clean
> dh_testdir
> dh_auto_clean
> dh_clean
> gbp:info: Orig tarball 'libvistaio_1.2.14.orig.tar.xz' not found at
> '../tarballs/'
> paranoia check failed on params from delta (-z -9) at
> /usr/bin/pristine-xz line 191.
> pristine-tar: command failed: pristine-xz --no-verbose --no-debug
> --no-keep genxz /tmp/pristine-tar.bffzZiUMta/wrapper
> /tmp/pristine-tar.Wepsnhp2KB/libvistaio_1.2.14.orig.tar.xz.tmp
> pristine-tar: failed to generate tarball
> gbp:error: /usr/bin/pristine-tar returned 255
> gbp:error: Couldn't checkout "libvistaio_1.2.14.orig.tar.xz"
>
> The machine where I created the repro is a VM running the latest SID
> (updated yesterday) the other machine is some Ubuntu 12.04.
>
> Which means git-buildpackage version 0.6.0~got20121124 (sid)
> versus 0.5.32 (Ubuntu 12.04). Could this be the problem?
I'm running testing and had
$ apt-cache policy git-buildpackage
git-buildpackage:
Installiert: 0.6.0~git20120601
Installationskandidat: 0.6.0~git20120601
Versionstabelle:
0.6.0~git20121124 0
50 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
*** 0.6.0~git20120601 0
501 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
100 /var/lib/dpkg/status
and also tried installing git-buildpackage from unstable right now
without any difference. I do not think that this problem is caused
by the different git-buildpackage versions - just lets hear what our
Git experts here on this list might say (several of them live in a
different time zone).
Kind regards
Andreas.
--
http://fam-tille.de