After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 141763 - Nautilus erase previous content of a directory when copying from another one whith the same name instead of merging
Nautilus erase previous content of a directory when copying from another one ...
Status: RESOLVED DUPLICATE of bug 48085
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.6.x
Other Linux
: Urgent critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-03 20:42 UTC by Djamé
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Djamé 2004-05-03 20:42:04 UTC
what happenned ?
1) take 2 directories with the same name
2) copy one to another
3) the contents of the one who is receiving the copy is erased
what I expect ?
1) exactly as cp -R
2) exactly as gmc
3) exactly as gnome-commander or even every kind of filemanager I used in my life
the content should have been merged and updated...
It means do you want to replace ? but not erased the file from dir 1 which are
not present in dir 2 !!!!!!!!!!!!!!!
Comment 1 Djamé 2004-05-03 20:44:18 UTC
I'm still hallucinating from this one, I know it has been reported the first
time in 2001 and I still can't believe it's still here and shipped whith every
recent distribution.....

Comment 2 Richard Kinder 2004-05-03 23:46:51 UTC
This also happens for nautilus 2.6 - is this as designed? If so, it is
counter-intuitive and dangerous for users migrating from Windows.

At the very least, one would expect the popup 'Conflict While Copying' dialog to
offer the option of merging the direcories (Skip, Replace, Merge).

Reducing priority/severity as the dialog that pops up does warn that the 'file'
will be replaced (sub-optimal text since it is the directory being replaced).
Also changing the versions as there is probably more chance it will get fixed if
it is against the latest version :)
Comment 3 Djamé 2004-05-04 00:22:56 UTC
the most incredible is that this bug has already been resolved because someone
has sent a patch against it, look at this bug report :

http://bugzilla.gnome.org/show_bug.cgi?id=48085


I was hoping it was not present into gnome2.6, so it's not worth upgrade...

I'm going to try velocity just to see if it has this now called worst bug ever......

yeeeeeah, man, one more year and it will be top 1 in the top 10 bugzilla bug...
(most frequently reported bug)


Comment 4 Richard Kinder 2004-05-04 06:32:52 UTC

*** This bug has been marked as a duplicate of 48085 ***