From: Daniel Kahn Gillmor <dkg@debian.org>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] test/smime: fix signature verification test with newer gmime.
Date: Sun, 10 Apr 2022 17:35:53 -0700 [thread overview]
Message-ID: <87r164mp7a.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20220409123453.606391-2-david@tethera.net>
[-- Attachment #1.1: Type: text/plain, Size: 1247 bytes --]
Thanks, Bremner!
This series looks reasonable to me. nice clever hack to reuse the
gmime embedded .c source for the test.
a bit of a tweak below:
On Sat 2022-04-09 09:34:53 -0300, David Bremner wrote:
> + printf "Checking for GMime new email format... "
> + if ${CC} -DCHECK_EMAIL ${CFLAGS} ${gmime_cflags} _check_gmime_cert.c ${gmime_ldflags} -o _check_email &&
> + GNUPGHOME=${TEMP_GPG} ./_check_email; then
> + gmime_new_email_format=1
> + printf "Yes.\n"
> + else
> + gmime_new_email_format=0
> + printf "No (some tests will be skipped).\n"
> + fi
> else
> printf 'No.\nFailed to set up gpgsm for testing X.509 certificate validity support.\n'
> errors=$((errors + 1))
Words like "new" have a tendency to get, well, old.
I'd say
"Checking GMime emits email addresses from certs without angle brackets..."
And i'd name the variable gmime_cert_addresses_have_angle_brackets (so
"1" effectively means "probably a stale, deprecated version of GMime").
Then change the rest of the tests to match.
This is kind of an aesthetic choice -- i'd be fine with the original
patch too. but it seems safer to just identify the out-of-date stuff
when it happens, rather than identifying the current stuff.
--dkg
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2022-04-11 0:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 10:48 Failing notmuch/SMIME test David Bremner
2022-03-20 21:10 ` 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 [this message]
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=87r164mp7a.fsf@fifthhorseman.net \
--to=dkg@debian.org \
--cc=david@tethera.net \
--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).