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
To unlock a file in your working copy from command prompt that is currently locked by another user, use --force
option.
$ svn unlock --force tree.jpg
Using svn command line to unlock the local folders, just use svn cleanup
.
Before:
# svn commit -m "fixing #1234"
# svn st
# svn cleanup
After:
# svn st
# svn commit -m "fixing #1234"
I had this happen after having Tortoise get corrupted and crash while trying to update folders. I ended up re-installing Tortoise, but the ghost lock was still present. From there I had to delete the folder and do a new checkout. Obviously I got really lucky that I didn't have any new changes to commit at the time. Anyhow, not great news, and if anyone has a better solution I'd love to hear it myself. Even using "Break Lock" ie unlock with the force option did not change anything.
I had this problem where I couldn't unlock a file from the client side. I decided to go to the sever side which was much simpler.
On SVN Server:
Locate locks
svnadmin lslocks /root/of/repo
(in my case it was var/www/svn/[name of Company])
You can add a specific path to this by svnadmin lslocks /root/of/repo "path/to/file"
Remove lock
svnadmin rmlocks /root/of/repo “path/to/file”
That's it!
I was able to resolve this issue on my machine by renaming folders to make the folder path smaller.