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@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? Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 6 (Zod) - Linux kernel 2.6.19-1.2895.fc6 Load : 0.69 0.58 0.60 -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
