Old talk:Installing SVN

From The Uniform Server Wiki
Revision as of 10:22, 24 November 2010 by Upazixorys (talk | contribs)
Jump to navigation Jump to search


Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly


CLICK HERE



<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">


Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly


CLICK HERE


</div> MrX has reported a problem with SVN working under the /www/ folder...

This article is still under editing...

--Olajide 19:05, 10 Apr 2005 (EDT)

301 Moved Permanently and other errors

This is what happened to me, I'll wait for another person to confirm it before making changes to the wiki.

Olajide decided to use /www/svn instead of /home/svn, which was my choice. I'm sure he has his valid reasons :)

From the free SVN book licensed under Creative Commons:

I can see my repository in a web browser, but &lt;u&gt;svn checkout&lt;/u&gt; gives me an error about 301 Moved Permanently.

&lt;pre&gt; It means your httpd.conf is misconfigured. Usually this error happens when you've defined the Subversion virtual “location” to exist within two different scopes at the same time.

For example, if you've exported a repository as &lt;Location /www/foo&gt;, but you've also set your DocumentRoot to be /www, then you're in trouble. When the request comes in for /www/foo/bar, Apache doesn't know whether to find a real file named /foo/bar within your DocumentRoot, or whether to ask mod_dav_svn to fetch a file /bar from the /www/foo repository. Usually the former case wins, and hence the &quot;Moved Permanently&quot; error.

The solution is to make sure your repository &lt;Location&gt; does not overlap or live within any areas already exported as normal web shares. &lt;/pre&gt;

From what I understand, that means your Repository Root shouldn't be under your Apache DocumentRoot. I decided to try it out for myself. After changing my Repository Root into /www/svn. I got this error while trying to commit: &lt;pre&gt;&lt;nowiki&gt; D:\Misc\SVN\testbdb&gt;svn commit --message &quot;More Test&quot; svn: Commit failed (details follow): svn: OPTIONS request failed on '/svn/testbdb' svn: OPTIONS of '/svn/testbdb': 301 Moved Permanently (http://localhost) &lt;/nowiki&gt;&lt;/pre&gt;

I moved changed my Repository Root back to /home/svn and tried again. This is what I got: &lt;pre&gt;&lt;nowiki&gt; D:\Misc\SVN\testbdb&gt;svn commit --message &quot;New Files :D&quot; Adding 123.txt Adding New.txt Transmitting file data .. Committed revision 6. &lt;/nowiki&gt;&lt;/pre&gt;

Other than that, I get a bunch of errors like these every time I access my repository: &lt;pre&gt; [Sat Apr 09 12:33:27 2005] [error] A subtree cannot specify a different DAV provider than its parent. [Sat Apr 09 12:33:27 2005] [error] A subtree cannot specify a different DAV provider than its parent. [Sat Apr 09 12:33:28 2005] [error] A subtree cannot specify a different DAV provider than its parent. &lt;/pre&gt; My current guess is that, it has something to do with activating Dav in /www

--MrX

Finalization

We have concluded and it seems MrX Won! To run SVN, you now have to create a /svn folder in the Uniform Server SUBST Drive. :)

--Olajide 14:07, 11 Apr 2005 (EDT)