SVN Error when committing Access denied: 'foobar' MKACTIVITY MYREPO: SVN Error when committing Access denied: 'foobar' MKACTIVITY MYREPO: apache apache

SVN Error when committing Access denied: 'foobar' MKACTIVITY MYREPO:


I've found it!

Ok here's the answer:

What was the problem:

My users check out a Repo in the directory /svn/myDir/MYREPO

Apache knows that he has to translate MYREPO to a lowercase directory so when you check out or do any read operation this was working just fine.

But when the users did try to do the commit operation Apache changessomehow the order of the operations he has to do to fulfill the users request so, first accepts the write operation and tries to write, and then changes to lowercase.

Again, it tries to write to the /svn/myDir/MYREPO, the issue is that:

  • permissions to the repo where set to myrepo and not MYREPO
  • the actual repo is myrepo and not MYREPO

So... MYREPO does not exist! myrepo does. That's why it throws that error:

  • ACCESS DENIED because there is no permission written for MYREPO.
  • And It does recognize the repo in the read way because apache understands what you are asking for and translates.

But for writing first works with it and after that takes a moment to understand what is he doing. And the exception comes previous to the understanding so Apache never get's there.

How to solve it:

This is the simplest thing:

  • Go to the checked out Repo
  • Do a Relocate from
    http://YourServer/svn/myDir/MYREPO
    to
    http://YourServer/svn/myDir/myrepo

My recommendation:

My recommendation for svn-administrators and users from now on, is do

EVERITHING LOWERCASE... sorry, I correct myself:

everything lowercase!


Added to the above solution, please be informed that, prior to Subversion 1.7, Subversion treated repository names and paths in a case-insensitive fashion for the purposes of access control, converting them to lower case internally before comparing them against the contents of your access file. It now does these comparisons case-sensitively. If you upgraded to Subversion 1.7 from an older version, you should review your access files for case correctness.

Source - http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.serverconfig.pathbasedauthz