tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Kolinko <knst.koli...@gmail.com>
Subject Problem running "svn up" on Tomcat site
Date Thu, 14 Jun 2012 14:10:30 GMT
Hi!

I just had a problem with running "svn up" on tomcat.a.o.
I found a solution, but I wonder whether others will experience the same issue.

(..)/tomcat.apache.org$ svn up
svn: E155004: Working copy '(...)/tomcat.apache.org' locked
svn: E200031: attempt to write a readonly database
svn: E200031: attempt to write a readonly database
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

An attempt to run "svn cleanup" failed with the same
svn: E200031: attempt to write a readonly database
svn: E200031: attempt to write a readonly database

Looking at database file,
(..)/tomcat.apache.org$ ls -l .svn
total 9218
-rw-rw-r--    1 mturk     tomcat        3 Jun 14 10:56 entries
-rw-rw-r--    1 mturk     tomcat        3 Jun 14 10:56 format
drwxrwsr-x  258 mturk     tomcat      258 Jun 14 10:53 pristine
drwxrwsr-x    5 kkolinko  tomcat        5 Jun 14 11:03 tmp
-rw-r--r--    1 mturk     tomcat  9332736 Jun 14 11:03 wc.db

I see that wc.db is not writable by group. This is normal for svn on
this system. I did a sample checkout in my home folder and while other
files were "-rw-rw-r--", this one was "-rw-r--r--".

I solved the issue by creating a copy of the file and replacing the original:
An afterthought: maybe instead of "rm -f" I should have renamed it,
postponing deletion until everything is over.
cd .svn
cp wc.db wc.db.kkolinko
rm -f wc.db
mv wc.db.kkolinko wc.db

After that the owner of the file changed to me (kkolinko)
and "svn up" did run successfully, not asking for a cleanup and not
complaining about readonly database.

Note: it is known that copying the wc.db file when it is being
accessed is unsafe.
Before changing anything I noted that the change date of "wc.db" as
shown by "ls -l" was several hours ago.

As the owner of wc.db is now me, I wonder whether others will face the
same issue. So here is a recipe.

Generally, I do not understand why I was facing the issue. As I
mentioned, "wc.db" is normally read-only for the group.

For reference,
$ svn --version
svn, version 1.7.3 (r1242825)
   compiled Feb 26 2012, 21:09:32


Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message