From: "Ludovic Courtès" <ludo@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Bringing substitutes from the Guix Build Coordinator to users
Date: Thu, 06 May 2021 18:26:44 +0200 [thread overview]
Message-ID: <87czu3esl7.fsf@gnu.org> (raw)
In-Reply-To: <YJGUrLK2srmSoRob@jurong> (Andreas Enge's message of "Tue, 4 May 2021 20:38:36 +0200")
Hallo!
Andreas Enge <andreas@enge.fr> skribis:
> Relatedly, and this may already be documented: How do I know where the
> packages are downloaded from?
> $ guix package -u
> substitute: updating substitutes from 'https://bayfront.guix.info'... 100.0%
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
> imagemagick-6.9.12-4-doc 4.6MiB 1.6MiB/s 00:01 [##### ] 32.5%
> Before the print format overhaul, the full URL would be printed.
You can use ‘-v2’ to see URLs:
https://guix.gnu.org/manual/devel/en/html_node/Common-Build-Options.html
> Does the guix daemon complain when substitute URLs do not match any
> authorised key?
No, it just ignores it.
Ludo’.
next prev parent reply other threads:[~2021-05-06 16:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 18:56 Bringing substitutes from the Guix Build Coordinator to users Christopher Baines
2021-05-02 21:51 ` Ludovic Courtès
2021-05-03 10:30 ` Christopher Baines
2021-05-04 8:27 ` Ludovic Courtès
2021-05-04 19:22 ` Christopher Baines
2021-05-11 20:18 ` Ludovic Courtès
2021-05-04 18:38 ` Andreas Enge
2021-05-04 19:29 ` Christopher Baines
2021-05-12 22:58 ` Christopher Baines
2021-05-15 16:38 ` Ludovic Courtès
2021-05-15 17:24 ` Christopher Baines
2021-05-17 20:28 ` Ludovic Courtès
2021-05-18 8:26 ` Christopher Baines
2021-05-06 16:26 ` Ludovic Courtès [this message]
2021-05-18 19:45 ` [bug#48435] " Christopher Baines
2021-05-18 21:24 ` Ludovic Courtès
2021-05-18 22:29 ` Christopher Baines
2021-05-19 6:54 ` Mathieu Othacehe
2021-05-19 7:57 ` Christopher Baines
2021-06-07 14:53 ` Christopher Baines
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=87czu3esl7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@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.