Bas van Schaik <[EMAIL PROTECTED]> wrote: > Package: coreutils > Version: 5.97-5 > Severity: normal > > When using >> cp -lar srcdir/* targetdir > > on a srcdir containing files (no matter how deep in srcdir) with spaces in > their filenames, cp complains: >> cp: cannot create hard link `targetdir/(...)/filename' to >> `targetdir/(...)/filename': No such file or directory
Thanks for the report. I am unable to reproduce that. Please try to create a small test case that demonstrates the problem. For example, here's one of the things I've just tried: $ rm -rf a x; mkdir a x; touch 'a/b ' 'a/d e'; /bin/cp --verbose -lar a/* x `a/b ' -> `x/b ' `a/d e' -> `x/d e' > This cryptical message (which implies trying to create a hardlink from a file > to itself?) is caused by a filename > containing a space. Note that I took the quotes in the above messages exactly > as they were: not even a small hint > about a whitespace at the end of a filename, it took me ages to find the > cause of this problem! Also note that > this problem isn't related to some kind of shell variable expansion, since > I'm using recursive cp. The file > responsible for my problems was about 5 levels deep in the directory > structure under srcdir. > > In my opinion cp should be able to handle filenames containing all kinds of > permitted characters, this includes > filenames with a white space at the end. As far as I know, cp has always been able to handle such names. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
