unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michael J Gruber <git@grubix.eu>
To: Daniel Kahn Gillmor <dkg@debian.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] test/smime: fix signature verification test with newer gmime.
Date: Mon, 11 Apr 2022 10:44:47 +0200	[thread overview]
Message-ID: <CAA19uiRLSSZWm_xN=5uqieLFoCkqCuOM7b-c1-Qp45aY2T4RLg@mail.gmail.com> (raw)
In-Reply-To: <87r164mp7a.fsf@fifthhorseman.net>


[-- Attachment #1.1: Type: text/plain, Size: 2354 bytes --]

Am Mo., 11. Apr. 2022 um 02:36 Uhr schrieb Daniel Kahn Gillmor <
dkg@debian.org>:

> Thanks, Bremner!
>
> This series looks reasonable to me.  nice clever hack to reuse the
> gmime embedded .c source for the test.
>

Just so that others don't have to be wondering, too: notmuch does not embed
gmime sources and does not reuse them. (It would be very wrong to do so.)
notmuch has a file `_check_gmime_cert.c` which is used for configure checks
and which David cleverly amended to check for the return format of
signature checks (when compiled against the libgmime3).

If I read 2/2 correctly, though, then T355-smime does not adjust its
expected textual outcome to the results of the check, but rather marks the
test "known broken" if the signature check does not return the "new"
format. In other words: Unless you have a very new unpatched gmime,
T355-sime does not "really" do this subtest any more - it is happy as soon
as it fails for any reason.


> 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
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
>

[-- Attachment #1.2: Type: text/html, Size: 3329 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2022-04-11  8:52 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
2022-04-11  8:44           ` Michael J Gruber [this message]
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='CAA19uiRLSSZWm_xN=5uqieLFoCkqCuOM7b-c1-Qp45aY2T4RLg@mail.gmail.com' \
    --to=git@grubix.eu \
    --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).