From: George Clemmer <myglc2@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37789@debbugs.gnu.org
Subject: bug#37789: guix pull: error: You found a bug: the program
Date: Fri, 18 Oct 2019 10:57:07 -0400 [thread overview]
Message-ID: <cuctv86t83g.fsf@gmail.com> (raw)
In-Reply-To: <87wod3maiy.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> This is not the key of ci.guix.gnu.org.
Thanks for getting back to me. It turns out I mistakenly gave you this
server's public key. SORRY. Also I forgot the system is configured not
to use substitutes ...
(guix-service-type
config =>
(guix-configuration
(inherit config)
(use-substitutes? #f)
(substitute-urls (list "https://mirror.hydra.gnu.org"
"https://hydra.gnu.org"
"https://berlin.guixsd.org"))
(extra-options '("--gc-keep-derivations=yes"
"--gc-keep-outputs=yes"
"--cores=0" "--max-jobs=10"))
))))
... because it primarily builds Guix from Git. I only use 'guix pull' as
a kind of "rescue move" when the souce build fails, as it is now doing
configure: error: Guile-JSON is missing; please install it.
The last time I used 'guix pull' it worked fine ...
/home/glc/.config/guix:
lrwxrwxrwx 1 glc users 44 Dec 14 2018 current ->
/var/guix/profiles/per-user/glc/current-guix
The guix-configuration is unchanged since then. Shouldn't 'guix pull'
still work?
SORRY for the run-around on keys and substitutes.
TIA, George
next prev parent reply other threads:[~2019-10-18 14:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 10:49 bug#37789: guix pull: error: You found a bug: the program my glc2
2019-10-17 14:58 ` Ludovic Courtès
2019-10-17 16:39 ` George Clemmer
2019-10-17 19:34 ` Ludovic Courtès
2019-10-18 14:57 ` George Clemmer [this message]
2019-10-19 19:05 ` Ludovic Courtès
2019-10-19 19:56 ` George Clemmer
2019-10-19 20:09 ` Ludovic Courtès
2019-10-21 21:00 ` George Clemmer
2019-10-21 21:21 ` George Clemmer
2019-10-23 9:59 ` Ludovic Courtès
2019-10-23 13:35 ` George Clemmer
2020-06-09 23:12 ` George Clemmer
2020-06-09 23:40 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-06-10 14:48 ` 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
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=cuctv86t83g.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=37789@debbugs.gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).