SVN IS MAD.
Sorry, SVN and HTTPD team up to drive people crazy.
I just came across two (or maybe three) of their misdoing in my effort to setup SVN on http://repos.nitt.edu
- First, with this nitt.edu.conf in /etc/httpd/conf.d directory :I found this article : http://ynniv.com/blog/2005/12/troubling-svn-error.html
I got an error
<pre><span style="color:#ff0000;">RA layer request failed
svn: PROPFIND request failed on '/pragyan'
svn: PROPFIND of '/pragyan': 302 Found (http://repos.nitt.edu)</span>
It said that the error occurs when some cms meddles with the way non existent file message (404) is shown. This,… was my case. (Thanks to my Praygan CMS). So then I changed my document root to /var/www/svn.
Article that helped me in this grave time of need was : http://subversion.tigris.org/faq.html#http-301-error
It said that the error occurs because, when configuring SVN to work with httpd, the virtualhost document root shouldn’t contain the repository location (or httpd gets confused or something). My repos location was /var/www/svn/pragyan (which was within Document root). I simply changed the DocumentRoot to /var/www/svn/DocumentRoot and all started working well again.