Yesterday, I had a nightmare night after migrating some non-virtualhost sites to virtualhost sites inside Apache2.

Everything was migrated and fully functional until I receive a desperate call from my friend telling me that svn service was not working. I was stranged with that notice, because I had already done some tests in some repositories (commit and checkout).

After better explanations, I realized that only one repository was in trouble:

svn ls http://myhost.com/projectx
svn: Repository moved permanently to 'http://myhost.com/projectx/'; please relocate

What ?!?! Yes, yes, yes !!! Look at the error…a brutal 301 HTTP error code just at my eyes.

Well, the errors logs from Apache didn’t tell me anything useful, just the known error:

"OPTIONS /projectx HTTP/1.1" 301 241 "-" "SVN/1.6.5 (r38866) neon/0.28.6"

I resolved change the name of this directory to projecty and the repository changed back to work miraculously.

After 1/2 hour trying to find any potential mistake in configuration files, I decided to investigate the directories in DocumentRoot and to my surprise what I found…a folder named “projectx“.

So, I decided to read the subversion faq and to me surprise again, look what I found:

http://subversion.apache.org/faq.html#http-301-error

Yeah…this fucking bug made me crazy !!! =P

It’s not possible you have a folder in your DocumentRoot that it has the same name that a repository inside your SVNParentPath…bizarre !!! O_o

Well, I hope you see this post before you have to pass for this error.

And this bug is not treated as a bug…that I think is incredible… unbelievable!!!

For this and others limitations that I have done usage of Git, Mercurial and Bazaar…

SVN is past, centralized repository is past…but this is a history for a future post :)