GNU bug report logs - #41266
Suggested command to import key does not work on debian

Previous Next

Package: guix;

Reported by: Julien Lepiller <julien <at> lepiller.eu>

Date: Thu, 14 May 2020 16:29:01 UTC

Severity: normal

Done: zimoun <zimon.toutoune <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 41266 <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: 41266 <at> debbugs.gnu.org
Subject: Re: bug#41266: Suggested command to import key does not work on debian
Date: Sun, 17 May 2020 21:25:54 +0200
Le Thu, 14 May 2020 12:28:11 -0400,
Julien Lepiller <julien <at> lepiller.eu> a écrit :

> Hi,
> 
> I just installed a debian VM to test changes in the install script
> and found this issue when running the installer script:
> 
> First it fails because it cannot find the public key and suggests
> running:
> 
> wget … -q0 - | gpg --import
> 
> -q0 does not work with debian's wget, but -O works.
> 
> Aftcr importing the key, the script still complains it cannot find
> it. Re-running the same command with "sudo" in front of the gpg
> import command re-imports the key and the script is then able to find
> it.
> 
> My guess is that the first import imported the key in my user's
> keyring, but the script looks in root's keyring. The second attempt
> added the key to root's keyring.
> 

Forget the wget thing, it's my fault for not reading it properly. The
gpg command still needs to be run with sudo on at least fedora and
debian.




This bug report was last modified 4 years and 202 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.