bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not

2013-10-26 Thread Linda Walsh
I was trying to update a copy of /var (=>/root2/var). It issues non-fatal, failure messages when copying from or to a non-dir entry to a dir entry. I tried -a to force the removal of the target dir, or target file. It didn't work. I tried --remove-destination, which is clearly not "file" speci

bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not

2013-10-27 Thread Pádraig Brady
On 10/27/2013 03:48 AM, Linda Walsh wrote: > > I was trying to update a copy of /var (=>/root2/var). > It issues non-fatal, failure messages when copying from or to > a non-dir entry to a dir entry. > > I tried -a to force the removal of the target dir, or target file. > > It didn't work. > > I

bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not

2013-10-28 Thread Linda Walsh
On 10/27/2013 5:38 PM, Pádraig Brady wrote: So overwriting files with dirs and vice versa is prohibited by POSIX. The existing cp options do not adjust this aspect. If you don't care what's in the destination at all, why not just rm it before the copy? Um --- isn't that what the "--remove-d

bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not

2013-10-28 Thread Bernhard Voelker
Hi Linda, On 10/28/2013 08:09 AM, Linda Walsh wrote: > On 10/27/2013 5:38 PM, Pádraig Brady wrote: >> So overwriting files with dirs and vice versa >> is prohibited by POSIX. The existing cp options >> do not adjust this aspect. If you don't care what's >> in the destination at all, why not just

bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not

2013-10-28 Thread Linda Walsh
On 10/28/2013 1:56 PM, Bernhard Voelker wrote: If you don't care what's in the destination at all, why not just rm it before the copy? "--remove-destination" option is supposed to do? "info coreutils 'cp invocation'" says: But if I specify "-a" or "-r" those imply recursive. Why

bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not

2013-10-29 Thread Bernhard Voelker
> On October 28, 2013 at 11:05 PM Linda Walsh wrote: > On 10/28/2013 1:56 PM, Bernhard Voelker wrote: >> [...]  Tools like rsync may be better for such a scenario >> than cp(1) which is made primarily to > [...]  As for 'rsync', it's speed is *comparatively* abysmal > for local-to-local copies.

bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not

2013-10-29 Thread Philipp Thomas
* Bernhard Voelker (m...@bernhard-voelker.de) [20131029 12:26]: > hmm, well, could it be that this is because many features have > been added over the years? ... Leave alone checks that cp needs to do but dd doesn't. Philipp

bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not

2013-10-29 Thread Linda Walsh
So why not enhance rsync regarding performance? It's designed for slow, remote copies. It special-cases local copies, but uses much of the of the old code. It also follows it's manpage. It also does id translation and storage of ACL's and Xattrs on file systems that don't support it.

bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not

2019-01-11 Thread Assaf Gordon
severity 15727 wishlist retitle 15727 doc: cp: expand dirs-vs-files with -f/--remove-dest stop Hello, On 2013-10-29 12:20 p.m., Linda Walsh wrote: [...] You need to make the docs much more clear about "cp"s limitations. update isn't eally update, and -T is certainly wrong at the very least.