Package: tar Version: 1.30+dfsg-1 Severity: grave Justification: causes non-serious data loss
Hi, After tar 1.30 arrived in unstabled, pristine-tar can no longer reproduce tarballs that it previously could. For example I just hit this with bundler: $ debcheckout -a bundler declared git repository at g...@salsa.debian.org:ruby-team/bundler.git git clone https://salsa.debian.org/ruby-team/bundler.git bundler ... Cloning into 'bundler'... remote: Counting objects: 3981, done. remote: Compressing objects: 100% (1289/1289), done. remote: Total 3981 (delta 2570), reused 3950 (delta 2551) Receiving objects: 100% (3981/3981), 3.55 MiB | 24.00 KiB/s, done. Resolving deltas: 100% (2570/2570), done. git remote set-url --push origin g...@salsa.debian.org:ruby-team/bundler.git ... $ cd bundler/ $ pristine-tar checkout /tmp/bundler_1.16.1.orig.tar.gz xdelta3: target window checksum mismatch: XD3_INVALID_INPUT xdelta3: normally this indicates that the source file is incorrect xdelta3: please verify the source file with sha1sum or equivalent xdelta3: target window checksum mismatch: XD3_INVALID_INPUT xdelta3: normally this indicates that the source file is incorrect xdelta3: please verify the source file with sha1sum or equivalent xdelta3: target window checksum mismatch: XD3_INVALID_INPUT xdelta3: normally this indicates that the source file is incorrect xdelta3: please verify the source file with sha1sum or equivalent xdelta3: target window checksum mismatch: XD3_INVALID_INPUT xdelta3: normally this indicates that the source file is incorrect xdelta3: please verify the source file with sha1sum or equivalent pristine-tar: Failed to reproduce original tarball. Please file a bug report. pristine-tar: failed to generate tarball See also #897249 and #897421 for similar pristine-tar user reports. Downgrading tar to 1.29b-2 makes it work again. I realize that pristine-tar is not sustainable in the long run, but for better or worse it became a relevant part of Debian development infrastructure. I'm filing this bug to avoid this situation hitting testing, while we figure some way out of this. Bdale, do you have any initial thoughts on this? -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tar depends on: ii libacl1 2.2.52-3+b1 ii libc6 2.27-3 ii libselinux1 2.7-2+b2 tar recommends no packages. Versions of packages tar suggests: ii bzip2 1.0.6-8.1 ii ncompress 4.2.4.4-20 pn tar-doc <none> pn tar-scripts <none> ii xz-utils 5.2.2-1.3 -- no debconf information
signature.asc
Description: PGP signature
