title: Weird Subversion permissions issue
body: <p>I'm trying to set up SVN on a CentOS 5 system so that several people can use a repository. </p>
  
  <ul>
  <li>I've created the repository at <code>/var/svnrepository</code>.</li>
  <li>I added a <code>subversion</code> user and group, made that the owner of the repository recursively.</li>
  <li>I set permissions to 775 recursively.</li>
  <li>I ensured that all the system users are in the <code>subversion</code> group.</li>
  </ul>
  
  <p>The problem I'm running into is that when I do a commit, SVN apparently creates a file called <code>db/current</code> and it has my username and group. So say my username is <code>jimbo</code>...</p>
  
  <pre><code>-rwxrwxr-x 1 jimbo      jimbo         11 Dec  2 01:09 current
  </code></pre>
  
  <p>Then after that no one else can check anything out. They get a permission denied error.</p>
  
  <p>There's also a similar issue with a file called <code>db/format</code>.</p>
  
  <pre><code>Can not open file /var/svnrepository/contactdb/trunk/format: Permission denied
  </code></pre>
  
  <p>Has anyone else seen this? Know of a solution?</p>
  
  <p>All repository access is through ssh.</p>
  
  <p>The weird thing is, I've set up SVN on Linux before and never had this problem. I don't know what I'm doing differently this time.</p>