Package: git-buildpackage Version: 0.4.46 Severity: normal git-buildpackage seems to use an existing .orig.tar.gz file rather than checking one out with pristine-tar. In my case, I'm the upstream maintainer as well, so I happened to have an older tarball around. I had used "pristine-tar commit" with the correct, newer tarball, but gbp didn't use that one, and I accidentally uploaded a package with the wrong .orig.tar.gz as a result. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (400, 'unstable'), (1, 'experimental') Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-buildpackage depends on: ii devscripts 2.10.46 scripts to make the life of a Debi ii git-core 1:1.6.1.3-1 fast, scalable, distributed revisi ii python 2.5.4-2 An interactive high-level object-o ii python-dateutil 1.4.1-3 powerful extensions to the standar ii python-support 0.8.7 automated rebuilding support for P git-buildpackage recommends no packages. Versions of packages git-buildpackage suggests: pn git-load-dirs <none> (no description available) ii pristine-tar 0.21 regenerate pristine tarballs -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
