Control: tag -1 + confirmed On Sat, Jun 06, 2020 at 05:11:58PM +0200, Andrea Bolognani wrote: > Package: pristine-tar > Version: 1.47 > Severity: normal [...] > Downgrading pristine-tar to 1.46 from buster makes it possible to run > gbp import-orig successfully, at which point both 1.46 and 1.47 are > able to regenerate the tarball from the git branch. > > The Debian repository for libvirt is > > https://salsa.debian.org/libvirt-team/libvirt/ > > and the commits the various branches were pointing to when I > encountered the issue are > > pristine-tar 9964e57257 pristine-tar data for > libvirt_6.2.0.orig.tar.xz > upstream/latest 1b6982f1b5 New upstream version 6.2.0 > debian/experimental 51d88f1e6f Document changes and release 6.2.0-1 > > The tarball I was trying to import is > > https://libvirt.org/sources/libvirt-6.4.0.tar.xz > > but I tried libvirt 6.3.0 as well and got the same results. A couple > of months ago, when I imported libvirt 6.2.0, and indeed all the many > times I used gbp import-orig before now, everything worked smoothly. [...]
I bisected this and the commit that introduced this bug was
4ff745f2d3e905d88718b5e57bc6b4baf479f55b ("pristine-xz: Detect pixz
compression").
Kevin, can you please take a look?
signature.asc
Description: PGP signature
