TortoiseSVN error “Working copy locked” “sqlite: a

问题:

A working copy of an app is returning the described error when trying to Update.

Can this error be caused by having insufficient permissions to write to the folder (or some of the files within it)?

I've tried the "Release Lock" function and Tortoise tells me there are no locks.

回答1:

Working copies on shares frequently cause problems (including/especially with permissions) - as a result, it is not a recommended configuration. There actually was a bug in quite a few releases of Samba that was triggered by SVN 1.5 or 1.6 which caused a number of issues like this. It can be worked around with a change to the Samba configuration - but this may not resolve all of your issues. Best practice is to not do what you are doing - only operate on WCs locally, not via shares

回答2:

I got that very error with TortoiseSVN under Windows. Apparently, the .svn folder has a small SQLite database file, which, if you don't have write access to, will cause that error.

As I was using TortoiseSVN through the windows shell (the right-click) menu, to work around it I ran the windows explorer I used to navigate to the folder as administrator and everything worked fine.

Another solution, of course, would be to give write rights to the user you are trying to use TortoiseSVN with.

回答3:

While not related to tortoise, I just had this error because I ran svn update as root (forgot I was su'd on a Linux box) and got a conflict.

Fixing it was as simple as doing a chown -R user .svn and then chmod ug=rwx on the file wc.db in the .svn folder.

回答4:

This error can occur if write access is not available for your group to the rep-cache.db file in your repository on the SVN server. You'll need access to the SVN server or get someone who has access.

Search for the rep-cache.db file:

find / | grep rep-cache.db

Go to the db subdirectory under the repository that you are working with and type the following:

chmod g+w rep-cache.db

Typically the group has only read-only access when this error occurs. This will give the group read/write, which should stop the error from occurring.

回答5:

I got this error, because I moved my repositories to a new server. The main folder was created by root. As a result, there was an inconsistance of rights between restored files and newly created files. chown -R on the main folder solved the problem.

回答6:

I got this error recently and it was because I had logged into my development environment using the wrong user account. I had set the project up on a development VM using the local Administrator account. I got this error when I logged in user my personal account who was not a local Windows Admin. So in my case it was due to Windows permissions.

回答7:

I got the same error when copying whole SVN repo to another location. When I checked Windows permissions, everything seemed fine. I reapplied Windows permissions and all of a sudden Windows applied permissions and from then on everything is working fine.

回答8:

Had this on windows 7 system, after waiting 10 mins the SVN update was available without problems. Maybe a problem during Tortoise startup.

回答9:

For Ubuntu users

when you setup project on a public directory such as home don't use sudo on it. ex: sudo mkdir folderName use mkdir folderName or create it manually.

when you created using sudo you get the folder as locked.(check image with and without sudo)

---

As well don't use sudo svn co http://path/to/trunk/ ./ use without sudo

like this

svn co http://path/to/trunk/ ./

---

Just got this error and solved well