unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Bringing substitutes from the Guix Build Coordinator to users
Date: Tue, 4 May 2021 20:38:36 +0200	[thread overview]
Message-ID: <YJGUrLK2srmSoRob@jurong> (raw)
In-Reply-To: <878s4ye116.fsf@cbaines.net>

Hello Chris,

Am Sat, May 01, 2021 at 07:56:05PM +0100 schrieb Christopher Baines:
> I think there are some benefits for using the Guix Build Coordinator to
> build things for substitutes, and it would be good to work out how to
> get those benefits to users of Guix generally.

my question is a bit tangential, but how can we get the substitutes that
the build coordinator puts on bayfront? I still have bayfront.guix.info
in my list of substitute servers, but does it use the same signing key
as before? It would be nice to document what a user should do. In my
opinion, a second build farm would be a useful thing, in case one server
goes down, or needs to be updated, for instance. (And then it allows for
reproducibility checks.)

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.

Does the guix daemon complain when substitute URLs do not match any
authorised key?

I know this should probably go to help-guix, but my questions fit the thread ;-)

Andreas



  parent reply	other threads:[~2021-05-04 18:38 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 [this message]
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
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

  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=YJGUrLK2srmSoRob@jurong \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /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).