Daniel the configuration is very similar to mine and it only partially works.
Did you test your configuration by using "svn log" from the command line? I
did and it still has the same problem.
D:\projects\foo>svn log svn://myrepo/projects/foo
svn: E220001: Item is not readable
The only way the "svn log" works that I have read about or found is when the
admin adds * = r to the root folder in the authz file.
-----Original Message-----
From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
Sent: Friday, September 02, 2016 12:38 PM
To: Billy Buzzard
Cc: users@subversion.apache.org
Subject: Re: CLI SVN LOG E220001: Item not readable
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.
