From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Konrad Hinsen <konrad.hinsen@fastmail.net>,
zimoun <zimon.toutoune@gmail.com>,
guix-science@gnu.org
Subject: Re: Help! I messed up guix-past
Date: Sun, 11 Sep 2022 18:19:31 +0300 [thread overview]
Message-ID: <Yx38gzNl1kZsftKu@3900XT> (raw)
In-Reply-To: <87h71eypfo.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
On Sun, Sep 11, 2022 at 04:07:55PM +0200, Ludovic Courtès wrote:
> Hi,
>
> Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
>
> > I spent a lot of time on this problem, and reached the conclusion that
> > it's the existence of two different versions of GnuPG that causes the
> > trouble. GnuPG then picks up the wrong version of gpg-agent, discovers a
> > version mismatch, and gives up on password checking. A rather strange
> > way to handle security!
>
> Ah, in that case that’s a different problem.
>
> I remember there were issues along these lines at the time GnuPG 2.2 (?)
> was released and the previous major version was still around, but that
> was quite some time ago.
>
> I don’t have the solution off the top if my head, but there ought to be
> one; maybe having PATH consistently prefer either Guix’s profile or
> Ubuntu would help?
>
> Maybe we’ll improvise a GPG debugging sessions in Paris next week, who
> knows? ;-)
Ah yes, needing to be explicit about using Guix's gnupg or the host's
gnupg and not mixing the two. I've run into that problem before with
Guix on foreign-distro.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-11 15:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:16 Help! I messed up guix-past Konrad Hinsen
2022-09-09 15:36 ` Ricardo Wurmus
2022-09-09 15:46 ` zimoun
2022-09-09 16:10 ` Konrad Hinsen
2022-09-09 17:39 ` zimoun
2022-09-10 7:39 ` Konrad Hinsen
2022-09-10 9:47 ` zimoun
2022-09-10 16:20 ` Konrad Hinsen
2022-09-11 14:07 ` Ludovic Courtès
2022-09-11 15:19 ` Efraim Flashner [this message]
2022-09-12 6:16 ` Konrad Hinsen
2022-09-12 15:26 ` Ludovic Courtès
2022-09-13 8:58 ` Konrad Hinsen
2022-09-13 9:23 ` Ricardo Wurmus
2022-09-14 9:31 ` Konrad Hinsen
2022-09-10 10:27 ` Ludovic Courtès
2022-09-10 10:40 ` zimoun
2022-09-10 14:39 ` Ricardo Wurmus
2022-09-12 16:00 ` zimoun
2022-09-09 16:16 ` Julien Lepiller
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yx38gzNl1kZsftKu@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-science@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.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.
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).