ansaurus

Question

Release locks in Subversion recursively

Answer 1

A:

Ok I got it.

What I did was I checked out a working copy.
Then went in explorer menu, TortoiseSVN -> Check for modifications...
Clicked on Check repository button
Select All the files, right click and select the break lock option.
Delete the working copy and the one in repository. Voila! :)

Regards

ShiVik 2010-07-01 06:34:41

Answer 2

+1 A:

From the advance locking section

$ svn status -u
M              23   bar.c
M    O         32   raisin.jpg
       *       72   foo.h
Status against revision:     105
$ svn unlock raisin.jpg
svn: 'raisin.jpg' is not locked in this working copy

That simply means the file is not locked in your current working directory , but if it is still locked at the repository level, you can force the unlock ("breaking the lock")

$ svn unlock http://svn.example.com/repos/project/raisin.jpg
svn: Unlock request failed: 403 Forbidden (http://svn.example.com)
$ svn unlock --force http://svn.example.com/repos/project/raisin.jpg
'raisin.jpg' unlocked.

(which is what you did through the TortoiseSVN GUI)

VonC 2010-07-01 06:41:10

I also did what you told in the repository, but if I had to do it one file each, it would have taken me ages. Since my limited knowledge with cli didn't allow me to find a recursive command, that is why it took me a little more time. :)

ShiVik 2010-07-01 06:53:02

@ShiVik: true there is no recursive option, but you can find some way to script it: http://old.nabble.com/recursive-find-locks-unlock-in-repository-td25010776.html `svnadmin lslocks <path_to_repo> |grep -B2 Owner |grep Path |sed "s/Path: \///" | xargs svn unlock --force` for example. But the TortoiseSVN GUI is a good solution too.

VonC 2010-07-01 07:10:00

ansaurus

tags:

views:

answers:

Release locks in Subversion recursively

related questions