Re: svn mv in wc seems to leave remnant directories

On Wed, 2004-03-31 at 13:55, Ryan Hunt wrote:
> I am noticing that given the following dir structure:
>
> /trunk
> /dir1
> /dir2
>
> and the following command
>
> cd /trunk
> svn mv dir1 dir2/dir1

'svn mv A B' is the same as running 'svn cp A B; svn rm A'

Therefore, after your move command, if you run 'svn status', you should
see dir1 scheduled for deletion, and dir2/dir1 scheduled for
addition-with-history.

That's why dir1 isn't gone yet. It's only *scheduled* for deletion.
After you 'svn commit', all will be normal. dir1 will be gone, and
dir2/dir1 will be truly added.

> svn: Commit failed (details follow):
> svn: Out of date: '/trunk/doc/esx' in transaction '1e'

And the reason you can't commit is because dir1 is out-of-date. You
can't delete a directory whose working revision is not equal to HEAD.
Run 'svn up' from the top of your working copy, then 'svn commit' will
work.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 31 21:55:25 2004