Re: T350 test failures with gnupg-2.1.16

Subject: Re: T350 test failures with gnupg-2.1.16

Date: Tue, 22 Nov 2016 21:12:13 +0100

To: David Bremner, notmuch@notmuchmail.org

Cc:

From: Marius Bakke

David Bremner <david@tethera.net> writes:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Hello!
>>
>> After updating to gnupg 2.1.16, T350-crypto.sh fails in some of the
>> signature verification steps with wrong content-length:
>>
>> T350-crypto: Testing PGP/MIME signature verification and decryption
>>  PASS   emacs delivery of signed message
>>  FAIL   signature verification
>>         --- T350-crypto.2.expected      2016-11-22 18:59:48.341851653 +0000
>>         +++ T350-crypto.2.output        2016-11-22 18:59:48.341851653 +0000
>>         @@ -11,7 +11,7 @@
>>                                          "id": 2
>>                                      },
>>                                      {
>>         -                                "content-length": 280,
>>         +                                "content-length": 312,
>>                                          "content-type": "application/pgp-signature",
>
> These failures are not duplicated for me in debian sid, also with gpg
> 2.1.16. From IRC I believe Marius is running GuixSD.

This is correct. Strange that it's not reproducible on Debian. Any tips
for how to troubleshoot this further? Is the content-length based on
signature only? I'll see if I can extract the raw output somehow.
signature.asc (application/pgp-signature)

Thread: