Folder is locked and I can't unlock it

Question

When I\'m trying to update or commit code from a project it\'s telling me that the folder is locked. When I try to \"release lock\" it says that there\'s nothing to unlock in th

Answer 1

If the file was locked by yourself(same svn account), you can follow these steps:

Right click on the locked file or folder, and select TortoiseSVN->Get lock... , and check on "[] Steal the locks" at the bottom left corner of the dialog, click "OK". If it complete successfully, that's ok. When you right click on the file again, you can see TortoiseSVN->Release lock..., click to unlock.

Answer 2

Solution :

1. Right Click on Project Working Directory.
2. Navigate TortoiseSVN.
3. Navigate To Clean Up.
4. Select Clean up working copy status(make checked mark)
5. Click OK
6. Repeat Step 1 and 2 then navigate to release Lock.
7. Click OK Your project lock get opened.

Answer 3

I was moving a folder up one level and into another folder. My mistake was doing the move from within the parent folder.

Bad example:

pwd -> C:\Repo\ParentDir\
svn move ./DirtoCopy ../AnotherDir

SVN needs to update the parent directory with the deleted folders info.
You have to do it from the common root of the source and destination folders or use full paths.

Good example:

svn move C:\Repo\ParentDir\DirtoCopy C:\Repo\NewLocation

Answer 4

I encountered this problem after these operations:

1. get lock on folder
2. modify files
3. remove files and update folders --> new files downloaded
4. try to commit or release lock

I finally resolved the problem by forcing the lock again : TortoiseSVN --> Get Lock --> check "steal lock" then commit or release lock.

Answer 5

Right click on your Subversion working directory folder, and select TortoiseSVN->Clean Up from the Context Menu. This will recurse it's way through your working directory and cleanup any incomplete actions, remove the local locks (which is different from using Subversion locking of a file in the repository which lets everyone know about the lock).

If that doesn't work, see if you can find the names of the files that were changed, but not yet committed, save them, and redo the checkout.

Answer 6

In addition to David M's answer, while doing cleanup -> check 'break locks' option. This will ensure release of locks. Then do svn update. This worked for me.