Bug 2676 - Directory replaced by a single file cannot be deleted
Summary: Directory replaced by a single file cannot be deleted
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 2.5.7
Hardware: All other
: P3 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
URL: http://www.adelard.co.uk/info/staff/p...
Depends on:
Reported: 2005-05-03 02:28 UTC by Peter Bishop
Modified: 2005-06-03 01:39 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Peter Bishop 2005-05-03 02:28:50 UTC
NB found in rsync version 2.5.5
but this version not available on the form
So this is a bit old - but could not see a similar bug in Bugzilla

I use rsync to archive a Windows machine (with SMB shares). 
The Windows machine uses Zipmagic which makes ZIP
files appear as normal folders.

If Zipmagic is disabled. ZIP file becomes a normal file 
(not a folder)
If I  rsync again, it complains that it cannot delete the XXX.ZIP 
directory (because it contains other files)

Possible cause:
rsync does not expect a folder name to be replaced by
a normal file with the same name, i.e. it assumes the
type is the *current* type of XXX.ZIP (a folder), not the type that was last
archived (a directory) and so cannot delete it if it performs a simple single
file delete.
Comment 1 Wayne Davison 2005-05-03 08:20:28 UTC
Sounds like you failed to specify --force.