pristine-tar fails to reproduce the tarball

[Nafallo Bjälevik]

RUN ['git-build-recipe', '--safe', '--no-build', '--manifest', '/home/buildd/build-RECIPEBRANCHBUILD-2920304/chroot-autobuild/home/buildd/work/tree/manifest', '--distribution', 'jammy', '--allow-fallback-to-native', '--append-version', '~ubuntu22.04.1', '/home/buildd/build-RECIPEBRANCHBUILD-2920304/chroot-autobuild/home/buildd/work/recipe', '/home/buildd/build-RECIPEBRANCHBUILD-2920304/chroot-autobuild/home/buildd/work/tree']
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

Link to recipe: https://code.launchpad.net/~volvo-cars-ubuntu/+recipe/vcul-ansible
Link to buildlog: https://code.launchpad.net/~volvo-cars-ubuntu/+archive/ubuntu/staging/+recipebuild/2920304/+files/buildlog.txt.gz

[Colin Watson (cjwatson)]

In the past this sort of thing has been fixed by upgrading our pristine-tar backport (ppa:launchpad/ubuntu/buildd-staging → ppa:canonical-is-sa/ubuntu/buildd) by backporting it from Debian unstable, but we'll need to reproduce the problem locally first and confirm that an updated pristine-tar actually fixes it. It's also possible that we might need to upgrade some other tool such as xdelta3 as well as or instead of this.

[Nafallo Bjälevik (nafallo)]

Some extra information regarding this one. I could checkout the pristine-tar fine on an up-to-date focal, and I had the failure when I gbp import-orig --uscan on focal this morning. I reset --hard my branches back to upstream (Debian in this case) version of the packaging and force pushed them until we get this resolved however. The linked build log is with that revert in play.

Hopefully this information is valuable in trying to narrow this down. Feel free to poke me if I can help with this in any way.