Comment 13 for bug 2045452

Hi Otto,

Indeed, I tested a build of mariadb-10.3 on a bionic system and indeed the build works without issues.

Now looking at your previous sponsoring request in February 2023 and this one, I don't see any updates for xdelta3 in jammy nor for git-buildpackage. Therefore I think it must be something else that was updated in between those two.

What I also did, was to comment the line `pristine-tar = True` in debian/gbp.conf. That solves the issue, but instead of continuing with the build, I stopped and saw that in ../ I had mariadb-10.3_10.3.39.orig.tar.gz
So I returned the uncommented the pristine-tar line again and tried again to build, and got the following:

$ gbp buildpackage --git-builder="umt source"
gbp:error: Pristine-tar couldn't verify "mariadb-10.3_10.3.39.orig.tar.gz": pristine-tar: /home/ubuntu/packages/mariadb-10.3/mariadb-10.3_10.3.39.orig.tar.gz does not match stored hash (expected 18bd51c847565af4da18748b052ab9bcbb569ab6e6766ca8da7dcca1f941f876, got 0cd8e4fb9c41e0d08a8ea6b6ebb77bc7c50d5a92a60b99155a342e7a5e3a9255)

and if I do
$ sha256sum ../mariadb-10.3_10.3.39.orig.tar.gz
0cd8e4fb9c41e0d08a8ea6b6ebb77bc7c50d5a92a60b99155a342e7a5e3a9255 mariadb-10.3_10.3.39.orig.tar.gz

If I manually download the tarball from the URL you shared, check the checksum, it matches what you pasted and the build passes.

So I'm not sure how is it possible that on bionic it gets the correct orig.tar.gz with the expected checksum, but on a jammy or lunar host it downloads a tarball with a different checksum.