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

Partial update possible?

From: Geir Engebakken <geir.engebakken_at_edb.com>
Date: Wed, 4 Feb 2009 15:25:21 +0100

I have a situation where I regularly want to update my WC of a project, but there are some Java packages that I dont want to have in my WC, so after I run svn update I need to physically remove the directories to get the product to compile. Is there any possibility in Svn to configure that some of the directories should be ignored when updating?


-----Original Message-----
From: schmidt_at_isf.rwth-aachen.de [mailto:schmidt_at_isf.rwth-aachen.de]
Sent: 4. februar 2009 15:16
To: users_at_subversion.tigris.org
Subject: SASL and path-based Authorization


I'm trying to set up a Subversion-Server on a Debian Linux system. In my repository there are some folders that should only be changed by one group.
I'm using SASL for authentication and encryption but if I comment in the authz-db line in svnserve.conf I cant commit anything anymore.

Here my conf-files:

anon-access = none
auth-access = write
#password-db = passdb
authz-db = authzdb
realm = MyRealm

use-sasl = true
min-encryption = 128
max-encryption = 256

main = ans
head = art

* =
@main = rw
@head = rw

* =
@main = r
@head = rw

The user ans and art are in the sasldb-File for the realm MyRealm and if I comment out "authz-db" it works properly but without restrictions on different paths...

(I've also tried to use the username in the autzdb but it doesn't work

So, can I use path-based authorization with SASL-user-management, or is it impossible? And if it works, how?

Thank you very much.

With best regards,
Andre Schmidt


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-04 15:27:34 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.