[cvsnt] reg: head-branch acl permission

[Shivendra_Vishal]

Hi,

Thank you Arthur, I changed the ACL for head (removed deny) and its working for our demo repository, we still have to verify the same in our main repository!!!!!

Here I want to ask a question that why giving the "deny" permission is creating problem for applying ACL to the branch?? I am asking this because "Aclmode=normal" in config file is also denying all permission whereas specifying deny permission explicitly through chacl is creating trouble.

Secondly, I tried to remove the ACL using the -d option as follows:
D:\demo1>cvs chacl -d module1
deleting ACL for directory module1

However when I use lsacl to view the ACL the ACL's are not deleted and cvs shows following result. Any suggestions??

D:\demo1>cvs lsacl module1
Directory: module1
Owner: sb17461

user=sv48388,branch=BR_TEST
        read
        write

user=sv48388
        read
        write(deny)
        tag(deny)

user=vb59263
        read
        write


Regards,

Vishal
 


-----Original Message-----
From: Arthur Barrett [mailto:arthur.barrett at march-hare.com] 
Sent: Friday, December 21, 2007 11:04 PM
To: Shivendra_Vishal; cvsnt at cvsnt.org
Subject: RE: [cvsnt] reg: head-branch acl permission

Vishal,

> and branch. When I am giving read permission on the head to the
> developers and read/write permission on the branch then while 
> committing
> the changes in the branch developers get the error "User do not have
> permission to write to the repository" whereas when I gave write
.
.
.
> user=sv48388,branch=BR_TEST
>         read
>         write
> 
> user=sv48388
>         read
>         write(deny)
>         tag(deny)
.
.
.
> # Set the Acl parsing type (none,compat,normal).
> AclMode=normal
> 

Do not create any (deny) permissions, all users are denied automatcially
due to AclMode=normal.

Please confirm that once the write(deny) and tag(deny) permissions are
removed from HEAD that the user sv48388 can now commit to branch BR_TEST
but not HEAD.

Regards,


Arthur Barrett



DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.