Package: git-buildpackage
Version: 0.4.64
Severity: normal
Hello,
It seems that git-buildpackage does not handle yet .tar.bz2 orig
tarballs in the tarballs directory, see:
20:14 ~/packages/fig2ps gitbs --git-no-create-orig
dh_testdir
dh_testroot
rm -f build-stamp
dh_clean
Looking for orig tarball 'fig2ps_1.5.orig.tar.gz' at
'/home/vincent/packages/tarballs'
Orig tarball 'fig2ps_1.5.orig.tar.gz' not found at
'/home/vincent/packages/tarballs'
Exporting 'HEAD' to '/home/vincent/packages/build-area/fig2ps-tmp'
Moving '/home/vincent/packages/build-area/fig2ps-tmp' to
'/home/vincent/packages/build-area/fig2ps-1.5'
This package has a Debian revision number but there does not seem to be
an appropriate original tar file or .orig directory in the parent directory;
(expected one of fig2ps_1.5.orig.tar.gz, fig2ps_1.5.orig.tar.bz2,
fig2ps_1.5.orig.tar.lzma or fig2ps-1.5.orig)
continue anyway? (y/n) n
In principle, git-buildpackage should simply blindly copy all
fig2ps_1.5.orig* files to target build directory and not bother. I'll
try to see if I can provide a patch for that.
Cheers,
Vincent
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages git-buildpackage depends on:
ii devscripts 2.10.61 scripts to make the life of a Debi
ii git-core 1:1.6.6.1-1 fast, scalable, distributed revisi
ii python 2.5.4-9 An interactive high-level object-o
ii python-dateutil 1.4.1-3 powerful extensions to the standar
ii python-support 1.0.6 automated rebuilding support for P
Versions of packages git-buildpackage recommends:
ii pristine-tar 1.00 regenerate pristine tarballs
Versions of packages git-buildpackage suggests:
pn git-load-dirs <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
