> From: Torsten Landschoff [mailto:torsten@debian.org]
>
> As I am reorganizing some subversion repositories today I stumbled
> across a "misfeature" in subversion. Basically I was splitting a trunk
> directory from "trunk" to "trunk-2.1" and "trunk-2.2" for different
> upstream version of the software I am working on.
>
> Now I was curious what would happen to checked-out copies. After
> renaming I got the following error message from svn update:
>
> svn: Cannot replace a directory from within
>
> Well, I wondered why that is as the name of the WC is not
> linked to the
> name in the repository.
The problem is that Subversion does not (yet) have true renames. What
appears to be a rename is a copy from the old name to the new name, followed
by a delete of the old name. Thus, when you try to update, the forward
history of "trunk" is "it is deleted in rev 435".
There are probably other, independent complications, but currently there is
no reason to expect Subversion to correctly update a WC when it must rename
directories containing locally-changed files.
Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 1 18:17:48 2005