Bug 725369

Summary: [PATCH] gnupg2 (and rpm-sign) broken with libgcrypt 1.5.0
Product: [Fedora] Fedora Reporter: Paul Howarth <paul>
Component: gnupg2Assignee: Rex Dieter <rdieter>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bcl, nalin, rdieter, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnupg-2.0.17-2.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-26 10:45:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Upstream fix for libgcrypt 1.5.0 compatibility none

Description Paul Howarth 2011-07-25 10:34:01 UTC 
Created attachment 515008 [details]
Upstream fix for libgcrypt 1.5.0 compatibility

Description of problem:

Trying to sign rpms following upgrade to libgcrypt 1.5.0, I get:
gpg: pkglue.c:41: mpi_from_sexp: Assertion `data' failed.
error: gpg exec failed (0)

Version-Release number of selected component (if applicable):
gnupg2-2.0.17-1.fc16

I've attached the upstream fix for this, which works for me.
This problem is also reported in debian and ubuntu:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/815190

Upstream mailing list reference:
http://www.gossamer-threads.com/lists/gnupg/gcrypt/55063
Comment 1 Tomas Mraz 2011-07-25 10:46:45 UTC 
I'm currently disputing the API/ABI break that the change to 1.5.0 caused with upstream.
Comment 2 Tomas Mraz 2011-07-25 17:16:27 UTC 
Unfortunately upstream (Werner) does not want to change the default in gcry_sexp_nth_mpi(). And Werner also said that he only found gnupg2 and gnutls to be affected, so I am going to patch these two packages.