On 13/01/17 19:02, Guido Günther wrote: > On Fri, Jan 13, 2017 at 06:54:52PM +0100, Guido Günther wrote: > > Package: pristine-tar > > Version: 1.37 > > Severity: normal > > > > Hi, > > Importing xz-utils fails with: > > > > $ gbp import-dsc --verbose apt://xz-utils/sid > > gbp:info: Downloading 'xz-utils/sid' using 'apt-get'... > > gbp:info: No git repository found, creating one. > > gbp:info: Tag upstream/5.2.2 not found, importing Upstream tarball > > gbp:debug: /usr/bin/pristine-tar [] ['commit', > > '/tmp/tmpePy8LE/xz-utils_5.2.2.orig.tar.xz', > > '78070151ccd87648d5f2c3b6a8c0ad4bf9685f03'] > > gbp:error: Couldn't commit to 'pristine-tar' with upstream > > '78070151ccd87648d5f2c3b6a8c0ad4bf9685f03': pristine-xz failed to reproduce > > build of /tmp/tmpePy8LE/xz-utils_5.2.2.orig.tar.xz > > (Please file a bug report.) > > pristine-tar: command failed: pristine-xz --no-verbose --no-debug --no-keep > > gendelta /tmp/tmpePy8LE/xz-utils_5.2.2.orig.tar.xz > > /tmp/pristine-tar.NLMdqskICv/wrapper > > pristine-tar: failed to generate delta > > Importing yad seems to have the same problem. >
Thanks for this report. Things don't look good. I was not able to reproduce any xz-utils orig tarballs we have e.g. in debian snapshot (or here http://tukaani.org/xz/old.html). The default options to xz seem to be "-6" or "-6e", but this produces a different output. This will need more investigation... It maybe that the debian's xz is producing something non-standard, I don't know yet. That said, we must consider a way to force importing a tarball as-it-is, to work around hopeless cases. Tomasz
signature.asc
Description: PGP signature
