Kyle Wheeler | 2 Dec 23:05

[voss <at> debian.org: Bug#400831: logic error in mutt-1.5.13/account.c]

I came across this posting to the Debian mutt list.

~Kyle
-- 
I love America more than any other country in this world, and, exactly 
for this reason, I insist on the right to criticize her perpetually.
                               -- James Baldwin, Notes of a Native Son
Picon Favicon
From: Jochen Voss <voss <at> debian.org>
Subject: Bug#400831: logic error in mutt-1.5.13/account.c
Date: 2006-11-28 23:00:29 GMT
Package: mutt
Version: 1.5.13-1
Severity: normal

Hi,

recently I came across the following bit of code in the source file
mutt-1.5.13/account.c (near the end of the file):

    void mutt_account_unsetpass (ACCOUNT* account)
    {
      account->flags &= !M_ACCT_PASS;
(Continue reading)

Thomas Roessler | 3 Dec 15:10

Re: [voss <at> debian.org: Bug#400831: logic error in

fixed

On 2006-12-02 17:05:47 -0500, Kyle Wheeler wrote:
> From: Kyle Wheeler <kyle-mutt-dev <at> memoryhole.net>
> To: mutt-dev <at> mutt.org
> Date: Sat, 2 Dec 2006 17:05:47 -0500
> Subject: [voss <at> debian.org: Bug#400831: logic error in
> 	mutt-1.5.13/account.c]
> X-Spam-Level: 
> Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
> 
> I came across this posting to the Debian mutt list.
> 
> ~Kyle
> -- 
> I love America more than any other country in this world, and, exactly 
> for this reason, I insist on the right to criticize her perpetually.
>                               -- James Baldwin, Notes of a Native Son

> From: Jochen Voss <voss <at> debian.org>
> To: Debian Bug Tracking System <submit <at> bugs.debian.org>
> Date: Tue, 28 Nov 2006 23:00:29 +0000
> Subject: Bug#400831: logic error in mutt-1.5.13/account.c
> Reply-To: Jochen Voss <voss <at> debian.org>, 400831 <at> bugs.debian.org
> X-Spam-Level: 
> DomainKey-Status: no signature
> 
> Package: mutt
> Version: 1.5.13-1
> Severity: normal
(Continue reading)

Thomas Roessler | 4 Dec 05:00

[2006-12-04] CVS repository changes

This message was generated and sent automatically.  It contains a
summary of the CVS commits over the last 48 hours.  These changes
should be propagated to the public repository within at most a day
or two.  Most probably, they have already been propagated.

2006-12-03 14:07:54  Thomas Roessler  <roessler <at> does-not-exist.org>
(roessler)

	* account.c: Fix logic error; debian#400831.

Derek Martin | 4 Dec 18:46
Gravatar

building the manual

Where is it documented what tools are needed to build the manual (in
CVS)?  

Thanks

--

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail.  Sorry for the inconvenience.  Thank the spammers.

David Champion | 4 Dec 18:58
Favicon

Re: building the manual

* On 2006.12.04, in <20061204174615.GA22441 <at> dragontoe.org>,
*	"Derek Martin" <invalid <at> pizzashack.org> wrote:
> Where is it documented what tools are needed to build the manual (in
> CVS)?  

.../doc/devel-notes.txt

/Generating Mutt Documentation From Source/

--

-- 
 -D.    dgc <at> uchicago.edu        NSIT    University of Chicago

Derek Martin | 5 Dec 06:10
Gravatar

Re: building the manual

On Mon, Dec 04, 2006 at 11:58:26AM -0600, David Champion wrote:
> * On 2006.12.04, in <20061204174615.GA22441 <at> dragontoe.org>,
> *	"Derek Martin" <invalid <at> pizzashack.org> wrote:
> > Where is it documented what tools are needed to build the manual (in
> > CVS)?  
> 
> .../doc/devel-notes.txt

Thanks David.  FWIW, I attempted to follow the directions on an older
system, but was not able to get it to work (in what I consider to be a
reasonable amount of time).  I have stuff installed for docbook but
needed the xsl stuff.  After unzipping it and setting the variables
mentioned, I still got errors when Mutt tried to build the manual,
albeit different ones from before.

I must be getting old...  I no longer have the patience to spend time
debugging this kind of thing.  I ended up building it on my FC5 system
and just copying it.  Of course, I remember the days when an entire
Linux distribution fit on a few floppies (where "a few" is some number
between 10 and 30)...  ;-)  [Point being the system has gotten a whole
lot bigger and more complicated, such that keeping track of every
peice (and how to install/configure it) is no longer possible...]

:)

--

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail.  Sorry for the inconvenience.  Thank the spammers.
(Continue reading)

Thomas Roessler | 5 Dec 05:00

[2006-12-05] CVS repository changes

This message was generated and sent automatically.  It contains a
summary of the CVS commits over the last 48 hours.  These changes
should be propagated to the public repository within at most a day
or two.  Most probably, they have already been propagated.

2006-12-03 14:07:54  Thomas Roessler  <roessler <at> does-not-exist.org>
(roessler)

	* account.c: Fix logic error; debian#400831.

Pavel Gorshkov | 5 Dec 19:07
Picon

doc/manual.pdf

There is a target named `manual.pdf' in doc/Makefile.am, but the
resulting PDF file has a lot of undefined references.

To get a neat looking PDF manual, one needs to run pdfjadetex
*three* times in a row, so please review the attached patch for
inclusion in CVS.

Thanks.

--
Pavel Gorshkov
--- doc/Makefile.am.orig	Tue Nov 14 21:56:29 2006
+++ doc/Makefile.am	Tue Dec  5 20:49:08 2006
@@ -82,7 +82,8 @@

 check:
 manual.txt: manual.html
-	-lynx -dump -nolist -with_backspaces $^ > $@ || w3m -dump $^ > $@
+	-lynx -dump -nolist -with_backspaces $^ > $@ || w3m -dump $^ > $@ || \
+	    elinks -dump -no-numbering -no-references $^ > $@

 manual.html: $(srcdir)/html.xsl stamp-doc-xml
 	-xsltproc --nonet -o $@ $(srcdir)/html.xsl manual.xml
@@ -92,7 +93,9 @@
 	touch stamp-doc-chunked

 manual.pdf: manual.tex
-	-if test -f manual.tex; then pdfjadetex manual.tex; fi
(Continue reading)

getreu | 6 Dec 09:58
Picon

mutt/2595: mutt doesn't accept utf8 configuration files starting with EF BB BF

>Number:         2595
>Notify-List:    
>Category:       mutt
>Synopsis:       mutt doesn't accept utf8 configuration files starting with EF BB BF
>Confidential:   no
>Severity:       minor
>Priority:       medium
>Responsible:    mutt-dev
>State:          open
>Keywords:       
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 06 09:58:26 +0100 2006
>Originator:     getreu <at> web.de
>Release:        1.5.11 (2005-09-15)
>Organization:
>Environment:
Linux
>Description:
since vers approx 1.4 utf8 coded configuration files are allowed in order to use utf8 coded strings.
This works fine.
But today's editors add the sequence EF BB BF at the beginning of the file which normally should be ignored.
Mutt exits instead with a fatal error message.
>How-To-Repeat:
>Fix:
>Add-To-Audit-Trail:

>Unformatted:

(Continue reading)

Rocco Rutte | 6 Dec 13:35
Picon

Re: mutt/2595: mutt doesn't accept utf8 configuration files

The following reply was made to PR mutt/2595; it has been noted by GNATS.

From: Rocco Rutte <pdmef <at> gmx.net>
To: bug-any <at> bugs.mutt.org
Cc: 
Subject: Re: mutt/2595: mutt doesn't accept utf8 configuration files
	starting with EF BB BF
Date: Wed, 6 Dec 2006 12:28:53 +0000

 Hi,

 * getreu <at> web.de [06-12-06 09:58:27 +0100] wrote:

 >since vers approx 1.4 utf8 coded configuration files are allowed in order to use utf8 coded strings.
 >This works fine.
 >But today's editors add the sequence EF BB BF at the beginning of the file which normally should be ignored.
Mutt exits instead with a fatal error message.

 If you ask me, this is not a mutt bug but a bug of those editors since 
 that magic sequence will be considered binary data by almost any tool 
 reading the input.

 I only saw pieces of "software" on Windows doing that so that I think 
 there it may be some sort of library routine being evil.

 Of couse, mutt could be relatively easy made to ignore these few bytes 
 and adjust $config_charset internally... but it's not a mutt bug I'd 
 say.

    bye, Rocco
(Continue reading)


Gmane