From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] [PATCH] Start gpg with LC_MESSAGES=C
Date: Fri, 19 Mar 2010 19:53:04 +0100 [thread overview]
Message-ID: <1269024593-sup-9101@midna.zekjur.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 170 bytes --]
Hi,
attached you find a patch which ensures that LC_MESSAGES=C is set when starting
gpg so that the regexps for interpreting the gpg output work.
Best regards,
Michael
[-- Attachment #2: 0001-Use-LC_MESSAGES-C-when-starting-gpg-so-that-the-rege.patch --]
[-- Type: application/octet-stream, Size: 813 bytes --]
From 78a452c8701bec4371e0f361246ecf6413e6148e Mon Sep 17 00:00:00 2001
From: Michael Stapelberg <michael@stapelberg.de>
Date: Fri, 19 Mar 2010 19:52:04 +0100
Subject: [PATCH] Use LC_MESSAGES=C when starting gpg so that the regexps for parsing the output works
---
lib/sup/crypto.rb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/sup/crypto.rb b/lib/sup/crypto.rb
index 5ece6d9..a5ce680 100644
--- a/lib/sup/crypto.rb
+++ b/lib/sup/crypto.rb
@@ -194,7 +194,7 @@ private
def run_gpg args, opts={}
args = HookManager.run("gpg-args", { :args => args }) || args
- cmd = "#{@cmd} #{args}"
+ cmd = "LC_MESSAGES=C #{@cmd} #{args}"
if opts[:interactive] && BufferManager.instantiated?
output_fn = Tempfile.new "redwood.output"
output_fn.close
--
1.6.5
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2010-03-19 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 18:53 Michael Stapelberg [this message]
2010-03-28 21:36 ` Rich Lane
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=1269024593-sup-9101@midna.zekjur.net \
--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