TortoiseSVN error "Working copy locked" "sqlite: attempt to write read-only database" - Could this be caused by incorrect permissions?

Question

A working copy of the application returns the described error when trying to update.

Could this error be caused by insufficient write permissions to the folder (or some of the files inside it)?

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

Answer 1

Working copies of stocks often cause problems (including / especially with permissions) - as a result, this is not recommended. There was actually a bug in several releases of Samba that were caused by SVN 1.5 or 1.6, which caused a number of problems like this. You can get around it by changing your Samba configuration - but this may not solve all your problems. The best practice is not to do what you are doing - only work with WCs locally and not with shares

Answer 2

I have such an error with TortoiseSVN on Windows. Apparently, the .svn folder has a small SQLite database file, which if you do not have write access will result in this error.

Since I used TortoiseSVN through the Windows shell menu (right-click) to get around it, I launched Windows Explorer . I used to go to the folder as an administrator and everything worked fine.

Another solution, of course, would be to grant write access to the user with whom you are trying to use TortoiseSVN.

Answer 3

Not related to the turtle, I just had this error, because I ran svn update as root (forgot that I was su'd in a Linux box) and got a conflict.

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

Answer 4

This error may occur if write access is not available for your group in the rep-cache.db file in your repository on the SVN server. You will need access to the SVN server or gain access to someone.

Locate the rep-cache.db file:

 find / | grep rep-cache.db 

Go to the db subdirectory in the repository you are working in and enter the following:

 chmod g+w rep-cache.db 

Usually this group has read-only access when this error occurs. This will give the group a read / write that should stop the error.

Answer 5

I got this error because I moved my repositories to a new server. The main folder was created by root. As a result, a mismatch of rights was found between the recovered files and the newly created files. chown -R in the main folder solved the problem.

Answer 6

I recently got this error because I logged into my development environment using the wrong user account. I installed the project on the development virtual machine using the local administrator account. I got this error when I registered a user, a personal account that was not a local Windows administrator. So in my case it was related to Windows permissions.

Answer 7

If it were on Windows 7, after waiting 10 minutes, an SVN update was available without problems. There may be a problem while starting Tortoise.

Answer 8

I got the same error when copying the entire SVN repo to another location. When I checked Windows permissions, everything seemed fine. I reapplied Windows permissions and suddenly applied Windows permissions, and from that moment everything works fine.

Answer 9

For Ubuntu Users

when you set up a project in a public directory such as home , do not use sudo on it. ex: sudo mkdir folderName use mkdir folderName or create it manually.

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

---

Also do not use sudo svn co http://path/to/trunk/ ./ use without sudo

like this

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

---

Just got this error and decided well