I tried both setting up SVNPath as /sas/svnrepos/crma
and SVNParentPath as /sas/svnrepos
it does not work. I am getting exactly the same error as before.
I am looking into changing locale. I found AddDefaultCharset line in
apache config file.
I change it to
Unfortunately, when restarting server UTF8 charset can not be loaded. I
think i am missing something
but do not know what. I will keep browsing for more info on locale change.
On Feb 15, 2006, at 13:45, firstname.lastname@example.org wrote:
>>> <Location /repos>
>>> DAV svn
>>> SVNPath /sas/svnrepos
>>> THere is only one repository in sas/svnrepos = crma
>>> Tried to check out repository over the network with
>>> Svn co http://hostname/repos
>>> Svn co http://hostname/repos/crma/trunk (crma - project name)
>>> Does not work: getting following error
>>> svn: PROPFIND request failed on '/repos'
>>> svn: Could not open the requested SVN filesystem
>> I believe you either need to use
>> SVNParentPath /sas/svnrepos
>> then use URLs like http://hostname/repos/crma/turnk/...
>> OR use
>> SVNPath /sas/svnrepos/crma
>> Then use URLs like http://hostname/repos/trunk/...
> Thanks Paul for your response. I tried both solutions.
> Unfortunately, neither worked.
Paul is correct. If you use SVNPath, it must point to the repository.
If you use SVNParentPath, it must point to the directory containing
any number of repositories. So either "SVNPath /sas/svnrepos/crma" or
"SVNParentPath /sas/svnrepos" but not "SVNPath /sas/svnrepos" as you
have it now.
Now, it's possible that, after you've made that change, there are
still other problems. Did changing the above change the error message
or log output at all?
>>> This is the log:
>>> [Tue Feb 14 15:16:02 2006] [notice] caught SIGTERM, shutting down
>>> [Tue Feb 14 15:16:15 2006] [notice] Digest: generating secret for
>>> digest authentication ...
>>> [Tue Feb 14 15:16:15 2006] [notice] Digest: done
>>> [Tue Feb 14 15:16:16 2006] [notice] Apache/2.0.54 (Unix) PHP/
>>> 5.0.3 DAV/2 SVN/1.2.3 mod_perl/2.0.1
>>> Perl/v5.8.7 configured -- resuming normal operations
>>> [Tue Feb 14 15:17:15 2006] [error] [client XXX.XXX.XXX.XXX]
>>> (20014)Error string not specified yet
>>> : Can't create a character converter from 'UTF-8' to native encoding
This UTF-8-to-native-encoding error message is probably important. I
can only find that exact message once in Google and that page didn't
help me. I do recall this recent conversation:
There it was discovered that, nonintuitively, it was necessary to set
the locale *on the server* to a UTF-8 locale. Although the error
message in that thread is different from the one you see, perhaps the
same solution will help? I'm not sure how to set the locale for
Received on Wed Feb 15 19:31:06 2006