From: David Bremner <david@tethera.net>
To: Jan Malakhovski <oxij@oxij.org>, notmuch@notmuchmail.org
Subject: Re: [BUG] gmime-3.0.1 (was: [PATCH] crypto: gracefully handle gmime errors)
Date: Tue, 05 Sep 2017 07:54:19 -0300 [thread overview]
Message-ID: <87zia9wh44.fsf@tethera.net> (raw)
In-Reply-To: <874lsn6c1h.fsf@oxij.org>
Jan Malakhovski <oxij@oxij.org> writes:
> When building with gmime-3.0.1 `tests/T355-smime.sh` passes and messages
> in my inbox get parsed ok, but a lot of other tests break.
>
> Both on 0.25 tag and HEAD get. See attached build log.
>
> building path(s) ‘/nix/store/x7dql3l36nrs84wmzc3jnma71rgdfdfb-notmuch-0.25’
> unpacking sources
> unpacking source archive /nix/store/w1kbvfgbi5sz6fp8vwn888yckiwwd24d-notmuch-46bda29
> source root is notmuch-46bda29
I'm fairly certain this something nix specific. 3.0.1 is the
default version of gmime I develop against these days.
> patching sources
What patches, if any are applied here?
> T350-crypto: Testing PGP/MIME signature verification and decryption
> PASS emacs delivery of signed message
> FAIL signature verification
> --- T350-crypto.2.expected 2017-08-31 14:25:03.126885225 +0000
> +++ T350-crypto.2.output 2017-08-31 14:25:03.126885225 +0000
> @@ -18,13 +18,7 @@
> ],
> "content-type": "multipart/signed",
> "id": 1,
> - "sigstatus": [
> - {
> - "created": 946728000,
> - "fingerprint": "5AEAB11F5E33DCE875DDB75B6D92612D94E46381",
> - "status": "good"
> - }
> - ]
> + "sigstatus": []
> }
> ],
> "date_relative": "2000-01-01",
> Failed to verify signed part: Cannot verify multipart/signed part: unregistered signature protocol 'application/pgp-signature'.
It seems like your gmime install doesn't understand PGP/MIME. That's
pretty strange since afaik it enables SMIME and PGP/MIME with the same flag.
Previously you wrote
,----
| I wonder why gnupg stops getting referenced with gmime-3.0.1. My guess
| is that `./configure` does something very different when compiling with
| gmime-3.
`----
Although I don't think that configure is really the problem, the missing
dependence on gnupg is suspicious. Not having a gpg binary at all
should cause more failures and/or messages about skipping. It's hard for
me to test because on Debian there is a hard dependency of gmime-3.0 on
gnupg.
next prev parent reply other threads:[~2017-09-05 10:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 13:31 [PATCH] crypto: gracefully handle gmime errors Jan Malakhovski
2017-08-31 13:44 ` Jan Malakhovski
2017-09-01 0:10 ` [PATCH] cli: propagate NULL from _mime_node_create, handle it in callers David Bremner
2017-09-01 20:32 ` Jan Malakhovski
2017-08-31 14:22 ` [PATCH] crypto: gracefully handle gmime errors David Bremner
2017-08-31 14:30 ` David Bremner
2017-08-15 17:37 ` bug: notmuch show --decrypt leads to SIGSEGV Matt Armstrong
2017-08-15 18:11 ` David Bremner
2017-08-15 19:10 ` Matt Armstrong
2017-08-15 23:12 ` David Bremner
2017-08-16 16:41 ` Matt Armstrong
2017-08-20 13:43 ` David Bremner
2017-08-31 15:17 ` [PATCH] crypto: gracefully handle gmime errors Jan Malakhovski
2017-08-31 18:33 ` David Bremner
2017-08-31 22:27 ` David Bremner
2017-08-31 23:20 ` Matt Armstrong
2017-08-31 23:59 ` Jan Malakhovski
2017-11-10 1:05 ` bug: notmuch show --decrypt leads to SIGSEGV David Bremner
2017-08-31 14:34 ` [BUG] gmime-3.0.1 (was: [PATCH] crypto: gracefully handle gmime errors) Jan Malakhovski
2017-09-05 10:54 ` David Bremner [this message]
2017-09-05 12:55 ` Jan Malakhovski
2017-09-05 13:38 ` David Bremner
2017-09-05 14:26 ` Jan Malakhovski
2017-09-05 15:26 ` David Bremner
2017-09-05 20:23 ` Jan Malakhovski
2017-09-05 14:04 ` Servilio Afre Puentes
2017-09-05 14:27 ` Jan Malakhovski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zia9wh44.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=oxij@oxij.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).