Support Requests: Browse | Submit New | Admin

[#29548] Commit failed: attempt to write a readonly database

Date:
2012-03-19 13:42
Priority:
3
Submitted By:
Mark Borkum (mib104)
Assigned To:
Tom Copeland (tom)
Category:
existing-svn-repository
State:
Open
Summary:
Commit failed: attempt to write a readonly database

Detailed description
Hi,

Would you please check the "blog3-rails3" SVN repository. 

When I issue an SVN commit, my client claims that the commit was successful, but, then reports that there was an
"attempt to write a readonly database" and exits.

I accessed the files in question using the Web interface. My SVN commit messages are definitely getting through [to
RubyForge] (as the files are updated and the revision counter is incremented.)

My [heavy-handed] fix for this issue has been to tear down my working copy of the repository, SVN checkout a fresh copy,
copy over the updated files and issue a SVN commit [which "succeeds" if you discount ignore the error
message].

Obviously, this approach is not sustainable. 

Any suggestions?

Thanks,
Mark

Add A Comment: Notepad

Please login


Followup

No Followups Have Been Posted

Attached Files:

Name Description Download
No Files Currently Attached

Changes:

No Changes Have Been Made to This Item