usrmove breaks on directory name conflict

Michal Schmidt mschmidt at
Mon Apr 23 16:25:06 UTC 2012

On 04/23/2012 05:45 PM, Daniel Drake wrote:
> cp: cannot overwrite directory /mnt/sysimage/usr/bin.usrmove-new/mkdir
> with non-directory
> Something failed. Move back to the original state.
> Rebooted back into F16. It looks like the issue was that I had a
> directory at "/usr/bin/mkdir/". No idea how, looks like it was from
> December. Probably my fault, but perhaps usrmove shouldn't fall over
> when facing this situation.

If usrmove really reverted everything to its original state, it seems to 
me like a case of well-behaving error handling after encountering an 
unusual situation that cannot be resolved automatically and safely.


More information about the devel mailing list