It turns out I was trying to create a repository at /path/svn, then use that as a ParentPath. I.e., I was running svnadmin create /path/svn.

The correct way is to create a directory at /path/svn, then you can add additional subdirectories, e.g., /path/svn/repo1, /path/svn/repo2, then run:

svnadmin create /path/svn/repo1
svnadmin create /path/svn/repo2

Then, later, if you need another repository, create another sub-directory and run “svnadmin create” again, with no need to restart Apache.

Sometimes you just need to ask somebody the question to find the answer.

The long and sort is, when using SVNParentPath, you do NOT make the parent path a repository. While that might seem obvious in retrospect, for beginners trying put all this together for the first time, the entire process contains dozens of booby-traps waiting to spring on the unwary and inexperienced. I’ve spent more time on Google over the last week than I care for. You can’t imagine how tired I am of reading on numerous sites to make sure the file permissions are all set correctly. (sigh!)

Your advice works with SVNPath — but I lose the Parent-path functionality.

Indeed, when I make your suggested change, removing the trailing slash, this is exactly the error I receive.

So it appears I have the choice between no trailing slash, and a “moved permanently” error, or with the trailing slash and a “405 Method not allowed” error.

Either way, I’m screwed.