After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 404081 - GPG2 Support
GPG2 Support
Status: RESOLVED DUPLICATE of bug 375062
Product: seahorse
Classification: Applications
Component: general
0.9.10
Other All
: Normal enhancement
: 1.0.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2007-02-03 21:32 UTC by Gilles Dartiguelongue
Modified: 2007-02-03 21:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
seahorse-0.9.10-configure.patch (1.75 KB, patch)
2007-02-03 21:33 UTC, Gilles Dartiguelongue 		none Details | Review
seahorse-0.9.10-libseahorse.patch (570 bytes, patch)
2007-02-03 21:34 UTC, Gilles Dartiguelongue 		none Details | Review

Description Gilles Dartiguelongue 2007-02-03 21:32:20 UTC 
At gentoo, we have bug https://bugs.gentoo.org/show_bug.cgi?id=128780 which is for tracking seahorse releases until next stable branch. It appears that gnupg-2 has been released and seahorse can't use it since its configure and one file limits seahorse the 1.x series.

Including patches in a minute
Comment 1 Gilles Dartiguelongue 2007-02-03 21:33:03 UTC 
Created attachment 81834 [details] [review]
seahorse-0.9.10-configure.patch

Patch that enables seahorse to detect gnupg-2.x
Comment 2 Gilles Dartiguelongue 2007-02-03 21:34:31 UTC 
Created attachment 81835 [details] [review]
seahorse-0.9.10-libseahorse.patch

Patch that enable libseahorse to use gnupg-2.x

I've been using those patches since seahorse-0.9.10 release with gnupg-2.0.1 and I've seen no problem with them.
Comment 3 Adam Schreiber 2007-02-03 21:54:16 UTC 
Gilles,

I've been looking at a similar patch from Alon Bar-Lev also of Gentoo.  It's been attached to bug #375062.  Could you comment if there's anything missing from it that your's includes?

I'm going to mark this bug as a duplicate of the other so that  we can keep this conversation in one place.

*** This bug has been marked as a duplicate of 375062 ***