In this repository:

https://salsa.debian.org/python-team/modules/python-django.git

$ pristine-tar checkout python-django_1.11.20.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
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


Andreas

In that case it's probably a dependency problem, my build machine is a
mixed stable..experimental system :-)
I'll investigate ...

Andreas

Control: tag -1 + moreinfo

Interesting, it just worked for me on a fresh git clone:

python-django (debian/sid) $ pristine-tar checkout python-django_1.11.20.orig.tar.gz
pristine-tar: successfully generated python-django_1.11.20.orig.tar.gz

Do you have anything locally that is not also in the remote repository?

Control: tag -1 - moreinfo
https://salsa.debian.org/python-team/modules/python-django.git

I can reproduce now with python-azure. Tarball committed on my buster system with git and pristine-tar from buster-backports:

$ apt-cache policy pristine-tar git xdelta xdelta3
pristine-tar:
  Installed: 1.47~bpo10+1
  Candidate: 1.47~bpo10+1
  Version table:
 *** 1.47~bpo10+1 100
        100 https://deb.debian.org/debian buster-backports/main amd64 Packages
        100 /var/lib/dpkg/status
     1.46 500
        500 https://deb.debian.org/debian buster/main amd64 Packages
git:
  Installed: 1:2.27.0-1~bpo10+1
  Candidate: 1:2.27.0-1~bpo10+1
  Version table:
 *** 1:2.27.0-1~bpo10+1 100
        100 https://deb.debian.org/debian buster-backports/main amd64 Packages
        100 /var/lib/dpkg/status
     1:2.20.1-2+deb10u3 500
        500 https://deb.debian.org/debian buster/main amd64 Packages
        500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
xdelta:
  Installed: 1.1.3-9.2
  Candidate: 1.1.3-9.2
  Version table:
 *** 1.1.3-9.2 500
        500 https://deb.debian.org/debian buster/main amd64 Packages
        100 /var/lib/dpkg/status
xdelta3:
  Installed: 3.0.11-dfsg-1+b1
  Candidate: 3.0.11-dfsg-1+b1
  Version table:
 *** 3.0.11-dfsg-1+b1 500
        500 https://deb.debian.org/debian buster/main amd64 Packages
        100 /var/lib/dpkg/status

Can check it out just fine on my buster machine, but checkout fails in a sid chroot - both on my machine and on Salsa CI.

# pristine-tar checkout python-azure_20201118+git.orig.tar.xz
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
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

Repo:

https://salsa.debian.org/bluca/python-azure.git

Re-committing the same tarball seems to fix the issue. Left the old,
broken commit on a specific branch if needed for future inspection and
repro:

https://salsa.debian.org/bluca/python-azure/-/tree/pristine-tar-broken

should be caused by:
- https://bugs.debian.org/897653

if you upgrade tar to buster version 1.30+dfsg-6 or later, it should
be resolved.

ii  pristine-tar   1.49         amd64        regenerate pristine tarballs
ii  tar            1.34+dfsg-1  amd64        GNU version of the tar archiving utility
and I still have the problem.

I try to upgrade the package 0ad to a new upstream version but that fails:
$ gbp import-orig --uscan
gbp:info: Launching uscan...
gbp:info: Using uscan downloaded tarball ../0ad_0.0.25.orig.tar.xz
What is the upstream version? [0.0.25]
gbp:info: Importing '../0ad_0.0.25.orig.tar.xz' to branch 'upstream'...
gbp:info: Source package is 0ad
gbp:info: Upstream version is 0.0.25
gbp:error: Import of ../0ad_0.0.25.orig.tar.xz failed: Couldn't commit to 'pristine-tar' with upstream 'c98ef96af6f9638844dce03af30a3060b677fee2': pristine-xz failed to reproduce build of ../0ad_0.0.25.orig.tar.xz
(Please file a bug report.)
pristine-tar: failed to generate delta
gbp:error: Error detected, Will roll back changes.
gbp:info: Rolling back branch upstream by resetting it to 86bb850b0a939ace014cbd3b7126410c258fc25c
gbp:info: Rolling back branch pristine-tar by resetting it to f0bd6693182069f87ebd7f5ab8e28911ffc157db
gbp:error: Rolled back changes after import error.

I tried with a fresh "git clone" of 0ad but the problem is still
present.

I don't want to regerenrate old tarballs, but to add a new one.

I extracted the upstream 0ad_0.0.25.orig.tar.xz and regenerated a new
.tar.xz file and this time the inclusion worked:
$ gbp import-orig ../0ad_0.0.25.orig.tar.xz
What is the upstream version? [0.0.25]
gbp:info: Importing '../0ad_0.0.25.orig.tar.xz' to branch 'upstream'...
gbp:info: Source package is 0ad
gbp:info: Upstream version is 0.0.25
gbp:info: Replacing upstream source on 'master'
gbp:info: Successfully imported version 0.0.25 of ../0ad_0.0.25.orig.tar.xz

But, of course, the archived version is not more a "pristine-tar" since
that is one that I re-created myself.

I have no idea what version of tar was used by upstream.
Upsteam file is available at https://releases.wildfiregames.com/0ad-0.0.25-alpha-unix-data.tar.xz

Bye

I ran into a similar problem today with the git repository available
from <URL: https://salsa.debian.org/deeplearning-team/whisper.cpp.git >,
on Debian Bookworm:

% gbp buildpackage
gbp:info: Creating /scratch/pere/src/whisper.cpp_1.7.4.orig.tar.gz
gbp:error: Error creating whisper.cpp_1.7.4.orig.tar.gz: Pristine-tar couldn't checkout "whisper.cpp_1.7.4.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
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
%

I have no idea how I ended up here.  The tarball was imported using
'gbp import-orig' the same way I normally do this.  Do anyone want to
have a closer look before I do my best to work around the problem?

Hi!

I've seen this same error message in multiple bug reports:

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
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933031
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897421
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897653
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924912

And also in
https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/326