Reputation: 135
Help me, please, with an issue:
build@subversion:~> find /home/build/cruise-work/cruise-checkout/30.0/ | grep rep-cache.db
build@subversion:~> cd /home/build/cruise-work/cruise-checkout/30.0/
build@subversion:~/cruise-work/cruise-checkout/30.0> svn cleanup
svn: E200031: sqlite[S8]: attempt to write a readonly database
svn: E200031: Additional errors:
svn: E200031: sqlite[S8]: attempt to write a readonly database
build@subversion:~/cruise-work/cruise-checkout/30.0>
EDIT1:
build@subversion:~/cruise-work/cruise-checkout/30.0> chmod g+w rep-cache.db chmod: cannot access `rep-cache.db': No such file or directory
EDIT2:
I haven't the rep-cache.db file at all:
> sudo find / | grep rep-cache.db root's password:
> /usr/src/subversion-1.8.11/subversion/libsvn_fs_fs/rep-cache-db.sql
> /usr/src/subversion-1.8.11/subversion/libsvn_fs_fs/rep-cache-db.h
Upvotes: 4
Views: 10610
Reputation: 2466
Things seemed to get in a mess for me after I have been recursively changing permissions on directories and had given ownership to another user. I am assuming that the .svn directories now belonged to that other user and I did not have permission to alter them. Using sudo
, just for the cleanup, solved the problem.
sudo svn cleanup
Upvotes: 1
Reputation: 3
Often this issues happens because you are not running svn commands as super user. So just add sudo to the commands and try that.
Upvotes: 0
Reputation: 2260
this is caused by wrong permissions on a file on the SVN server.
The file “rep-cache.db” will most likely have wrong permissions like the group not having write access to the file.
A simple chmod g+w on the file will be enough for the error message not appearing again.
Upvotes: 2