Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

mutt-1.5.10 (version bump)

Let's see if this one get's out before mutt-1.5.11 comes out! ;)

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Also note this is a rather major release since some patches (i.e. edit-threads)
have been integrated into mutt.

Aaron If you need help with this I'll be eager to help.

Cheers,
Ferdy

I also read at the header cache homepage
(http://wwwcip.informatik.uni-erlangen.de/~sithglan/mutt/) that it should be
integrated into mutt from 1.5.10.
It says so on the front page.

Yes... I also noticed that the header cache has been fully merged.

We think that is pointless to still maintaining nntp support in mutt since not a
lot of people use it and muttng implements it. Also it difficults maintaining
mutt up to date and adding new patches so mutt-1.5.10 won't have nntp support.

I've been playing with mutt-1.5.10, I have a working (at least for me) ebuild in
my overlay:

http://dev.gentoo.org/~ferdy/overlay/mail-client/mutt/mutt-1.5.10-r1.ebuild

Though I'm having a little problem... switching from USE="vanilla" to
USE="-vanilla" makes mutt segfault while evaluating the cache. I still don't
know what's causing it. (I haven't tested if this happens with earlier mutt
versions yet).

If you could test that ebuild and report some feedback it'd be great.

Cheers,
Ferdy

(In reply to comment #3)
> Yes... I also noticed that the header cache has been fully merged.
> 
> We think that is pointless to still maintaining nntp support in mutt since not a
> lot of people use it and muttng implements it. Also it difficults maintaining
> mutt up to date and adding new patches so mutt-1.5.10 won't have nntp support.
> 
> I've been playing with mutt-1.5.10, I have a working (at least for me) ebuild in
> my overlay:
> 
> http://dev.gentoo.org/~ferdy/overlay/mail-client/mutt/mutt-1.5.10-r1.ebuild
> 
> Though I'm having a little problem... switching from USE="vanilla" to
> USE="-vanilla" makes mutt segfault while evaluating the cache. I still don't
> know what's causing it. (I haven't tested if this happens with earlier mutt
> versions yet).
> 
> If you could test that ebuild and report some feedback it'd be great.
> 
> Cheers,
> Ferdy


Try to delete the contents of your hader_cache directory to see if it stops
segfaulting...

It stopped with me with 1.5.9...

Well... removing the header_cache directory works... I meant *switching* made
it
segfault (and also run out of memory, i.e. weird situation).

From 'scratch' both (vanilla and -vanilla) work fine.

Cheers,
Ferdy

I do use NNTP support in mutt and do not want to switch to another program for
NNTP alone. Therefore, it would be glad if you could continue including it.

Just heard from Aaron that we will continue to support nntp.

Cheers,
Ferdy

(In reply to comment #5)
> Well... removing the header_cache directory works... I meant *switching* made it
> segfault (and also run out of memory, i.e. weird situation).
> 
> From 'scratch' both (vanilla and -vanilla) work fine.
> 
> Cheers,
> Ferdy

Exactly what happened to me, segfault on one comp and out of memory on another...

ok, 1.5.10 is in portage now