I suppose this is why I am wondering if I should be emailing through the regular mail list, rather than dev, because I’m not quite sure what to do with the patch. I managed to find the patch command, but when I run 'patch <patch-1.5.21hg.tamovl.sysdotlock.1’, I get:
patching file Makefile.am patching file configure.ac patching file Makefile.am Hunk #1 FAILED at 2. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.am.rej patching file init.h Then, when I add the —with-system-dotlock option to ./configure, it still doesn’t recognize it. I am barely treading water with these issues, so I ask, if you are willing, to bear with me as I work out the procedure. Best, Conor Cook > On Feb 2, 2015, at 7:48 AM, Vincent Lefevre <[email protected]> wrote: > > On 2015-02-01 13:16:04 -0600, Conor Cook wrote: >> My mutt -v does not list the "Configure Options," so I went through >> and tried to corroborate the list of "USE-…" and "HAVE_…" options, >> but still the error: >> >>> chgrp: you are not a member of group mail >>> Can't fix mutt_dotlock's permissions! This is required to lock mailboxes >>> in the mail spool directory. >>> make[4]: *** [install-exec-hook] Error 1 >>> make[3]: *** [install-exec-am] Error 2 >>> make[2]: *** [install-am] Error 2 >>> make[1]: *** [install-recursive] Error 1 >>> make: *** [install] Error 2 > > I solve this problem by using the very old sysdotlock patch (attached). > It adds a --with-system-dotlock option so that one can use a system > mutt_dotlock program that may already be installed. > > Now, AFAIK, dotlocking is completely unreliable. Only fcntl locking > should be used. If not available, use a mailbox format that does not > need locking. > > -- > Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> > 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> > Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) > <patch-1.5.21hg.tamovl.sysdotlock.1>
