On Feb 7, 2009, at 12:25, Edson Lidorio - Listas wrote:
> Ryan Schmidt escreveu:
>
>> On Feb 6, 2009, at 19:17, Edson Lidorio - Listas wrote:
>>
>>> I am setting up my apache with subversion server is generating
>>> this error below:
>>> Could not open the requested SVN filesystem
>>
>> Generally this means your Apache is not pointing to where your
>> repository exists on disk. Where is the repository on disk -- what
>> is the path that you "svnadmin create"d -- the path that now
>> contains the items README.txt, conf, dav, db, format, hooks, locks?
>
> I have a directory where I create all repository
> in: /srv/svnrepo #home directory
> /srv/svnrepo/meusdoc #repository /srv/svnrepo/teste
> #repository
>
> even so he does not believe, please check my file dav_svn.conf what
> is wrong there?
Then you need "SVNParentPath /srv/svnrepo"
and not "SVNParentPath /srv/svnrepo/meusdoc"
>>> Is attached: dav_svn.conf
>>>
>>>
>>> # dav_svn.conf - Example Subversion/Apache configuration
>>> #
>>> # For details and further options see the Apache user manual and
>>> # the Subversion book.
>>> #
>>> # NOTE: for a setup with multiple vhosts, you will want to do this
>>> # configuration in /etc/apache2/sites-available/*, not here.
>>>
>>> # <Location URL> ... </Location>
>>> # URL controls how the repository appears to the outside world.
>>> # In this example clients access the repository as http://
>>> hostname/svn/
>>> # Note, a literal /svn should NOT exist in your document root.
>>> <Location /svnrepo>
>>> # Uncomment this to enable the repository
>>> DAV svn
>>> # Set this to the path to your repository
>>> #SVNPath /srv/svnrepo
>>> # Alternatively, use SVNParentPath if you have multiple
>>> repositories under
>>> # under a single directory (/var/lib/svn/repo1, /var/lib/svn/
>>> repo2, ...).
>>> # You need either SVNPath and SVNParentPath, but not both.
>>> SVNParentPath /srv/svnrepo/meusdoc
>>> #SVNParentPath /srv/svnrepo/apostila
>>> # Access control is done at 3 levels: (1) Apache
>>> authentication, via
>>> # any of several methods. A "Basic Auth" section is commented out
>>> # below. (2) Apache <Limit> and <LimitExcept>, also commented out
>>> # below. (3) mod_authz_svn is a svn-specific authorization module
>>> # which offers fine-grained read/write access control for paths
>>> # within a repository. (The first two layers are coarse-
>>> grained; you
>>> # can only enable/disable access to an entire repository.)
>>> Note that
>>> # mod_authz_svn is noticeably slower than the other two layers,
>>> so if
>>> # you don't need the fine-grained control, don't configure it.
>>> # Basic Authentication is repository-wide. It is not secure
>>> unless
>>> # you are using https. See the 'htpasswd' command to create and
>>> # manage the password file - and the documentation for the
>>> # 'auth_basic' and 'authn_file' modules, which you will need
>>> for this
>>> # (enable them with 'a2enmod').
>>> AuthType Basic
>>> AuthName "Server Ubuntu - Linux - Repositório"
>>> AuthUserFile /etc/apache2/dav_svn.passwd
>>> # To enable authorization via mod_authz_svn
>>> AuthzSVNAccessFile /etc/apache2/dav_svn.authz
>>> # The following three lines allow anonymous read, but make
>>> # committers authenticate themselves. It requires the
>>> 'authz_user'
>>> # module (enable it with 'a2enmod').
>>> #<LimitExcept GET PROPFIND OPTIONS REPORT>
>>> Require valid-user
>>> #</LimitExcept>
>>> </Location>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1120418
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-07 19:38:29 CET