Bug 725369 - [PATCH] gnupg2 (and rpm-sign) broken with libgcrypt 1.5.0
Summary: [PATCH] gnupg2 (and rpm-sign) broken with libgcrypt 1.5.0
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnupg2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-25 10:34 UTC by Paul Howarth
Modified: 2011-07-26 10:45 UTC (History)
4 users (show)

Fixed In Version: gnupg-2.0.17-2.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-26 10:45:04 UTC
Type: ---

Attachments (Terms of Use)
Upstream fix for libgcrypt 1.5.0 compatibility (1.01 KB, patch)
2011-07-25 10:34 UTC, Paul Howarth 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.