On Wednesday 03 November 2010 00:29:32 Paul Eggert wrote: > In the meantime I'll CC: this to help-tar, so that people there > are aware of the situation. Briefly, the proposal is to change > GNU tar so that: > > tar -cf ../archive.tar * > > works regardless of the file names that "*" expands to. Currently, > if one of the file names contains backslash-backslash, or backslash-n, > those sequences are interpreted as backslash and as newline, > respectively, which means the "tar" command won't behave as > expected.
I'm unsure if this description actually covers the problem which Динар reported on on Tuesday 02 November 2010 11:08:41: > i have tested that with giving simple argument without backslashes, for > that i have created a directory "sed" and copied the file into it, then > have archived the directory this way: > > tar -cf x.tar "/home/dinar/Документы/sed" > > and it has worked, that means when i have opened that archive with > file-roller, i have seen correct file name in it, and size of archive is > correct. > though, i could not extract it with file-roller; and i could not extract > it with tar this way: i have renamed old sed directory to sed0 and > entered this command: > > tar -xf x.tar > > and new sed directory has not been created, though i have not seen any > error message, and , listing files has not showed correct file name, > with this command: > > tar -tvf x.tar > > it has reported: > > drwxr-xr-x dinar/dinar 0 2010-11-02 12:57 > home/dinar/Документы/sed/ > -rw-r--r-- dinar/dinar 65863 2010-09-29 18:29 > home/dinar/Документы/sed/SED: How can I replace > a newline (\\n)? - Stack Overflow.html > id est, it has shown backslash with double backslash, that is not > correct. I suspect -- also because of my observation that tar was working on the offending file if the file name contained either three or four backslashes, which appears to be inconsistent -- that the unquote routine is buggy itself.
