Re: [BUG] gmime-3.0.1 (was: [PATCH] crypto: gracefully handle gmime errors)

Subject: Re: [BUG] gmime-3.0.1 (was: [PATCH] crypto: gracefully handle gmime errors)

Date: Tue, 05 Sep 2017 14:26:32 +0000

To: David Bremner,


From: Jan Malakhovski

David Bremner <> writes:

>> I added `gpgme` to `buildInputs` of `gmime` and now `notmuch` passes all
>> the tests. Yay! So that was the root problem.
>> Is it correct to assume that when building with `gmime-3` `notmuch`
>> stops calling `gpg` binary and does all the things PGP using `gmime-3`?
> notmuch does not call gpg directly in either case. What changes in the
> way gmime calls gpg. In 2.6 gmime called gpg, while in 3.0 it uses gpgme.
> It sounds like your gmime-3 package is missing a dependency on gpgme.

Why then at the very least

- crypto.c
- notmuch-config.c
- emacs/notmuch-crypto.el

files refer to "gpg" in the source with lines like

    params.crypto.gpgpath = notmuch_config_get_crypto_gpg_path (config);
    notmuch_config_set_crypto_gpg_path (config, "gpg");
    gpgctx = g_mime_gpg_context_new (NULL, crypto->gpgpath ? crypto->gpgpath : "gpg")
notmuch mailing list