Failed Switch?

[Hjörtur Arnarson <ha...@medcare.is>]

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>> 

RE: Failed Switch?

[Dale Worley <dw...@pingtel.com>]

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]

There was, until very recently, a nasty bug in 'svn switch' which did
exactly this:  if you interrupted it, it would leave your working copy
is a corrupted state.  (Even worse, it wasn't always immediately
obvious that it was corrupted!)

It's been fixed in /trunk, and it should be out in 1.1.2 soon.
-------------------------

I think I've run into that, or something similar -- if there was a
non-versioned file in a directory that 'svn switch' wanted to delete, it
gave an incomprehensible error message and left the working copy in an
unworkable state.

IIRC, your solution worked -- move the residual directory out of the way and
update its parent.

Dale



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Failed Switch?

[Ben Collins-Sussman <su...@collab.net>]

On Dec 15, 2004, at 10:00 AM, Dale Worley wrote:

> Hjörtur Arnarson wrote:
>> 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.
>
> It seems to me that switch should never leave the working copy in an
> inconsistent state -- at worst, it might have to quit part way through 
> the
> switch, but that would only leave the working copy with mixed 
> revisions, and
> possibly some un-versioned files or directories.
>

There was, until very recently, a nasty bug in 'svn switch' which did 
exactly this:  if you interrupted it, it would leave your working copy 
is a corrupted state.  (Even worse, it wasn't always immediately 
obvious that it was corrupted!)

It's been fixed in /trunk, and it should be out in 1.1.2 soon.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Failed Switch?

[Dale Worley <dw...@pingtel.com>]

Hjörtur Arnarson wrote:
>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.

It seems to me that switch should never leave the working copy in an
inconsistent state -- at worst, it might have to quit part way through the
switch, but that would only leave the working copy with mixed revisions, and
possibly some un-versioned files or directories.

Dale


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Failed Switch?

[Brad Kittenbrink <br...@windwardmark.net>]

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