On Sun, 10 Feb 2002, Lawrence Greenfield wrote: > cvs export: failed to create lock directory in repository > > 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.
Hmm, probably not. The kind of fix we would do here for such a problem would be a registry of the correct ACLs for every subtree, and a cron job that force-applied them (recursively) every day... > 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). Either through a mailinglist, or even by adding our addresses to a manual list through direct request :) The commit logs are extremely useful for anyone tracking CVS, since we get to notice every time an important bug is closed in CVS (provided the developers like to write good log entries, I suppose). > 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). Sure thing. cvs -z 4 -d :pserver:[EMAIL PROTECTED]:/cvsroot/config export -rHEAD config For you guys, a simple checkout of config.sub and config.guess before you release an official tarball would be enough, I think. You can use config.sub -t and config.guess -t to get their release dates for logging. > 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. I will have a go at it later, then. Autoconf 2.52-generated configure scripts are a bit faster than old autoconf 2.13, but other than that (and a saner command-line interface and internals), there aren't many changes. OTOH, people often do not have autoconf 2.52 installed, and autoconf 2.52 will not always work right with an autoconf 2.13 script... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
