From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] [PATCH] Require gpgme 1.0.8 (v2 breaks API)
Date: Tue, 29 Nov 2011 23:20:39 +0000 [thread overview]
Message-ID: <1322608753-sup-6359@stapelberg.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 160 bytes --]
Hi,
The latest version of gpgme breaks its API. Pragmatic fix for now is requiring
the old version.
Hamish: Is this patch OK with you?
Best regards,
Michael
[-- Attachment #2: 0001-Require-gpgme-1.0.8-v2-breaks-API.patch --]
[-- Type: application/octet-stream, Size: 934 bytes --]
From cdbe24aa7df7021b1a342cd742167583248f2792 Mon Sep 17 00:00:00 2001
From: Michael Stapelberg <michael@stapelberg.de>
Date: Tue, 29 Nov 2011 23:18:34 +0000
Subject: [PATCH] Require gpgme 1.0.8 (v2 breaks API)
---
bin/sup | 2 ++
lib/sup/crypto.rb | 2 ++
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/bin/sup b/bin/sup
index ad7a0d1..a1a88b6 100755
--- a/bin/sup
+++ b/bin/sup
@@ -12,6 +12,8 @@ end
no_gpgme = false
begin
+ # gpgme broke its API in 2.0, so make sure we have the old version for now.
+ gem 'gpgme', '=1.0.8'
require 'gpgme'
rescue LoadError
no_gpgme = true
diff --git a/lib/sup/crypto.rb b/lib/sup/crypto.rb
index bc96f88..9452c73 100644
--- a/lib/sup/crypto.rb
+++ b/lib/sup/crypto.rb
@@ -1,4 +1,6 @@
begin
+ # gpgme broke its API in 2.0, so make sure we have the old version for now.
+ gem 'gpgme', '=1.0.8'
require 'gpgme'
rescue LoadError
end
--
1.7.5.4
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2011-11-29 23:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1322608753-sup-6359@stapelberg.de \
--to=michael+sup@stapelberg.de \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox