From: Daiki Ueno <ueno@gnu.org>
To: npostavs@users.sourceforge.net
Cc: 23619@debbugs.gnu.org
Subject: bug#23619: Some epg tests fail
Date: Sun, 19 Feb 2017 19:34:39 +0100 [thread overview]
Message-ID: <87bmtyjagw.fsf-ueno@gnu.org> (raw)
In-Reply-To: <878tp2jhpr.fsf@users.sourceforge.net> (npostavs's message of "Sun, 19 Feb 2017 10:58:08 -0500")
npostavs@users.sourceforge.net writes:
> tags 23619 patch
> quit
>
> Glenn Morris <rgm@gnu.org> writes:
>
>> Two epg tests fail for me on RHEL 7.2 with current master (and have done
>> since they stopped being skipped).
>>
>> gpg --version
>> gpg (GnuPG) 2.0.22
>> libgcrypt 1.5.3
>
>> 2 unexpected results:
>> FAILED epg-decrypt-1
>> FAILED epg-roundtrip-1
>
> I have
>
> gpg --version
> gpg (GnuPG) 2.1.18
> libgcrypt 1.7.6
>
> These tests popup a dialog box to enter a passphrase before failing.
> The following patch which sets pinentry mode to 'loopback' fixes it for
> me (I have not tested with other gpg versions though):
Thank you. That sounds like a good idea, but the version actually
matters: gpg 1.x and 2.0.x refuse the --pinentry-mode option and exit
abnormally...
Maybe you could add a version check around the call (or in epg--start)?
epg-config.el provides a few functions to do that.
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2017-02-19 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 17:01 bug#23619: Some epg tests fail Glenn Morris
2017-02-19 15:58 ` npostavs
2017-02-19 18:34 ` Daiki Ueno [this message]
2017-02-19 20:35 ` npostavs
2017-02-20 8:39 ` Daiki Ueno
2017-02-20 16:04 ` npostavs
2017-02-20 16:15 ` Daiki Ueno
2017-02-20 18:16 ` npostavs
2017-02-21 10:43 ` Daiki Ueno
2017-02-22 2:05 ` npostavs
2017-02-24 9:25 ` Daiki Ueno
2017-03-01 1:01 ` npostavs
2017-03-01 23:47 ` Glenn Morris
2017-03-02 0:17 ` npostavs
2017-03-03 17:57 ` Glenn Morris
2017-03-03 18:37 ` Glenn Morris
2017-03-04 4:53 ` npostavs
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=87bmtyjagw.fsf-ueno@gnu.org \
--to=ueno@gnu.org \
--cc=23619@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.