Package: git-debpush Version: 13.16 Severity: normal Dear Maintainer,
I was testing out local commands to help hypothetical collaborators who are confused by the absence of the pristine-tar anti-pattern in my package. Running 'git deborig' I obtained a different tarball from what 'git debpush' had previously caused to be generated by the tag2upload builder. It would be nice to make sure that an out-of-the-box local invocation produced bit-exact tarballs to what tag2upload produces to reduce the barriers to understand and accept this type of workflow. (Aside: I also wonder if the use of xz rather than gzip is sufficiently beneficial in terms of space saving to justify the greater difficulty (as I understand it - unless I have been taken in by FUD!) to guarantee reproducibility.) tag2upload job id: 1365 The Debian tag: $ git show debian/0.75.0-1 tag debian/0.75.0-1 Tagger: Andrew Bower <[email protected]> Date: Fri Oct 10 01:27:46 2025 +0100 wtmpdb release 0.75.0-1 for experimental [dgit distro=debian split --quilt=gbp] [dgit please-upload source=wtmpdb version=0.75.0-1 upstream-tag=v0.75.0 upstream=a6f185a241ee633cbba600029ec153feb2665cf8] The Upstream tag: commit a6f185a241ee633cbba600029ec153feb2665cf8 (tag: v0.75.0, tag: upstream/0.75.0, upstreamvcs/main, upstreamvcs/HEAD) Local tarball generation and comparison: $ git deborig v0.75.0 $ sha256sum ../wtmpdb_0.75.0.orig.tar.xz cda596421261c2025c9a3f186e809255ef583ee2eae7a8e37c34eb7d36b51b68 ../wtmpdb_0.75.0.orig.tar.xz $ dgit download-unfetched-origs canonical suite name for experimental is rc-buggy suite has origs for this upstream version dgit: error: file wtmpdb_0.75.0.orig.tar.xz has hash cda596421261c2025c9a3f186e809255ef583ee2eae7a8e37c34eb7d36b51b68 but we need hash 237f6ac11e6360b2c553fe513c28567020f3a42fa4c02fb5eab8968ac79afa96 (perhaps you should delete this file?) Some relevant additional information: ii xz-utils 5.8.1-2 amd64 XZ-format compression utilities Comparing xz files: ├── xz --list │ @@ -1,16 +1,16 @@ │ Streams: 1 │ Blocks: 1 │ - Compressed size: 33.2 KiB (34020 B) │ + Compressed size: 33.2 KiB (34028 B) │ Uncompressed size: 240.0 KiB (245760 B) │ Ratio: 0.138 │ Check: CRC64 │ Stream Padding: 0 B │ Streams: │ Stream Blocks CompOffset UncompOffset CompSize UncompSize Ratio Check Padding │ - 1 1 0 0 34020 245760 0.138 CRC64 0 │ + 1 1 0 0 34028 245760 0.138 CRC64 0 │ Blocks: │ Stream Block CompOffset UncompOffset TotalSize UncompSize Ratio Check CheckVal Header Flags CompSize MemUsage Filters │ - 1 1 12 0 33984 245760 0.138 CRC64 64d299834c1556d0 12 -- 33961 9 MiB --lzma2=dict=8MiB │ + 1 1 12 0 33992 245760 0.138 CRC64 64d299834c1556d0 20 cu 33961 9 MiB --lzma2=dict=8MiB │ Memory needed: 9 MiB │ - Sizes in headers: No │ + Sizes in headers: Yes │ Minimum XZ Utils version: 5.0.0 Thanks, and I hope this isn't a duplicate of another bug report I missed, this time! Andrew -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.16.8+deb14-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages git-debpush depends on: ii git 1:2.51.0-1 ii gpg 2.4.8-3 ii gpg-agent 2.4.8-3 ii libdpkg-perl 1.22.21 git-debpush recommends no packages. git-debpush suggests no packages. -- no debconf information
