[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 01/02: gnu: gnupg: Update to 2.1.17.
From: |
Marius Bakke |
Subject: |
Re: 01/02: gnu: gnupg: Update to 2.1.17. |
Date: |
Thu, 22 Dec 2016 15:09:17 +0100 |
User-agent: |
Notmuch/0.23.3 (https://notmuchmail.org) Emacs/25.1.1 (x86_64-unknown-linux-gnu) |
Leo Famulari <address@hidden> writes:
> On Thu, Dec 22, 2016 at 02:17:23AM -0500, Mark H Weaver wrote:
>> > gnu: gnupg: Update to 2.1.17.
>> >
>> > * gnu/packages/gnupg.scm (gnupg): Update to 2.1.17.
>>
>> Unfortunately, this new version of gnupg consistently fails its test
>> suite on every system we support except for x86_64:
>
>> The error is always the same:
>>
>> --8<---------------cut here---------------start------------->8---
>> make check-local
>> make[3]: Entering directory
>> '/tmp/nix-build-gnupg-2.1.17.drv-0/gnupg-2.1.17/tests/gpgscm'
>> EXEEXT= GPGSCM_PATH=. \
>> ./gpgscm ./t-child.scm
>> make[3]: *** [Makefile:838: check-local] Segmentation fault
>> --8<---------------cut here---------------end--------------->8---
>>
>> If you can't find a fix quickly, please revert this commit, because
>> several very important packages depend on it.
>
> Upstream discussion:
>
> https://lists.gnupg.org/pipermail/gnupg-devel/2016-December/032364.html
Here is the patch from that thread:
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=6e96cdd41a0e55b672309431062f37c4a4a9f485
It doesn't look like they will do a new release with this fix, so I
pushed the patch as 059b3aa9c335041d947cf2b765ab3dab811cfdc5. It passes
with '--system=i686-linux' on my machine.
signature.asc
Description: PGP signature