From: Lars Ingebrigtsen <larsi@gnus.org>
To: Toon Claes <toon@iotcl.com>
Cc: 26298@debbugs.gnu.org,
Noam Postavsky <npostavs@users.sourceforge.net>,
Torsten Bronger <bronger@physik.rwth-aachen.de>
Subject: bug#26298: 26.0.50; Gnus fails to sign mail with PGP
Date: Sat, 14 Apr 2018 15:12:30 +0200 [thread overview]
Message-ID: <87h8oej5j5.fsf@mouse.gnus.org> (raw)
In-Reply-To: <m2po32s2jh.fsf@iotcl.com> (Toon Claes's message of "Sat, 14 Apr 2018 08:52:18 +0200")
Toon Claes <toon@iotcl.com> writes:
> I've built 20c6a516ec (which contains ef2059e877), and now I'm getting
> "Signature failed" whenever I'm trying to sign an email. Independent if
> my passphrase was correct or not. As a matter of fact, it no longer
> giving me the possibility to fill in my passphrase in the minibuffer.
OK, I'll revert that patch.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-04-14 13:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 12:15 bug#26298: 26.0.50; Gnus fails to sign mail with PGP Torsten Bronger
2017-08-14 20:33 ` Toon Claes
2017-08-14 21:19 ` Toon Claes
2017-08-14 23:46 ` npostavs
2017-08-15 5:54 ` Toon Claes
2017-08-15 15:23 ` Noam Postavsky
2018-01-28 19:39 ` Toon Claes
2018-01-28 21:23 ` Noam Postavsky
2018-04-11 22:06 ` Lars Ingebrigtsen
2018-04-12 7:25 ` Noam Postavsky
2018-04-12 11:37 ` Lars Ingebrigtsen
2018-04-12 12:45 ` Noam Postavsky
2018-04-14 6:52 ` Toon Claes
2018-04-14 13:12 ` Lars Ingebrigtsen [this message]
2018-04-14 13:36 ` Toon Claes
2018-04-14 13:54 ` Lars Ingebrigtsen
2018-04-14 13:15 ` Lars Ingebrigtsen
2018-04-29 14:38 ` Noam Postavsky
2018-05-17 23:41 ` Noam Postavsky
2018-05-18 9:55 ` Basil L. Contovounesios
2018-05-18 13:38 ` Noam Postavsky
2018-05-23 23:09 ` Noam Postavsky
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=87h8oej5j5.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=26298@debbugs.gnu.org \
--cc=bronger@physik.rwth-aachen.de \
--cc=npostavs@users.sourceforge.net \
--cc=toon@iotcl.com \
/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.