From: Daiki Ueno <ueno@gnu.org>
To: npostavs@users.sourceforge.net
Cc: 23619@debbugs.gnu.org
Subject: bug#23619: Some epg tests fail
Date: Tue, 21 Feb 2017 11:43:04 +0100 [thread overview]
Message-ID: <od14lznhljb.fsf-ueno@gnu.org> (raw)
In-Reply-To: <87o9xwiv7e.fsf@users.sourceforge.net> (npostavs's message of "Mon, 20 Feb 2017 13:16:37 -0500")
npostavs@users.sourceforge.net writes:
> Daiki Ueno <ueno@gnu.org> writes:
>
>> npostavs@users.sourceforge.net writes:
>>
>>> Although this doesn't solve the problem for gpg 2.0.
>>
>> For a proper fix, you might want to check how GPGME and its test suites
>> do.
>
> I don't see anything to handle gpg 2.0, specifically. They do disable
> pinentry for versions below 2.1. Maybe their tests don't work with 2.0
> either?
It sounds unlikely to me that they don't work with 2.0, because 2.0
support has been there for a decade.
If I understand correctly their tests use their own pinentry program for
2.0 and 2.1:
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=blob;f=tests/gpg/pinentry
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=blob;f=tests/gpg/Makefile.am;h=8e26a92f0c54ce3c76e63e223ce034dea11d6e71;hb=HEAD#l115
If your goal is to make epg tests work with all gpg versions, this could
be an option worth considering.
next prev parent reply other threads:[~2017-02-21 10:43 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=od14lznhljb.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).