Le Fri, Sep 12, 2025 at 04:03:52PM +0530, Nilesh Patra a écrit :
If there is a way to add the test data in a single tar without inflating the size of debian/ dir, I agree that this would be fair enough. However, I have no idea how to do that.
Hi Nilesh, I tried to research about multi-tar packages, and I am under the impression that when a multi-tar package A's version increases, both a new A_version.orig.tar.gz and new A_version.orig-foo.tar.gz tarball has to be uploaded, so unless the archive does smart deduplication there is no gain..._ Le Fri, Sep 12, 2025 at 02:25:16PM +0300, Andrius Merkys a écrit :
I might have missed something, but why we are losing the byte-to-byte identity?
Hi Andrius, if we do gbp import-orig with foo.tgz, and then gbp buildpackage, only if we use --pristine-tar we can recreate an orig tarball from scratch that is identical to what we gave to gbp. In the git debpush workflow, the orig tarball is recreated from the Git repository if it does not exist in the Debian archive. It has the same files but not necessarly the same checksum as upstreams source tarball, but this is not a blocker because if we want to do a Debian revision to the source package, we (and tag2upload) can download Debian's version of the upstream source tarball, and therefore keep it stable. Have a nice week-end! Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from work, https://fediscience.org/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
