Control: severity -1 minor Hi Sean,
On Sat, Oct 11, 2025 at 03:36:37PM +0100, Sean Whitton wrote: > On Sat 11 Oct 2025 at 01:09pm +01, Andrew Bower wrote: [...] > > 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. [...] > tag2upload doesn't invoke git-deborig in any special way, so this > difference can only be due to version skew between tar and/or xz-utils > on the tag2upload Builder and your machine. > > I don't think there is much we can do other than preserve information > about the versions of the software involved, which we already do in the > .buildinfo file included with the upload. That is a reasonable position in principle but iff developers develop predominantly on unstable hosts it seems to me that this is likely to hit every upload so a small change on the build server might have an outsized benefit. I just picked an upload of a new upstream, cage/0.2.1 (job 1322) and it had exactly the same problem.
