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

RE: One repository for all company projects, permissions problem.

From: Geir Engebakken <geir.engebakken_at_edb.com>
Date: Tue, 10 Feb 2009 12:31:11 +0100

Good question, I asked the same on the list way back, but I did not get any clear answer to this. I ended up doing it this way :

[repos:/test/test2]
@admin = rw
@test2 = rw
~test2 =

The notation ~test2 means "all users not in test2 group"

This seems to work the way we want.

Geir

________________________________
From: Vladimir Bukreev [mailto:VBukreev_at_it-assist.ru]
Sent: 9. februar 2009 13:29
To: users_at_subversion.tigris.org
Subject: One repository for all company projects, permissions problem.

I have a repository configured with no access (even read) to it's root.
Developers only have rw access to the subfolders, like this:
[/noaccesshere/accessible_project]
Dev = rw

And I have a problem, when developer wants to create a branch inside allowed part of the source tree,
Like copy accessible_project/trunk to accessible_project/tag/beta1
TortoiseSVN returns error :
Server sent unexpected return value (403 Forbidden) in response to PROPFIND request for '/noaccesshere'

Is there a way to fix it without splittion one repo into a lot of different small repos for each project?
Or without setting specific denies for every other project, each developer should not have access to?

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1133729

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-10 15:38:55 CET

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