What should I do when 'svn cleanup' fails?

Question

I have a lot of changes in a working folder, and something screwed up trying to do an update.

Now when I issue an \'svn cleanup\' I get:

>svn clea         


        

Answer 1

$ ls -la .svn
$ rm -f .svn/lock

Then

$ svn update

Hope it helps

Answer 2

Subclipse gets confused by Windows' truly diabolical locking behaviour. Unlocker is your friend. This can find locked files and forcibly release the locks.

Answer 3

If all else fails:

1. Check out into a new folder.
2. Copy your modified files over.
3. Check back in.
4. Zip the old folder up somewhere (you never know + paranoia is good) before deleting it and using the new one.

Answer 4

It's possible that you have a problem with two filenames differing only by uppercase. If you ran into this problem, creating another working copy directory does not solve the problem.

Current Windows (i.e. crappy) filesystems simply do not grok the difference between Filename and FILEname. You have two possible fixes:

1. Check out at platform with a real filesystem (Unix-based), rename the file, and commit changes.
2. When you are stocked to Windows you can rename files in the Eclipse SVN repository browser which does recognise the difference and rename the file there.
3. You can rename the problematic files also remotely from any command-line SVN client using svn rename -m "broken filename case" http://server/repo/FILEname http://server/repo/filename

Answer 5

The latest verion (I'm using 1.9.5) solve this problem by adding an option of "Break locks" on the clean up menu. Just make sure this check box is selected when doing clean up.

Answer 6

I ran into that too lately. The trick for me was after selecting "Clean up", in the popup options dialog, check "Break Locks", and then "OK". It cleaned up successfully for me.