Hi.

A couple Debian users have reported issues using our packaging of tar
1.30 to unpack source packages made with 1.29 and prior stored in git
repos using pristine-tar, due to an unfortunate side-effect of

http://git.savannah.gnu.org/cgit/tar.git/commit/?id=dee7e3f16e74e07504bb8f4d80426005fe4364ae

My thanks to Eric Prestemon for figuring out which commit was at fault,
and for his diagnosis and thoughts documented at

http://tech.prestemon.com/debugging/2018/08/09/debian-bug-901952.html

Is it expected / correct that --unquote and --verbatim-files-from no
longer work together?  I'm trying to figure out the least obnoxious
patch that would enable recovery of pristine-tar archives created with
1.29 and older using 1.30.  If this was an unexpected side-effect and
there's already an upstream commit I can pull and/or you're willing to
suggest a suitable patch, that'd be awesome.

Independently, I'd be pleased to have your opinions on Eric's suggestion
that pristine-tar switch to using --null in the future (which I don't
have control over but could make suggestions to the maintainer about).

Regards,

Bdale

Attachment: signature.asc
Description: PGP signature

Reply via email to