From: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
To: 35629@debbugs.gnu.org
Subject: bug#35629: 27.0.50; version-to-list fails on Cygwin gpg2 version string
Date: Wed, 08 May 2019 17:23:48 +0900 [thread overview]
Message-ID: <86mujx9wx7.wl--xmue@d1.dion.ne.jp> (raw)
Cygwin's gpg2 has "-unknown" suffix in version string.
> $ gpg2 --version
>
> gpg (GnuPG) 2.2.15-unknown
> ...
version-to-list function fails to parse this version string and
epg-find-configuration can't find gpg2 as supported one.
(epg-find-configuration 'OpenPGP t)
-> ((program . "/usr/bin/gpg")
(compress 0 1 2 3)
(digestname . "MD5;SHA1;RIPEMD160;SHA256;SHA384;SHA512;SHA224")
(digest 1 2 3 8 9 10 11)
(ciphername . "IDEA;3DES;CAST5;BLOWFISH;AES;AES192;AES256;TWOFISH;CAMELLIA128;CAMELLIA192;CAMELLIA256")
(cipher 1 2 3 4 7 8 9 10 11 12 13)
(pubkey 1 2 3 16 17)
(version . "1.4.23"))
Modifying version-regexp-alist variable resolves the issue.
;; I don't know meaning of "-unknown" version, so I don't know whether
;; "-4" is apropriate value.
(progn (add-to-list 'version-regexp-alist
'("^[-._+ ]?unknown$" . -4))
(epg-find-configuration 'OpenPGP t))
-> ((program . "/usr/bin/gpg2")
(curve . "cv25519;ed25519;nistp256;nistp384;nistp521;secp256k1")
(compressname . "Uncompressed;ZIP;ZLIB;BZIP2")
(compress 0 1 2 3)
(digestname . "SHA1;RIPEMD160;SHA256;SHA384;SHA512;SHA224")
(digest 2 3 8 9 10 11)
(ciphername . "IDEA;3DES;CAST5;BLOWFISH;AES;AES192;AES256;TWOFISH;CAMELLIA128;CAMELLIA192;CAMELLIA256")
(cipher 1 2 3 4 7 8 9 10 11 12 13)
(pubkeyname . "RSA;ELG;DSA;ECDH;ECDSA;EDDSA")
(pubkey 1 16 17 18 19 22)
(version . "2.2.15-unknown"))
--
Kazuhiri Ito
next reply other threads:[~2019-05-08 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:23 Kazuhiro Ito [this message]
2019-05-10 18:26 ` bug#35629: 27.0.50; version-to-list fails on Cygwin gpg2 version string Ken Brown
2019-05-11 8:32 ` Kazuhiro Ito
2019-05-11 21:18 ` Ken Brown
2019-08-26 6:04 ` Lars Ingebrigtsen
2019-08-27 14:50 ` Kazuhiro Ito
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=86mujx9wx7.wl--xmue@d1.dion.ne.jp \
--to=kzhr@d1.dion.ne.jp \
--cc=35629@debbugs.gnu.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.