I saw somewhere on the bitbucket site where this can be caused by the repo being located on an older shard without svn commit support. Is this a per-account thing or a per-repo thing? I don't really care about the existing repo (it's just a test), but if it's per-account, please move me to a svn-capable shard.

Thanks!

Command output:

{{

{\\ #!python rks@atom:~/tmp/trunk$ svn status\\ M README rks@atom:~/tmp/trunk$ svn commit\\ svn: Commit failed (details follow):\\ svn: At least one property change failed; repository is unchanged\\ svn: Server sent unexpected return value (500 Internal Server Error) in response to PROPPATCH request for '/rks1222/test/%21svn/wrk/f8ca4615-b0a5-4e49-a8ed-99bd97cb51a7/'\\ svn: Your commit message was left in a temporary file:\\ svn: '/home/rks/tmp/trunk/svn-commit.tmp' }

}}