[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Error: Cannot replace a directory from within after a move.

From: Eric Hoch <svn_at_erichoch.org>
Date: 2006-05-03 23:53:50 CEST


    One of our developers recently copied the trunk of a project to a
tag named "tags/Phase 4/trunk", and began committing changes against it.
Since it's not entirely logical to commit changes against a tag, I set
out to resolve this issue. I did the following:

- I moved the "trunk" directory to the "branches" folder, creating
- I renamed "branches/trunk" to "branches/Phase 4"

Next, I attempted to update my working copy. Instead of updating to the
latest version, which I expected to be the newly created branch, I
received the following message:
"Cannot replace a directory from within after a move."

This isn't too big of a deal, since I can switch my working copy to the
new URL. I was just expecting it to be a bit more "seamless", I guess.

Also, there was another developer working on the old path, and when she
attempted to commit her changes to the now non-existant path, she
received the same message. She then attempted an update and received the
same message, but only after several files were deleted from her working
copy, including files which had changed and were not yet comitted. She
tried to revert, but obviously that would do no good since those changes
existed only in the working copy. Is that the expected behavior?

Finally, what would be the best way to handle changes like this in the
future, to avoid the issues outlined above?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 3 23:55:12 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.