Christian Perrier wrote: > My build machine is still running wheezy and therefore has > pristine-tar version 1.25 > > My fellow co-maintainers do not have this problem with a sid machine > (and pristine-tar 1.28). > > Is that a known problem?
pristine-tar only allows whitelisted command parameters in its delta
files. This is to prevent a bad actor publishing a git repository that
unexpectedly emails them your gpg private key or something[1].
This means that as new features of compression programs get supported in
pristine-tar, it has to whitelist them, and older versions will then not
be able to check out those tarballs. Of course, other bug fixes in
pristine-tar can also cause the same effect.
The only solution I can see is for someone to backport pristine-tar for
wheezy, if they need to use it for development with others who are using
the newer version.
The actual bug here, which I've fixed in git, is that the error message
is wrong! The param it is actually rejecting is --check=crc64
--
see shy jo
[1] assuming gzip or xz one day conform to the maxim that all programs
grow to the point that they can send email
signature.asc
Description: Digital signature
