tags:

views:

1111

answers:

3

What would cause the "SVN Move versioned files here" command with Tortoise SVN to fail with the error "Unable to lock '', Please execute cleanup command", even after having executed the cleanup command?

+1  A: 

I've encountered this before - always in subdirectories of a directory that itself is under source control. If this is the case, please try svn cleanup in the parent of the current directory, or in the parent of that as well, etc - i.e., try it in the highest order parent you can find that is under source control.

Mihai Limbășan
Thanks. No luck with that. I found the TortoiseSVN mailing list. Will try there.
AaronLS
Sorry to hear that - was worth a shot...
Mihai Limbășan
If all else fails, sometimes deleting the Working copy and checking out again helps. There are a few weird problems Subversion can have locally. This is only an option if you don't have local changes, though :)
Joey
I wish I could upvote comments. Johannes, can you make that into an answer?
Mihai Limbășan
That's actually the answer I got on the tortoise mailing list :)
AaronLS
+1  A: 

I've had problems with the Tortoise move facility too (apart from it being difficult to accomplish with a touchpad) and have switched to using the command line svn move command when I need to move something.

Edit: Tortoise doesn't come with a command-line client, so I use that from www.sliksvn.com.

anon
What is the easiest way to run the svn command line? Is that an option through TortoiseSVN? (I thought it was but can't find it, maybe thinking of TortoiseCVS) No dice on finding anything int he manual.
AaronLS
There is another at Collab.net: http://www.open.collab.net/downloads/subversion/ Download the Command Line client
MatthieuF
A: 

I marked Neil's answer as correct, as this is essentially what led me to a workaround. The move command actually failed as well, which indicated the problem was not with ToirtoiseSVN, but actually with SVN itself. I deleted the workspace and re-checked out the repository. However there were still problems with the folder, so I ultimately had to delete a few folders in the repository itself, and re-commit them before the problem went away.

AaronLS