all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daiki Ueno <ueno@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 23561@debbugs.gnu.org
Subject: bug#23561: epg tests are (almost) always skipped
Date: Thu, 19 May 2016 10:40:49 +0900	[thread overview]
Message-ID: <m3h9duvn8e.fsf-ueno@gnu.org> (raw)
In-Reply-To: <clzirnxtf3.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 18 May 2016 11:44:16 -0400")

Glenn Morris <rgm@gnu.org> writes:

>> as long as "gpg2" is GnuPG 2.0
>
> epg-config--program-alist requires gpg2 to be in the 2.1 series, so that
> seems a bit contradictory?
>
> If these are tests for gpg v1, could you not bind epg-gpg-program to
> "gpg" in epg-tests-gpg-usable and with-epg-tests (when
> require-passphrase is set)?

The problem is that some distributions rename "gpg2" to "gpg" and it's
not that simple to detect it's v1.  Maybe a better solution would be to
define `epg-config--program-alist' as a normal defvar rather than
defconst, bind it in `with-epg-tests', and find the correct gpg v1
executable.  I'll try to write a patch later today.

Regards,
-- 
Daiki Ueno





  reply	other threads:[~2016-05-19  1:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17  6:29 bug#23561: epg tests are (almost) always skipped Glenn Morris
2016-05-17  8:48 ` Daiki Ueno
2016-05-18 15:44   ` Glenn Morris
2016-05-19  1:40     ` Daiki Ueno [this message]
2016-05-19  9:12       ` Daiki Ueno
2016-05-25 17:07         ` Glenn Morris
2017-06-30  3:38           ` npostavs
2017-07-07  2:10             ` npostavs
2017-07-09 23:34               ` Glenn Morris
2017-07-11  2:04                 ` npostavs
2017-07-23  5:02                   ` npostavs
2018-07-13 12:25           ` Noam Postavsky
2018-07-13 16:54             ` Glenn Morris
2018-07-16 11:29               ` Noam Postavsky
2018-07-24 17:47                 ` Glenn Morris

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=m3h9duvn8e.fsf-ueno@gnu.org \
    --to=ueno@gnu.org \
    --cc=23561@debbugs.gnu.org \
    --cc=rgm@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.