On Fri, Jun 20, 2025 at 06:20:14PM +0000, Debian FTP Masters wrote:
> trustedqsl_2.8.1-1~bpo12+1.dsc: Invalid size hash for trustedqsl_2.8.1.orig.tar.gz:
> According to the control file the size hash should be 4123027,
> but trustedqsl_2.8.1.orig.tar.gz has 4125568.
>
> If you did not include trustedqsl_2.8.1.orig.tar.gz in your upload, a different version
> might already be known to the archive software.
Perhaps there is an issue with gbp or how we are performing imports?
Below are 4 mechanisms for retrieving/regenerating the orig tarball:
1. pulling the tarball in the achive
apt-get source trustedqsl
ls -gG trustedqsl_2.8.1.orig.tar.gz
-rw-r--r-- 1 4125568 May 1 02:10 trustedqsl_2.8.1.orig.tar.gz
2. using the pristine-tar command directly
debcheckout --auth --git-track '*' trustedqsl
cd trustedqsl
pristine-tar checkout trustedqsl_2.8.1.orig.tar.gz
ls -gG trustedqsl_2.8.1.orig.tar.gz
-rw-rw-r-- 1 4125568 Jun 20 11:57 trustedqsl_2.8.1.orig.tar.gz
3. building with gbp specifying --git-pristine-tar
gbp buildpackage --no-clean --chroot=bookworm-amd64 --git-debian-branch=debian/bookworm-backports --git-pristine-tar
gbp:info: Tarballs 'trustedqsl_2.8.1.orig.tar.gz' not found at '../tarballs/'
gbp:info: Creating /data/debian/sponsor/trustedqsl/build-area/trustedqsl_2.8.1.orig.tar.gz
...
ls -gG ../build-area/trustedqsl_2.8.1.orig.tar.gz
-rw-rw-r-- 1 4125568 Jun 20 12:16 ../build-area/trustedqsl_2.8.1.orig.tar.gz
4. building with gbp *without* specifying --git-pristine-tar
gbp buildpackage --no-clean --chroot=bookworm-amd64 --git-debian-branch=debian/bookworm-backports
gbp:info: Tarballs 'trustedqsl_2.8.1.orig.tar.gz' not found at '../tarballs/'
gbp:info: Creating trustedqsl_2.8.1.orig.tar.gz from 'upstream/2.8.1'
^^^^^^^^^^^^^^
...
ls -gG ../build-area/trustedqsl_2.8.1.orig.tar.gz
-rw-rw-r-- 1 4123027 Jun 20 12:19 ../build-area/trustedqsl_2.8.1.orig.tar.gz
Looking at the difference between the tarballs, the contents are
identical; the only difference is the first segment of the path:
In the pristine-tar/archive file, all files are beneath tqsl-2.8.1/...
In the gbp-generated file, all files are beneath trustedqsl-2.8.1/...
I guess it makes sense that the build process in (4) doesn't have any
knowledge of the original top-level directory in the tarball when it was
extracted into the upstream branch.
Maybe there is a way to tweak debian/watch or the original gpb
import-orig step so these don't get out of whack. Can we specify to
strip the first segment of the path?
Thanks,
tony
Attachment:
signature.asc
Description: PGP signature