Hans-Christoph Steiner <h...@eds.org> writes: > this also goes the other way, where tarballs created in tar 1.30 fail to > work in pristine-tar when tar 1.29 is installed:
Unfortunately, the nature of pristine-tar is such that it's somewhat brittle in the face of upstream changes to tar. I don't think it's unreasonable to expect someone working on a package to have a version of tar installed that's at least as new as the one used to create the package. And as long as we have the work-around of temporarily installing an older version of tar to recover source packages created with older archives, none of this should rise to the level of release criticality for the tar package itself in my mind. Having said that, I just forwarded this bug upstream and hope we'll get some useful advice. Bdale
signature.asc
Description: PGP signature
