Hi!
That's not a bug, everything works correct!
Permissions which are set to the directory ("defined" permissions)
have a priority over the "inherited" permissions in Subversion.
Otherwise it would be impossible to limit access to subdirectories for
particular users.
We'll consider the implementation of the UI to show effective rights
in the future versions of VisualSVN Server.
On Thu, Dec 11, 2008 at 6:08 AM, Fervent Coder <[email protected]> wrote:
>
> I have noticed that when I add the Everyone account explicitly to a
> location, any permission set that is inheriting from its parent no
> longer works. To me this is unexpected behavior, but please let me
> know.
>
> This is on version 1.6.2 of VisualSVN Server.
>
> STEPS TO REPRODUCE:
> 1. Add a group with Read / Write permissions at the base level.
> 2. Use an account from that group to check in something to a
> repository. [SHOULD BE SUCCESSFUL]
> 3. In that same repository, add the Everyone account.
> 4. Now try to check in something. [DOES NOT WORK]
> 5. Change the permissions on the group to Explict (no longer
> inheriting).
> 6. Now try to check in something [SHOULD BE SUCCESSFUL]
>
> More information here:
> http://ferventcoder.com/archive/2008/12/10/caveat-to-adding-the-everyone-account-in-visualsvn-server.aspx
>
--
Olga Dolidze
VisualSVN Support
