Date: Sat, 9 Feb 2002 10:29:17 -0200 From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [...] cvs export: failed to create lock directory in repository `/cvs/src/cyrus/doc/internal': Permission denied cvs export: failed to obtain dir lock in repository `/cvs/src/cyrus/doc/internal' cvs [export aborted]: read lock failed - giving up
This is NOT the first time I get this problem. Anyone knows what is up, and how to permanently fix this? (HEAD branch) This is due to an incorrect AFS ACL (our repository is stored in AFS internally, and our CVS server only has rights to create locks, not actually modify the source files). I've fixed this problem; the root cause is when we create new directories in the repository a manual setacl command has to be run. I don't think there's an easy fix for this. Also, is there a way for people to receive the CVS commit logs for Cyrus IMAPd (and SASL for that matter)? It would help me a damn great deal to coordinate new releases when something really serious gets fixed in CVS... You mean via a mailing list? Not currently; if this would really be useful to people I can look into it (it might be a little difficult due to our current setup). PS for the CMU crew: *PLEASE* update the config.sub and config.guess files you have in there, they are ANCIENT, and break builds in at least 4 architectures (MIPS, MIPSEL, ia64, hppa). GNU config is a !@% pain in the backside in that regard, one MUST keep it updated from GNU config CVS. Please let me know where to fetch it (more specifically). Also, would you guys be interested in a configure.in port to configure.ac (autoconf 2.52)? Other than that, I have all my patches to cyrus 2.0 ported to CVS cyrus 2.1, and will repost them here shortly (or start maintaining a www page for them). Yes. Obviously, we'd like libsasl2 upgraded too. Larry
