configuration with SVNPath works, with SVNParentPath not :(

[Goddchen]

hi, i have a strange problem i'm now trying to set up svn on my vserver for a week and can't get it to work.

here is the situation:

i created a directory /usr/local/svns
in there i created a svn repo "test-svn"

so now i insert SVNPath /usr/local/svns/test-svn in my http.conf i can access the svn via http
when i change that line to SVNParentPath /usr/local/svns i can only check the svn out but when i try to commit something i get:

[kama]

Hi,

how does your Apache Config (<location>-Area) looks like?
and what about your svnaccess.conf ?

Kind Regards.
Karl Heinz Marbaise
_________________
SoftwareEntwicklung Beratung Schulung
Web: www.soebes.de
Mail: info@soebes.de
Software Configuration Management Wiki
Subversion Repository Search Engine (SupoSE)

[Goddchen]

ok, here is an update of the situation

i created a repo namen "error" under /usr/local/svns and everything works fine dunno why, and i don't think that this is a good solution so i would realy like to solve the problem.

here is my httpd.conf part...

[andre]

I'm having the exact same problem. I have essentially duplicated this 'bug'.

Configuring location to use svnparentpath allows me to checkout, commit a change to an existing file, but not commit something new that has been added.

svn: Commit failed (details follow):
svn: PROPFIND request failed on '/test/trunk/test2.txt'
svn: Could not open the requested SVN filesystem

Location directive looks like...
<Location / >
DAV svn
# SVNPath /data/svn/test
SVNParentPath /data/svn

# Authorization BASIC
AuthType Basic
AuthName "svn"
AuthUserFile /foo/authfile
Require valid-user

</Location>


Configuring location to use svnpath allows me to do everything including checking in a newly added file.

Has anyone else experienced this and/or figured it out?

andre

[andre]

First - what I did wrong:
I was setting this all up in a virtual host

<VirtualHost xxx.xxx.xxx.xxx:443>
ServerName svn.example.com
<Location / >
Dav svn
SVNParentPath /data/svn/
#other
#stuff
</Location>
</VirtualHost>

And I was attempting to work on http://svn.example.com/somerepo/

Checking out works. So does committing changes to existing docs... but when trying to add something new - the commit would fail (as per my previous message).

The problem:
For reasons I do not completely understand <Location / > won't work.
(I'm sure some apache directives / mod_dav expert may be able to explain why).

The solution:
It appears YOU MUST provide a location 'path' that is something other than root ("/"). e.g. <Location /foo>. And therefore you must request from http://svn.example.com/foo/somerepo.

With all that in mind the new httpd.conf would look like this

<VirtualHost xxx.xxx.xxx.xxx:443>
ServerName svn.example.com
<Location /foo >
Dav svn
SVNParentPath /data/svn/
#other
#stuff
</Location>
</VirtualHost>

svn commit https://svn.example.com/foo/somerepo will work.

Of course this configuration is precisely what the documentation says to do. But, trying to be clever and have cleaner urls I thought I could cheat and not have to supply a trailing argument in my URL and specify location to be the root of svn.example.com. Apparently a bad idea.

andre

[Goddchen]

hm cool, you solved it but i will leave it the way it's now with the "error"-repository because i realy want to have this clean url.