Patrick Heinemann <heinemann@informatik.uni-tuebingen.de> writes:
> I have recently changed the directory layout of our software, e.g.
> $> cd trunk/
> $> svn move IPC/ inter_process_com
> D + IPC
> A + inter_process_com
> $> svn commit
> commited revision 1005
> and so on...
>
> Now I tried to update a users working copy which he had changed meanwhile at
> some files. The result was:
> $> cd trunk/
> $> svn update
> svn: Cannot replace a directory from within
>
> What does that mean? The moved directories all are subdirectories of the
> trunk/ directory. This even happens with
> $> cd ..
> $> svn update trunk/
> svn: Cannot replace a directory from within
>
> Is there a problem with updating working directories when main directories
> where moved or is it just because the working directory was changed in the
> meantime?
Without knowing that user's local changes, it's impossible to say why
this is happening. What were his local changes before the update?
> This should not be the behaviour of a versioning system, right?
Subversion's bug tracker "should" be empty, too :-).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 6 18:22:41 2004