On Mon, 09 May 2011 10:20:18 -0700, Jameson Graef Rollins <jrollins at 
finestructure.net> wrote:
> ***I hereby declare that release-candidate/0.6 is ready for release.***

After all of that pomp, I take it all back!

Fully fearful of further delaying release of 0.6, I decided I wanted to
slip in a couple last-minute patches, most of which are really bug
fixes:

I told Felipe I would include his vim patches, so I wanted to follow
through on that.

Dmitry submitted a patch to fix sporadic seg faults in one of the emacs
tests.

I built release-candidate/0.6 against the Ubuntu package of
libgmime-2.4-dev, version 2.4.24-0ubuntu1 [0].  This fixed all but one
of the failing crypto tests, and the delinquent test only needed to be
updated to expect libgmime's improved error reporting.  This means that
all 184 tests now consistently cleanly pass (after 100 runs).  This
persuaded me to decide that 0.6 really should depend on this newly
released 2.4.24 version of libgmime-2.4-2, and I updated the debian
packaging accordingly.

If people think this is not the way to go, I'm open to arguments.  I
think this /will/ create a bit of a snag for debian users.  libgmime's
dependency is not currently available in debian, so declaring notmuch
0.6 dependent on libgmime-2.4-2 2.4.24 will render the debian package of
0.6 uninstallable (and maybe even unbuildable).  But I'm hoping we can
use this to convince the debian maintainer of libgmime to release 2.4.24
concurrently with notmuch 0.6.  If this sounds ridiculous, please let me
know and we can look at a different solutions.

Again, sorry for the last minute churn, but I think it's worth it [1].

jamie.

[0] https://launchpad.net/ubuntu/+source/gmime2.4/2.4.24-0ubuntu1/
[1] git://finestructure.net/notmuch
    release-candidate/0.6
    f357eafd3c315c7b59abe3088479a3b4e68a4d11
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: 
<http://notmuchmail.org/pipermail/notmuch/attachments/20110510/da69a3e9/attachment.pgp>

Reply via email to