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

Re: CLI SVN LOG E220001: Item not readable

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 2 Sep 2016 17:37:34 +0000

Billy Buzzard wrote on Fri, Sep 02, 2016 at 15:28:11 +0000:
> What do I do if I have a group of trusted developers who are allowed
> to see all projects and another group of non-so-trusted developers who
> are only allowed to see their project?

This:

    [groups]
    trusted = ...
    untrusted = ...
    
    [/]
    @trusted = rw
    @untrusted =
    
    [/projects/foo]
    @untrusted = rw
    
    [/projects/baz]
    @untrusted = rw

Now if /projects/bar exists, people in @untrusted [who aren't also in
@trusted] won't see it.

You don't need $anonymous since members of both @dev1 and @dev2 are
authenticated.

Cheers,

Daniel

> My authz file looks like this:
>
> [groups]
> dev1 = billy, chuck
> dev2 = jim, bob
>
> [/]
> $anonymous =
> @dev1 = rw
>
> [/Project2]
> @dev2 = rw
>
> If I use this authz as is then the svn log command does not work. If I give everyone read access it works, but now the non-so-trusted developers can see projects that I do not want them to see.
>
> I using svn, version 1.6.11 (r934486) on a 64-bit Linux machine. I am executing the svn log command from a 64 bit Windows 7 machine. I am not using httpd.
Received on 2016-09-02 19:38:17 CEST

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.