[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

301 Moved Permanently

From: Matt Duffy <mattduffy_at_gmail.com>
Date: 2006-09-15 23:45:38 CEST

Hello,
I know there are a bunch of posts about this type of error, but all
the ones I have seen are pretty old and don't seem to be on par with
the version of svn I am using, so I hope you'll bear with me for yet
another thread about 301 errors.

Some background-
Mac OS X 10.4 Server
Apache/2.0.55
svn 1.3.1
neon 0.25.5

SubVersion is set up with a repository for each project. These
repositories were originally created on a different machine running
Mandrake Linux and svn 1.2.x. I had to move them off that machine
because we were upgrading our hardware to a new Xserve G5.

On the old machine, the repositories where created by a fellow long
since gone from the company. They were a mix of individual
repositories and a main repository with a handful of projects jumbled
together.

After I moved them over to the new server I created this entry in my httpd.conf:

<VirtualHost *:80>
     ServerName svn.example.com
     ServerAlias svn
     DocumentRoot /Volumes/Vsites/SVNRepository

     <Directory /Volumes/Vsites/SVNRepository>
         DirectoryIndex index.php
         Options Indexes
         AllowOverride None
         Order allow,deny
         Allow from all
     </Directory>

     <Location />
         DAV svn
         SVNParentPath /Volumes/Vsites/SVNRepository

         AuthType Basic
         AuthName "SF developers"
         AuthuserFile /Volumes/Vsites/SVNRepository/svn_user_auth.htacces
         Satisfy Any
         Require valid-users
     </Location>

     ErrorLog /var/opt/apache2/logs/svn/svn-error_log
     CustomLog /var/opt/apache2/logs/svn/svn-access_log common
 </VirtualHost>

For the most part it seems to work. I can access the repositories via
all three protocols (http, svn and svn+ssh).

The problem that is really driving me crazy is the 301 issue. It
happens when I want to do things like copy the trunk to a new branch.
Here's an example of the error:

[matt@cebus trunk] svn copy \
> http://svn/Clients/trunk \
> http://svn/Clients/branches/admin_remove_from_view
subversion/libsvn_ra_dav/util.c:780: (apr_err=175002)
svn: PROPFIND request failed on '/Clients'
subversion/libsvn_ra_dav/util.c:295: (apr_err=175002)
svn: PROPFIND of '/Clients': 301 Moved Permanently (http://svn)

This also confuses me. I would expect to get the branches, tags,
trunk listing with this, but instead get this error:

[matt_at_cebus trunk] svn list http://svn/Clients
subversion/libsvn_ra_dav/util.c:780: (apr_err=175002)
svn: PROPFIND request failed on '/Clients'
subversion/libsvn_ra_dav/util.c:295: (apr_err=175002)
svn: PROPFIND of '/Clients': 301 Moved Permanently (http://svn)

But to show that svn is working in other respects, here is the working
copy info on the same project:

[matt@cebus trunk] svn info
Path: .
URL: http://svn/Clients/trunk
Repository UUID: 6cf89ca6-e603-0410-ad49-f62335a9b3e0
Revision: 276
Node Kind: directory
Schedule: normal
Last Changed Author: matt
Last Changed Rev: 275
Last Changed Date: 2006-09-14 21:26:17 -0700 (Thu, 14 Sep 2006)

This inability to create branches is really starting to impede our
development. Now, I readily admit that our svn installation is
probably pretty messed up. Some repositories where created without
the normal layout (branches, tags, trunk) and then manually massaged
into that format... but I can't really explain why or how that was
done. There is quite a lot of content in svn and I am worried that
its only going to get harder to deal with as time goes on.

Any help you can provide would be amazingly awesome.

Cheers,
Matt Duffy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 16 01:46:25 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.