Re: [Bug-tar] --verbatim-files-from change breaks pristine-tar

[Sergey Poznyakoff]

Bdale Garbee <address@hidden> ha escrit:

> 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

I have only a vague idea about pristine-tar. Does it do extraction using
the -T option and a list of members to extract? What other options are
used?

> Is it expected / correct that --unquote and --verbatim-files-from no
> longer work together?

Yes, that's right. The intent of dee7e3f16e74 was to fix the
functionality of the --verbatim-files-from option[1]. That's
reflected in the description of that option as well:

  "-T reads file names verbatim (no escape or option handling)"

The --unquote option effectively defeats the purpose of
--verbatim-files-from, so I don't see much sense in using the two
options together, especially given that --unquote behavior is the
default.

> 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

So, what kind of patch is needed? I would suppose you'd like
--verbatim-files-from to not do any option handling, while still
unquoting file names. Am I right?

> 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).

I quite agree with the suggestion.

Regards,
Sergey

[1] http://lists.gnu.org/archive/html/bug-tar/2017-10/msg00015.html