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

Re: commits not working with SVNParentPath

From: Michael Bussmann <bus_at_mb-net.net>
Date: 2004-06-28 14:29:43 CEST

Hi,

[ References and in-reply-to headers have been reconstructed manually ]

On 2004-02-19 Eugene Eric Kim <eekim@blueoxen.org> reported some problems
with subversion (0.37) when using the SVNParentPath-directive in apache
2.0.48. A (imho) similar problem has been reported as issue 1934.

I couldn't reproduce this problem in my production subversion repository
yet using "commit", but I got the very same response when I tried to create
a tag. Setting up a test repository I could even reproduce the problem
Eugene had:

| [Mon Jun 28 13:13:28 2004] [info] [client 128.7.27.131] Access granted: 'bus' CHECKOUT testrepo:/
| [Mon Jun 28 13:13:28 2004] [info] [client 128.7.27.131] Access granted: 'bus' PROPFIND testrepo:/t1
| [Mon Jun 28 13:13:28 2004] [info] [client 128.7.27.131] Access granted: 'bus' GET error:/HTTP_NOT_FOUND.html.var
| [Mon Jun 28 13:13:28 2004] [error] [client 128.7.27.131] (20014)Error string not specified yet: Can't open file '/home/svn/error/format': No such file or directory
| [Mon Jun 28 13:13:28 2004] [error] [client 128.7.27.131] Could not fetch resource information. [500, #0]
| [Mon Jun 28 13:13:28 2004] [error] [client 128.7.27.131] Could not open the requested SVN filesystem [500, #2]
| [Mon Jun 28 13:13:28 2004] [error] [client 128.7.27.131] (7)Argument list too long: Could not open the requested SVN filesystem [500, #2]
| [Mon Jun 28 13:13:29 2004] [info] [client 128.7.27.131] Access granted: 'bus' DELETE testrepo:

(Note I'm using subversion 1.0.5 on apache 2.0.49)

Now I think I found a solution (or a workaround that doesn't require you to
change the <Location> directive to something other than /, if there is at
least one other virtual host)

It seems svn asks the server for a non-existant file (t1 in my case), so
apache answers with a redirection to an error file (/error/blah). However,
since everything within / should be considered a potential SVN repository
(Location /), the following request for the error document is interepreted
as a svn request.

I got around this by simply adding a redirection for error documents.

| <VirtualHost ...>
| ...
| CustomLog /var/log/apache2/svn.log combined
| RedirectMatch permanent ^/error http://www.mb-net.net/error
|
| <Location />
| DAV svn
| SVNParentPath /home/svn
| ...
| </Location>
| </VirtualHost>

Of course, http://www.mb-net.net/error should be replaced with another
(virtual) host on the server :-)

It's not an elegant solution but it worked for me.

HTH

Cheers,
MB

-- 
Michael Bussmann <bus@mb-net.net>
BOFH excuse #296:
The hardware bus needs a new token.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 28 20:37:40 2004

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