Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Mutt 1.4-1 opens mbox read-only
Date:	Wed, 31 Jul 2002 03:02:44 -0500
Message-ID:	<NCBBIHCHBLCMLBLOBONKKEBBDDAA.g.r.vansickle@worldnet.att.net>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
In-Reply-To:	<20020730195051.GA1324@tishler.net>
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
Importance:	Normal

> Jens,
>
> On Sat, Jul 27, 2002 at 02:54:22AM +0200, Jens Schuessler wrote:
> > * Jason Tishler <jason AT tishler DOT net> [24-07-02 14:37]:
> > > Please try running mutt_dotlock -t on your mbox.  Does it indicate
> > > incorrect permissions?
> >
> > After building the package again with --enable-external-dotlock, I get
> > the mutt_dotlock.exe and my mboxes are writeable, everythings fine.
> > All mboxes got a "0" on this test.
>
> I'm glad the mutt is working for you now.  However, it would be nice to
> better understand why configuring without --enable-external-dotlock
> causes this problem.

Hmmm.  Well, in the interim, I think I'll just rebuild and reissue the package
with --enable-external-dotlock and call that good.

--
Gary R. Van Sickle
Brewer.  Patriot.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -