https://bugs.kde.org/show_bug.cgi?id=499245
--- Comment #3 from Felix Ernst <felixer...@kde.org> --- Let's first identify what even is going wrong here. > STEPS TO REPRODUCE > 1. Create a /usr folder elsewhere, add directories /bin /lib /share (may only > just require /usr not even need to do this I'm not gonna break my system over > and over to test lol) and add some files in it. 1. So you have two /usr folders. One is in root i.e. "/usr", the other is somewhere else i.e. "/some/other/place/usr" > 2. Merge this with the actual /usr folder 2. You now "merge" the two. I assume this means moving the folder "/some/other/place/usr" to "/", you are then asked what to do because there is already a "usr" folder there and you choose "Merge". > 3. Hit Ctrl + Z I think now it tries to undo the previous move of the folder "/some/other/place/usr" to "/". So it takes the only "/usr" folder that still exists and "puts it back" to "/some/other/place/usr". That's my interpretation of what is happening. I don't think this is an admin-specific issue. If my above interpretation is correct, the issue is that we store the moving of "/some/other/place/usr" to the already existing "/usr" as a creation of a "/usr" folder when in reality it already existed. The solution is probably to not store "moves of folders that already existed" (which are not really "moves" in the first place because a directory with that name already exists) and not have this as something that can be undone. Only the actual move operations on files need to be stored. -- You are receiving this mail because: You are watching all bug changes.
