Problem with CVS ACLs

[Josh Boyer]

On Mon, 2007-02-12 at 19:03 +0100, Matthias Saou wrote:
> Hi,
> 
> Bill just created the "libmp4v2" CVS module for me, where I added all
> the files I wanted to the various branches, and removed the pkg.acl
> file. But when I went ahead and did a "cvs commit" for all the changes
> at once, I got this :
> 
> [dude at python3 libmp4v2]$ cvs commit
> cvs commit: Examining .
> cvs commit: Examining FC-5
> cvs commit: Examining FC-6
> cvs commit: Examining devel
> thias is the package owner - allowing ACL changes for libmp4v2.
> **** Access denied: thias is not in ACL for rpms/libmp4v2
> cvs commit: Pre-commit check failed
> **** Access denied: thias is not in ACL for rpms/libmp4v2/FC-5
> cvs commit: Pre-commit check failed
> **** Access denied: thias is not in ACL for rpms/libmp4v2/FC-6
> cvs commit: Pre-commit check failed
> **** Access denied: thias is not in ACL for rpms/libmp4v2/devel
> cvs commit: Pre-commit check failed
> cvs [commit aborted]: correct above errors first!
> cvs commit: saving log message in /tmp/cvsPZljJI
> 
> The mail to the list about ACLs mentions that if a maintainer
> doesn't want any ACL restrictions for a package, he just needs to remove
> the pkg.acl file... hmmm... so why is this happening?

It takes up to an hour for the server side to sync.  Have you wait a bit
and tried again?

josh