On Thursday 19 February 2004 04:35, Eugene Eric Kim wrote:
> I recently installed Subversion 0.37 on Apache 2.0.48, and am having
> trouble getting it to work properly when using SVNParentPath. After
> doing some extensive experiments, I did a Google search and found a
> similar report, but no responses, so I thought I'd prod again to see
> if I could get some help:
> When I configure Subversion using SVNPath to specify the absolute path
> of the repository, everything works beautifully. However, when I
> switched to SVNParentPath, things go awry. Checkout works okay, but
> commits fail with the following message:
> svn: Commit failed (details follow):
> Could not open the requested SVN filesystem
What was your command line to checkout the repository? I'm assumming had
setup http://my.server.com/ as the repository itself (using SVNPath). The
you changed the configuration to use SVNParentPath? If so, then the location
of the repository has moved. Assuming the name of the repo was test, the new
URL should be http://my.server.com/test. You need to use svn switch
--relocate to rewrite the URL for the working copy.
> The error_log reports:
> [Thu Feb 19 01:15:37 2004] [error] [client 22.214.171.124] (20014)Error
> string not specified yet: Can't open file '/data/svn/repos/error/format':
> No such file or directory [Thu Feb 19 01:15:37 2004] [error] [client
> 126.96.36.199] Could not fetch resource information. [500, #0] [Thu Feb
> 19 01:15:37 2004] [error] [client 188.8.131.52] Could not open the
> requested SVN filesystem [500, #2] [Thu Feb 19 01:15:37 2004] [error]
> [client 184.108.40.206] (7)Argument list too long: Could not open the
> requested SVN filesystem [500, #2]
> Also, when I try a "make check BASE_URL=..." to run the tests, all of
> the tests starting with basic-tests.py fail.
> What I find very strange about the error message is the first line;
> Subversion is trying to access a file in the parent path that doesn't
> exist. This same behavior was reported in the other message I cited
If you changed the directive and nothing else, then I'd expect to see this as
an error. Your working copy still thinks the repository is in the old
> Configuration is as follows:
> * Parent path is /data/svn/repos. I tried both leaving this directory
> alone, and also creating a repository in it using svnadmin; both
> resulted in the same error. The repository below is /data/svn/test.
> I created this using svnadmin.
Uh, do you mean the repository below is '/data/svn/repos/test'?
> * Apache config is:
> ErrorLog /data/svn/logs/error_log
> CustomLog /data/svn/logs/access_log combined
> <Location />
> DAV svn
> SVNParentPath /data/svn/repos
> SetOutputFilter DEFLATE
> I actually have some auth stuff there, but I removed it for the sake
> of testing.
> Suggestions? Thanks.
If what I've said doesn't provide any insight, let me know. I've currently
got several repositories hosted at home using SVNParentPath and 16 at work...
none of which have ever had problems in this configuration.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Feb 19 10:57:05 2004