I've run in to this problem, I think the way I recovered was I removed
the parent dir of the failing object, then updated, switched back to the
original repository url, and then finally tried the original switch
again. This might be somewhat overkill, but it seemed to be the most
reliable way I could figure out to unclobber the working copy. I would
certainly be in favor a feature making this easier or easier to avoid.
-Brad
Hjörtur Arnarson wrote:
>Hi.
>
>I am having trouble with recovering from a failed switch. A switch fails when it needs to delete a file or a directory that has not been added to the repository. When this happens, what is the best way to recover. Update or switching back does not seem to work. Is this a known issue? It would be great if the possibility of making a forced switch was available; a forced switch means that svn deletes the files, directories that it needs to delete, even they are not part of the repository.
>
>Please see the enclosed sample to reproduce this behavior.
>
>Hjörtur A.
> <<runtest.zip>>
>
>
>------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 14 23:19:34 2004