Issue with mutt-devel after MacPorts update
Emmanuel Hainry
milosh at macports.org
Mon Oct 5 03:33:53 PDT 2009
Citando Bryan Blackburn :
>
> On Sun, Oct 04, 2009 at 03:55:11PM -0400, Doctor Who said:
> > On Sun, Oct 4, 2009 at 3:42 PM, Bryan Blackburn <blb at macports.org>
> > wrote:
> > > On Sun, Oct 04, 2009 at 09:49:50AM -0400, Doctor Who said:
> > >> I had mutt-devel working with no issues on my Snow Leopard
> > >> install until I did a complete uninstall and reinstall of
> > >> MacPorts to the latest version. The issue is specifically with
> > >> getting the "headercache" piece working again.
> > >>
> > >> I install mutt-devel with the following variants:
> > >>
> > >> sudo port install mutt-devel +headercache +gpgme +imap +ssl
> > >> +sidebar
> > >
> > > If you use 'port variants mutt-devel' you'll note that you need to
> > > select one of the database backends as well:
> > >
> > > headercache: Enable header caching (requires gdbm, qdbm, or
> > > tokyocabinet)
> > >
> > > The port should probably error out when headercache is selected
> > > but no database is...
> > >
> > > And for what it's worth, 1.5.20 with headercache and tokyocabinet
> > > is working fine here 10.6.1.
> > >
> >
> > Thanks. I had tried before with gdbm and had the same behavior.
> > Trying now with tokyocabinet seems to have it working again. Weird.
>
> Hmm, perhaps there's something wrong with headercache+gdbm; looking at
> the Portfile again, it actually looks like +gdbm should get set if you
> don't set one of the other databases.
>
If the headercache has been generated with tokyocabinet, it is quite
normal it fails to be read with gdbm. When changing thi format, you
should try to delete the header_cache file generated with the previous
variant and relaunch.
Emmanuel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20091005/60449d83/attachment.bin>
More information about the macports-users
mailing list