[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

failed commit that did not fail

From: Mark Keisler <grimm26_at_gmail.com>
Date: Mon, 28 Feb 2011 16:38:50 -0600

I got this error on a commit because the rep-cache.db file in the
repository had the wrong mode:
....
Transmitting file data
................................................................
.......................................................................................
.......................................................................................
.......................................................................................
.......................................................................................
.......................................................................................
.......................................................................................
............................svn: Commit failed (details follow):
svn: attempt to write a readonly database
svn: attempt to write a readonly database

Clearly, it says the commit failed. So I fixed the permissions in the
repository and tried the commit again:
....
svn: Commit failed (details follow):
svn: File already exists: filesystem '/svnroot/myrepo/db', transaction
'5323-43v', path '/blah/blah/blah'

So I seem to be stuck. I run svn update in my working copy and
nothing seems to happen. svn status still shows all my added files
staged and ready to be committed. the commit did not fail correctly.
So, what do I do to get out of this besides dumping up to right before
the current rev and reloading the repository? Also, is this a known
issue or shall I file a bug?

Subversion command-line client, version 1.6.15.
server is running 1.6.13, both are Linux.

--
Mark
Received on 2011-02-28 23:39:22 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.