This was reported to the dev list last week but an issue wasn't created yet. Can
you give some more info about your environment (Platform, server type and
version of client & server) then I can file a new issue - or you may if you
like.
Lieven
Quoting Quentin Narferao <qnarferao@yahoo.com>:
> I didn't see anything about this in the current issues (although it may be
> related in some way to other commit bugs dealing with authz?)
>
> Anyway, the issue is when you set up specific directory permissions as such:
>
> [groups]
> groupAB = userA,userB
>
> [/]
> * =
> @groupAB = rw
>
> [/a]
> userC = rw
>
> This means that userA and userB have full access throughout the entire
> repository, but userC only has access to the subfolder 'a'. When userC
> updates a file in this directory and commits (with or without comment) it
> succeeds. When userC locks a file in that directory, modifies it and commits
> with or without a comment it fails "Authorization failed".
>
> Strange bug to be sure, but a fairly important one because basically its
> saying that development users with access to specific development trees only
> cannot lock files and then commit them (they have to release the lock prior
> to commit...).
>
> Has anyone heard of this?
>
> -Q
>
>
>
>
>
>
____________________________________________________________________________________
> The fish are biting.
> Get more visitors on your site using Yahoo! Search Marketing.
> http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 19 10:18:19 2007