all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com> (by way of Jesse Gibbons <jgibbons2357@gmail.com>)
To: "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#36051: "guix import gnu" says public key is not in keyring
Date: Sun, 2 Jun 2019 12:43:56 -0600	[thread overview]
Message-ID: <20190602124356.2202614c@gmail.com> (raw)
In-Reply-To: <87tvd87yoz.fsf@gnu.org>

On Sun, 02 Jun 2019 18:13:16 +0200
Ludovic Courtès <ludo@gnu.org> wrote:

> Hi,
> 
> Jesse Gibbons <jgibbons2357@gmail.com> skribis:
> 
> > Starting download of /tmp/guix-file.cZoC7H
> > From ftp://ftp.gnu.org/gnu/gnurobots/gnurobots-1.2.0.tar.gz.sig...
> >  ….0.tar.gz.sig  72B                  170KiB/s 00:00
> > [##################] 100.0% In execvp of gpgv: No such file or
> > directory  
> 
> The real issue here is that ‘gpgv’ cannot be found in $PATH.
> 
> I think you have to run “guix install gnupg” to fix it.
> 
> HTH,
> Ludo’.

I pointed that out at the end of my bug report. I thought guix was
supposed to be stateless, with behavior independent on what the user has
installed, so I recommended adding gnupg as a propagated input so it
wouldn't be dependant on a user (or administrator) installing gnupg.
If it is preferrable not to install gnupg alongside guix, then I will
note in the docs that gnupg must be found in $PATH for "guix import
gnu", "guix import elpa" and "guix refresh" to be successful, and then
we can close this issue.

Thanks,
-Jessez

  reply	other threads:[~2019-06-02 23:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-02  3:33 bug#36051: "guix import gnu" says public key is not in keyring Jesse Gibbons
2019-06-02 16:13 ` Ludovic Courtès
2019-06-02 18:43   ` Jesse Gibbons [this message]
2019-09-02 19:41     ` Ludovic Courtès

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=20190602124356.2202614c@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=ludo@gnu.org \
    /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.