unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: help-gnu-emacs@gnu.org, Philip Kaludercic <philipk@posteo.net>,
	Eli Zaretskii <eliz@gnu.org>
Subject: Re: problems importing keys via epa-search-keys
Date: Sat, 11 Mar 2023 08:05:52 +0100	[thread overview]
Message-ID: <87a60jwywf.fsf@xelera.eu> (raw)
In-Reply-To: <m2edpwrz6k.fsf@fastmail.fm>

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

Hi Filipp,

Filipp Gunbin <fgunbin@fastmail.fm> writes:

> On 09/03/2023 08:14 +0100, Giovanni Biscuolo wrote:

[...]

>> if I "M-x epa-search-keys" and try to fetch a key with =f= and then =x=
>> in =Key search= buffer, I get this in *Messages*:

[...]

>> but the key is never imported in my gnupg keyring.

[...]

> Yes, broken since 23b6cd41f55b833e8a562c51642d36b5211a510b, the patch is
> below.

Thanks a lot!

I'm using Guix so I'll try to apply your patch for Emacs 28.2 to that
package and submit it for inclusion in official Guix distribution.

AFAIU there's no bug report for this, or am I wrong?  In case there
isn't one I'm going to submit a new bug report.

> Eli, would this be OK for emacs-29?  This is clearly a regression.

[...]

Happy hacking!  Gio'.

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2023-03-11  7:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09  7:14 problems importing keys via epa-search-keys Giovanni Biscuolo
2023-03-10 22:58 ` Filipp Gunbin
2023-03-11  7:05   ` Giovanni Biscuolo [this message]
2023-03-11 22:10     ` Filipp Gunbin
2023-03-12  9:32       ` Giovanni Biscuolo
2023-03-11  7:17   ` Eli Zaretskii
2023-03-11 23:04     ` Filipp Gunbin
2023-03-12  6:33       ` Eli Zaretskii
2023-03-13 12:37         ` Filipp Gunbin
2023-03-13 14:43           ` Eli Zaretskii
2023-03-13 17:40             ` Filipp Gunbin

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=87a60jwywf.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=eliz@gnu.org \
    --cc=fgunbin@fastmail.fm \
    --cc=help-gnu-emacs@gnu.org \
    --cc=philipk@posteo.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.
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).