Re: [Bug-tar] errors with some paths/filenames in null-separated file-list

[Sergey Poznyakoff]

address@hidden wrote:

> all problematic filenames/paths includes newlines, but newline only is
> not the cause.

It's a coincidence, the newline is not needed to trigger the bug.

The real reason are backslash caracters: by default tar "unquotes"
the filenames it reads with -T option, i.e. it translates
backslash+char combinations to single char (\n -> newline,
\t -> tab, etc.). However, output produced by find (both -print0
and -print) does not need such processing. I will add a
--no-unquote option to handle such cases.

Thank you for reporting the issue.

Regards,
Sergey