unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michael J Gruber <git@grubix.eu>
To: "Dan Čermák" <dan.cermak@posteo.net>, notmuch@notmuchmail.org
Subject: Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Date: Wed, 19 May 2021 11:05:11 +0200	[thread overview]
Message-ID: <162141511110.6266.13153591915211986004.git@grubix.eu> (raw)
In-Reply-To: <87r1i3gmu0.fsf@cgc-instruments.com>

Dan Čermák venit, vidit, dixit 2021-05-19 10:16:39:
> Hi list,
> 
> notmuch 0.32 recently stopped building on openSUSE Leap and Tumbleweed
> due to failures in the test suite. It now consistently fails in
> T356-protected-headers:
> 
>  FAIL   verify signed PKCS#7 subject (multipart-signed) signer User ID
>         sig_uid: object not found: data[0][0][0]["crypto"]["signed"]["status"][0]["userid"]
>  PASS   verify signed PKCS#7 subject (onepart-signed)
>  FAIL   verify signed PKCS#7 subject (onepart-signed) signer User ID
>         sig_uid: object not found: data[0][0][0]["crypto"]["signed"]["status"][0]["userid"]
>  PASS   confirm signed and encrypted PKCS#7 subject (sign+enc)
>  FAIL   confirm signed and encrypted PKCS#7 subject (sign+enc) signer User ID
>         sig_uid: object not found: data[0][0][0]["crypto"]["signed"]["status"][0]["userid"]
>  PASS   confirm signed and encrypted PKCS#7 subject (sign+enc+legacy-disp)
>  FAIL   confirm signed and encrypted PKCS#7 subject (sign+enc+legacy-disp) signer User ID
>         sig_uid: object not found: data[0][0][0]["crypto"]["signed"]["status"][0]["userid"]
> 
> 
> Unfortunately, I don't really know what the issue at hand is and how to
> debug it. If anyone could help me out here, I'd be very grateful. I have
> attached a Dockerfile that you can use to reproduce this issue (simply
> build it using your favorite container build tool, e.g.
> `buildah bud --layers --build-arg NOTMUCH_VERSION=0.32`). Note that in
> the container build additional tests fail in contrast to building the
> rpm.

I'm no docker guy, sorry. But the failures indicate that the output of
signature verification changed (unless local variables stopped being
local;) ). Can you check whether

notmuch show --decrypt=true --format=json "id:smime-${variant}@protected-headers.example"

for one of the variants (such as sign+enc) gives proper output but
misses sig_uid? You would have to that with
GNUPGHOME="${TEST_TMPDIR}/gnupg" etc.

Maybe gpgsm's output changed?

Michael

  reply	other threads:[~2021-05-19  9:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  8:16 Test failures with notmuch 0.32 and 0.32.1 on openSUSE Dan Čermák
2021-05-19  9:05 ` Michael J Gruber [this message]
2021-05-19 11:00 ` David Bremner
2021-05-20  6:10   ` Dan Čermák
2021-05-20  9:59     ` David Bremner
2021-05-20 14:16       ` Michael J Gruber
2021-05-20 14:30         ` Dan Čermák
2021-05-20 14:46           ` Michael J Gruber
2021-05-20 15:05             ` Dan Čermák
2021-05-20 19:54         ` Tomi Ollila
2021-05-20 14:28       ` Dan Čermák
2021-06-05 13:50         ` David Bremner
2021-06-08  8:24           ` Dan Čermák
2021-06-08 13:14             ` David Bremner
2021-06-08 14:13               ` Dan Čermák
2021-06-08 14:51                 ` David Bremner
2021-08-28 15:20                 ` 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=162141511110.6266.13153591915211986004.git@grubix.eu \
    --to=git@grubix.eu \
    --cc=dan.cermak@posteo.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).