On Fri, 2003-10-31 at 06:10, Gareth McCaughan wrote:
> [I don't intend the subject to imply that this happens *every* time
> you do "svn mv" on a non-empty directory, though I haven't checked
> that it doesn't.]
>
> If I do the following ...
>
> svnadmin create Repo
> svn co file://localhost`pwd`/Repo wc
> cd wc
> svn mkdir dir
> svn commit -m 'made dir'
> touch dir/file
> svn add dir/file
> svn commit -m 'made dir/file'
> svn mv dir dir2
> svn commit -m 'moved dir to dir2'
>
> ... then the last operation fails with this output:
>
> Deleting dir
> svn: Transaction is out of date
> svn: Commit failed (details follow):
> svn: out of date: 'dir' in transaction '3'
>
> Is this really reasonable?
For now, yes, this is expected. If you had run 'svn up' before
attempting to commit, it would have worked.
The problem is that 'svn mv' == 'svn cp; svn rm'. And one of our two
rules of directory versioning is "you cannot delete something that is
out of date." The commit had no problem adding 'dir2' as a copy of
'dir', but because 'dir' was not at HEAD, the server refused to delete
it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 31 14:58:42 2003