Voltechs

...and I don't mean "whoa". The first one, I experienced was recieving this message upon an attempted svn ci (svn checkin):

codesvn: Commit failed (details follow):
svn: Network connection closed unexpectedly

I'm not sure how I fixed it, but what I did do is delete some of my keys from ~/.ssh/known_hosts and copy over my ~/.subversion/ directory from a backup. (I'd recently done a clean install of OS X 10.6 so I didn't have some of those hidden files like that.)

The second error I got (once I seemed to have fixed the first one) was a permissions error:

codesvn: Can't open file 'experiments/.svn/lock': Permission denied

Seems pretty straight forward, but its easy to overlook the fact that it is actually talking about the file .svn/lock. Solution?

# First things first, make sure your entire svn checkout has the correct permissions. I like to give the owner (me) full access, the group (staff) read and execute status (so admins can "execute", that is, open directories, and read the files, but can't make changes) and others no access at all. This results in a 750 rwx code. To accomplish this, open a shell (Terminal or the like) and type
codesudo chmod -R /path/to/your/repository
# Then, to fix ownership, type (obviously replacing 'yourusername' with your actual username. If you don't know it, type 'whoami' in the terminal:
codesudo chown -R yourusername:staff /path/to/your/repository

And that should do it. Give your checkin or update a try.