unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: OBS substitutes
Date: Tue, 21 Sep 2021 22:08:33 +0100	[thread overview]
Message-ID: <877df9y6om.fsf@cbaines.net> (raw)
In-Reply-To: <86y27rc4lf.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4575 bytes --]


zimoun <zimon.toutoune@gmail.com> writes:

> I am confused because using Guix fb32a38, I get:
>
> $ guix weather obs
> computing 1 package derivations for x86_64-linux...
> looking for 1 store items on https://ci.guix.gnu.org...
> https://ci.guix.gnu.org
>   0.0% substitutes available (0 out of 1)
>   unknown substitute sizes
>   0.0 MiB on disk (uncompressed)
>
>   0.0% (0 out of 1) of the missing items are queued
>   at least 1,000 queued builds
>       powerpc64le-linux: 999 (99.9%)
>       i686-linux: 1 (.1%)
>   build rate: .00 builds per hour
>       powerpc64le-linux: 0.00 builds per hour
>       x86_64-linux: 0.00 builds per hour
>       i686-linux: 0.00 builds per hour
>       aarch64-linux: 0.00 builds per hour
> looking for 1 store items on https://bordeaux.guix.gnu.org...
> https://bordeaux.guix.gnu.org
>   100.0% substitutes available (1 out of 1)
>   4.0 MiB of nars (compressed)
>   15.2 MiB on disk (uncompressed)
>   (continuous integration information unavailable)
>
>
> well, I do not understand why it is not on Berlin.  But why not.  Then,
>
> $ guix build obs -n
> The following derivations would be built:
>    /gnu/store/iz6yxr0jz312xz6494zc9wwv3w2lxzs5-obs-27.0.1.drv
>    /gnu/store/s4yg1apy5m3l2scqbd2v27bcs07c1b5j-obs-27.0.1.tar.xz.drv
>    /gnu/store/i9r2gwiqqr3ggyf63ad3k6ardiv68w1c-obs-27.0.1-checkout.drv
>
>
> Hum, I am confused why Guix wants to build from source when it is
> available on Bordeaux.  I have checked my config, but why not if I
> miss something.  Explicitly,
>
> $ guix build obs --substitute-urls="https://bordeaux.guix.gnu.org"
> The following derivations will be built:
>    /gnu/store/iz6yxr0jz312xz6494zc9wwv3w2lxzs5-obs-27.0.1.drv
>    /gnu/store/s4yg1apy5m3l2scqbd2v27bcs07c1b5j-obs-27.0.1.tar.xz.drv
>    /gnu/store/i9r2gwiqqr3ggyf63ad3k6ardiv68w1c-obs-27.0.1-checkout.drv
> building /gnu/store/i9r2gwiqqr3ggyf63ad3k6ardiv68w1c-obs-27.0.1-checkout.drv...
> guile: warning: failed to install locale
> environment variable `PATH' set to `/gnu/store/v6f44zccwh9z5zk3pjlywjybbi8n2hjh-tar-1.32/bin:/gnu/store/ncydgq2znms5n1d2k5yqshhf58nsixwv-gzip-1.10/bin:/gnu/store/i8h2pcxqdq07ijm3ibkka8f4smn1w48v-bzip2-1.0.8/bin:/gnu/store/9860f1abqj8wjjnwl8a9v54pdcc3bhgf-xz-5.2.4/bin:/gnu/store/60g7r3l01fd7c58yjbm6krgcwj1jkpwg-file-5.38/bin:/gnu/store/n4n560pfvvw50a9369axw5vj5rrqfj1n-diffutils-3.7/bin:/gnu/store/cd5qf3kcnlq35p9k392pjdpdzpsnds70-patch-2.7.6/bin:/gnu/store/hic7snhayfl7m6cpfqqr73nmm19bpqkg-findutils-4.7.0/bin:/gnu/store/swqdvwri9dbv6zssg6v0by7l05hd6wxp-gawk-5.0.1/bin:/gnu/store/ishk7fswcs4gkwcp8mh788z4mvvl9bxh-sed-4.8/bin:/gnu/store/bhs4rj58v8j1narb2454raan2ps38xd8-grep-3.4/bin:/gnu/store/57xj5gcy1jbl9ai2lnrqnpr0dald9i65-coreutils-8.32/bin:/gnu/store/hm40bxnv8jxmbc1lpb7zfimii4xm9m81-make-4.3/bin:/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin:/gnu/store/mpa04aq8lblbcviyxywxcsb1zbi0mf39-ld-wrapper-0/bin:/gnu/store/m1z7cdbqsqyp9xnjw5cvlb4a7gkcg3m4-binutils-2.34/bin:/gnu/store/rn75fm7adgx3pw5j8pg3bczfqq1y17lk-gcc-7.5.0/bin:/gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/bin'
> hint: Using 'master' as the name for the initial branch. This default branch name
> hint: is subject to change. To configure the initial branch name to use in all
> hint: of your new repositories, which will suppress this warning, call:
> hint: 
> hint: 	git config --global init.defaultBranch <name>
> hint: 
> hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
> hint: 'development'. The just-created branch can be renamed via this command:
> hint: 
> hint: 	git branch -m <name>
> Initialized empty Git repository in /gnu/store/86x4q8w68984r6n4j0wl00zw1zq8xy96-obs-27.0.1-checkout/.git/
>   C-c C-c
>
> Why?  How is it possible that “guix weather” reports that the
> substitute is available but then “guix build” does not fetch it?

guix weather just looks whether there's a substitute.

When you run guix build, that substitute will only be used if it's
signed by a key that is in your ACL. My guess here is that this isn't
the case.

On Guix Systems, if the substitute keys are left as the default, for
recent revisions of Guix, the bordeaux.guix.gnu.org signing key will be
included in the ACL by default. With Guix on foreign distributions, it
needs adding manually.

I think there's some room for improvement in the UI/UX here, in terms of
telling users that there are substitutes available, if they trust a
specific key (all the relevant information is in the narinfo).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  parent reply	other threads:[~2021-09-21 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 21:35 OBS substitutes zimoun
2021-09-21  8:51 ` Mathieu Othacehe
2021-09-21  9:25   ` zimoun
2021-09-21 21:08 ` Christopher Baines [this message]
2021-09-21 21:21   ` Mathieu Othacehe

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=877df9y6om.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).