Paul Eggert <egg...@cs.ucla.edu> writes: > On 05/14/2018 07:56 AM, Antonio Terceiro wrote: >> I still need to study the > code a bit further to try to come up with a >> better suggestion. > Sorry, the only suggestion I can make is that you should just use the > new GNU tar. The old one was obviously busted and it generated busted > tarballs.
Antonio, given this, I wonder if maybe the right approach might be to come up with a work-around so that pristine-tar can collaborate with tar to successfully extract older tarballs from git repos? I could imagine a Debian-specific patch that adds a long-form command-line option to do the equivalent of reverting that one patch, and a mod to pristine-tar to try that option if reproducing the tarball fails before giving up entirely? In this way, Debian developers could continue to be able to rebuild and work on packages with older tarballs captured using pristine-tar, but all new work would be in the correct format. This means all developers would want to get to tar 1.30 or later as soon as possible, but at least we wouldn't lose access to all our existing work. What do you think? Bdale
signature.asc
Description: PGP signature
