[cvsnt] Problem setting permissions in 2.0.62.1817

[capaverde at 3ia.com.br]

Mike

The problem remains de same, no matter I use T00363 or t00363.
As long as I could undestand, cvs 2.0.62.1817 is not taking
care of the fact that I'm the dir's owner, just allowing the
admin users or anyone else that have the control right to change ACL.
It's no problem for us. Our problem is that the owner lost
the rights to change their own directories' permissions.
Tony, is that behavior correct?

Capaverde

Quoting Mike Wake <mike.wake at thales-tts.com>:

> Capitalisation is/might be important.
>
> try
> cvs chacl -u T00363 -a read,write
>
> Cheers
> Mikew
>
> capaverde at 3ia.com.br wrote:
> > Hello
> >
> > Testing the CVSNT 2.0.62.1817, I found a new (at least, to me)
> > behavior that seems incorrect. I just imported a new module to my
> > test repository and listed the directory's ACL:
> >
> > cvs lsacl
> > Directory: .
> > Owner: T00363
> >
> > Fine. Then I try to set permission for it:
> >
> > cvs chacl -u t00363 -a read,write
> > cvs server: User 'T00363' cannot modify permissions for /cvsroot/bky
> >
> > In 2.0.51d, that is the version we are currently using, only the
> > admin users and the directory's owner can change the ACL.
> > In 2.0.62.1817, the only way to change the ACL is giving admin
> > rights to user. I know that now anyone who has control rights can
> > set the ACL, but how do I do it first time after module's import,
> > as no ordinary user have permissions yet?
> > My CVSROOT is :sspi:localhost:/cvsroot
> >
> > capaverde
> >
> >
> >
> > _______________________________________________
> > cvsnt mailing list
> > cvsnt at cvsnt.org
> > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
>