From: Bengt Richter <bokr@bokr.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 41266@debbugs.gnu.org
Subject: bug#41266: Suggested command to import key does not work on debian
Date: Sun, 17 May 2020 21:48:02 +0200 [thread overview]
Message-ID: <20200517194802.GA5524@LionPure> (raw)
In-Reply-To: <20200517212554.465c0a35@tachikoma.lepiller.eu>
Hi,
On +2020-05-17 21:25:54 +0200, Julien Lepiller wrote:
> Le Thu, 14 May 2020 12:28:11 -0400,
> Julien Lepiller <julien@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.
>
>
>
If the problem is actually expired keys vs nonexistent,
gpg --refresh-keys
might be worth trying.
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2020-05-17 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 16:28 bug#41266: Suggested command to import key does not work on debian Julien Lepiller
2020-05-14 17:27 ` Ricardo Wurmus
2020-05-17 19:25 ` Julien Lepiller
2020-05-17 19:48 ` Bengt Richter [this message]
2020-10-28 17:40 ` zimoun
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=20200517194802.GA5524@LionPure \
--to=bokr@bokr.com \
--cc=41266@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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/guix.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.