From: Julius Schwartzenberg <julius.schwartzenberg@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 60207@debbugs.gnu.org
Subject: bug#60207: Bug report
Date: Sun, 25 Dec 2022 16:35:34 +0100 [thread overview]
Message-ID: <f5c50fb2-4b82-2953-c3de-d5fea1100217@gmail.com> (raw)
In-Reply-To: <87tu1kzdi3.fsf@pelzflorian.de>
Hi Florian,
Op 24-12-2022 om 22:40 schreef pelzflorian (Florian Pelz):
>> […]
>> Is there a way to enforce only binaries are fetched and compilation is
>> never attempted? Even if that means I might not always run the latest
>> version?
>
> Yes there is a way. Look at the output from `guix weather` (see
> <https://guix.gnu.org/en/manual/devel/en/html_node/Invoking-guix-weather.html>
> in the English manual); if substitute coverage is bad, you could wait a
> few days or maybe look at `guix build --log-file` if compilation fails
> at the build farm (see
> <https://guix.gnu.org/en/manual/devel/en/html_node/Additional-Build-Options.html>).
>
> If you want `guix pull` without compiling, then look at
> <https://guix.gnu.org/en/manual/devel/en/html_node/Channels-with-Substitutes.html>.
I added the lines to my personal .config/guix/channels.scm, but guix
pull then shows:
guix pull: waarschuwing: could not find available substitutes at
https://ci.guix.gnu.org
And it still ends up compiling. I also tried replacing ci with bordeaux
in the URL, but then it shows a 404.
I think I'm still missing something?
Best regards,
Julius
next prev parent reply other threads:[~2022-12-25 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 17:48 bug#60207: Bug report Julius Schwartzenberg
2022-12-20 9:34 ` pelzflorian (Florian Pelz)
2022-12-20 19:51 ` Julius Schwartzenberg
2022-12-21 15:26 ` pelzflorian (Florian Pelz)
2022-12-23 20:00 ` Julius Schwartzenberg
2022-12-24 21:40 ` pelzflorian (Florian Pelz)
2022-12-25 15:35 ` Julius Schwartzenberg [this message]
2022-12-26 12:09 ` bug#60207: ci build of latest guix for armhf pelzflorian (Florian Pelz)
2022-12-28 18:14 ` 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=f5c50fb2-4b82-2953-c3de-d5fea1100217@gmail.com \
--to=julius.schwartzenberg@gmail.com \
--cc=60207@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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.