From: Michael Albinus <michael.albinus@gmx.de>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 67012@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#67012: 29.1; epa-sign-file pinentry loopback mode does not work with S/MIME
Date: Sat, 25 Nov 2023 12:40:02 +0100 [thread overview]
Message-ID: <8734wuysbx.fsf@gmx.de> (raw)
In-Reply-To: <ua5r2m6al@gentoo.org> (Ulrich Mueller's message of "Sat, 25 Nov 2023 12:16:50 +0100")
Ulrich Mueller <ulm@gentoo.org> writes:
Hi Ulrich,
> As a workaround, input the passphrase with a GUI-capable pinentry
> program like 'pinentry-gnome' or 'pinentry-qt5'. Alternatively, you
> can use the 'pinentry' package from Emacs 25.
I have no idea what I'm speaking about. However, on GNU ELPA there is
the package pinentry 0.1 from Daiki Ueno <ueno@gnu.org>. Same is for
Emacs 25. Shouldn't we advertise the GNU ELPA package?
However, there are differences. On GNU ELPA, thetr is
--8<---------------cut here---------------start------------->8---
;; Copyright (C) 2015 Free Software Foundation, Inc.
--8<---------------cut here---------------end--------------->8---
In Emacs 25, there is
--8<---------------cut here---------------start------------->8---
;; Copyright (C) 2015-2017 Free Software Foundation, Inc.
--8<---------------cut here---------------end--------------->8---
Looks like the version in Emacs 25 is more up-to-date, although both say
--8<---------------cut here---------------start------------->8---
;; Version: 0.1
--8<---------------cut here---------------end--------------->8---
Shouldn't we upgrade the GNU ELPA version?
Best regards, Michael.
next prev parent reply other threads:[~2023-11-25 11:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 6:56 bug#67012: 29.1; epa-sign-file pinentry loopback mode does not work with S/MIME Ulrich Mueller
[not found] ` <handler.67012.B.169951307615474.ack@debbugs.gnu.org>
2023-11-09 9:46 ` Ulrich Mueller
2023-11-09 11:21 ` Eli Zaretskii
2023-11-09 11:43 ` Ulrich Mueller
2023-11-15 14:02 ` Eli Zaretskii
2023-11-15 15:07 ` Michael Albinus
2023-11-15 15:32 ` Michael Albinus
2023-11-15 16:48 ` Eli Zaretskii
2023-11-15 17:13 ` Michael Albinus
2023-11-16 9:54 ` Ulrich Mueller
2023-11-17 11:40 ` Ulrich Mueller
2023-11-19 5:43 ` Eli Zaretskii
2023-11-19 11:13 ` Ulrich Mueller
2023-11-25 9:53 ` Eli Zaretskii
2023-11-25 11:16 ` Ulrich Mueller
2023-11-25 11:40 ` Michael Albinus [this message]
2023-11-25 12:17 ` Ulrich Mueller
2023-11-25 14:59 ` Ulrich Mueller
2023-11-25 15:44 ` Michael Albinus
2023-11-25 16:32 ` Ulrich Mueller
2023-11-25 12:27 ` Eli Zaretskii
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=8734wuysbx.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=67012@debbugs.gnu.org \
--cc=eliz@gnu.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 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).