From: Chong Yidong <cyd@stupidchicken.com>
To: Daiki Ueno <ueno@unixuser.org>
Cc: Ulrich Mueller <ulm@gentoo.org>, emacs-devel@gnu.org
Subject: Re: PGG incompatible with GnuPG >=2.0.10 (patch included)
Date: Thu, 18 Jun 2009 13:51:20 -0400 [thread overview]
Message-ID: <87d491o2g7.fsf@stupidchicken.com> (raw)
In-Reply-To: <19002.29144.70040.780812@a1i15.kph.uni-mainz.de> (Ulrich Mueller's message of "Thu, 18 Jun 2009 18:56:56 +0200")
Ulrich Mueller <ulm@gentoo.org> writes:
>>>>>> On Thu, 18 Jun 2009, Chong Yidong wrote:
>
>>> Unfortunately, PGG expects the user ID in the "pub" line and therefore
>>> fails to parse the new output format. Attached is a patch that fixes
>>> the problem for me.
>
>> Does this patch behave properly for prior versions of GnuPG? Could you
>> test?
>
> Sorry, I forgot to mention this. I've tested it with GnuPG versions
> 2.0.11, 2.0.9, and 1.4.9. It seems to work fine with all of them.
Thanks. I went ahead and checked it in, so that it will be in the
upcoming pretest. Daiki, do you see any problem with the patch?
--- emacs-orig/lisp/pgg-gpg.el
+++ emacs-lisp/pgg-gpg.el
@@ -189,9 +189,9 @@
(let ((args (list "--with-colons" "--no-greeting" "--batch"
(if all "--list-secret-keys" "--list-keys")
string))
- (key-regexp (concat "^\\(sec\\|pub\\)"
+ (key-regexp (concat "^\\(sec\\|pub\\|uid\\)"
":[^:]*:[^:]*:[^:]*:\\([^:]*\\):[^:]*"
- ":[^:]*:[^:]*:[^:]*:\\([^:]*\\):")))
+ ":[^:]*:[^:]*:[^:]*:\\([^:]+\\):")))
(with-temp-buffer
(apply #'call-process pgg-gpg-program nil t nil args)
(goto-char (point-min))
next prev parent reply other threads:[~2009-06-18 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 14:46 PGG incompatible with GnuPG >=2.0.10 (patch included) Ulrich Mueller
2009-06-18 16:13 ` Chong Yidong
2009-06-18 16:56 ` Ulrich Mueller
2009-06-18 17:51 ` Chong Yidong [this message]
2009-06-19 5:42 ` Daiki Ueno
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=87d491o2g7.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=ueno@unixuser.org \
--cc=ulm@gentoo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.