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

Re: access denied - but shouldnt be?

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-09-06 12:56:53 CEST

On 9/5/06, will wade <willwade@gmail.com> wrote:
> Hi there
> Apologies if this is really obvious. I will try and explain my problem
> succinctly
> Imagine two projects (actually more than two)
>
> /usr/local/svn/project_a
> /usr/local/svn/project_b
>
> Both have a svnserve.conf file exactly the same:
>
> password-db = /usr/local/svn_conf/passwd_svn.txt
> authz-db = /usr/local/svn_conf/user_access_svn.txt
> realm = projects
>
> passwd_svn.txt:
>
> [users]
> will = test
> bob = test
> george = test
>
> user_access_svn.txt:
>
> [/]
> * = r
>
> [project_a:/usr/local/project_a]
> @developers = rw
> @everyone = r

The path you specify in the access rule isn't the filesystem path to
the repository. It should be a path *within* the repository. You've
granted the world read access to the repository, but you haven't
granted anyone write access.

If /usr/local/project_a isn't the repository itself for project_a, but
instead is a path in the repository pointing to a directory that
represents project_a, then you need to drop project_a: in front of the
path.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 6 12:58:41 2006

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