From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Cc: Daniel Kahn Gillmor <dkg@debian.org>
Subject: Failing notmuch/SMIME test
Date: Fri, 18 Mar 2022 07:48:01 -0300 [thread overview]
Message-ID: <87mthn5yfy.fsf@tethera.net> (raw)
One of the SMIME tests is failing for me.
T355-smime: Testing S/MIME signature verification and decryption
FAIL signature verification (notmuch CLI)
--- T355-smime.4.expected 2022-03-18 10:31:31.877258855 +0000
+++ T355-smime.4.output 2022-03-18 10:31:31.877258855 +0000
@@ -24,7 +24,7 @@
"sigstatus": [
{
"created": 946728000,
- "email": "<test_suite@notmuchmail.org>",
+ "email": "test_suite@notmuchmail.org",
"expires": 424242424,
"fingerprint": "616F46CD73834C63847756AF0DFB64A6E0972A47",
"status": "good",
@@ -38,7 +38,7 @@
"status": [
{
"created": 946728000,
- "email": "<test_suite@notmuchmail.org>",
+ "email": "test_suite@notmuchmail.org",
"expires": 424242424,
"fingerprint": "616F46CD73834C63847756AF0DFB64A6E0972A47",
"status": "good",
I'm running gpgsm 2.2.27, gpgme 1.16.0, and gmime 3.2.9. At guess the
change is due to the recent gmime upgrade, but that is pure speculation,
I could not find anything in the gmime git log to back it up. The change
looks innocuous enough, but of course it's enough to break the test, and
I'm not sure how to make this consistent between versions.
next reply other threads:[~2022-03-18 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 10:48 David Bremner [this message]
2022-03-20 21:10 ` Failing notmuch/SMIME test Daniel Kahn Gillmor
2022-03-22 17:16 ` David Bremner
2022-04-09 12:34 ` [PATCH 1/2] configure: restructure gmime cert validity checker code David Bremner
2022-04-09 12:34 ` [PATCH 2/2] test/smime: fix signature verification test with newer gmime David Bremner
2022-04-11 0:35 ` Daniel Kahn Gillmor
2022-04-11 8:44 ` Michael J Gruber
2022-04-11 21:53 ` Daniel Kahn Gillmor
2022-04-12 20:15 ` [PATCH v2 " michaeljgruber+grubix+git
2022-04-12 23:26 ` Daniel Kahn Gillmor
2022-04-13 11:28 ` David Bremner
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=87mthn5yfy.fsf@tethera.net \
--to=david@tethera.net \
--cc=dkg@debian.org \
--cc=notmuch@notmuchmail.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).