From: Leo Famulari <leo@famulari.name>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: successful installation, but problems updating
Date: Fri, 10 Nov 2017 11:28:18 -0500 [thread overview]
Message-ID: <20171110162818.GA11031@jasmine.lan> (raw)
In-Reply-To: <87fu9mptdl.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2509 bytes --]
> Thomas Sigurdsen <thomas.sigurdsen@gmail.com> writes:
>
> >> Secondly, I noted that with, e.g., 'guix package -i kodi' software gets
> >> compiled. I understood that GNU Guix is capable of both binary and
> >> source packages. Which should I typically expect? Can I choose?
Guix is a build-from-source system that can transparently download
pre-compiled binary "substitutes" when they are available, and when this
substitution method has been authorized by the user. On GuixSD, it's
authorized by default. Here's the documentation of substitution:
https://www.gnu.org/software/guix/manual/guix.html#Substitutes
If your Guix is relatively up to date [0], you've authorized a
substitute server, and you can connect to the European internet, then
most things will be substituted. But usually there will be a few things
to build from source anyways.
You can choose to never use substitutes by de-authorizing all substitute
signing keys [1] or by passing --no-substitutes to the guix-daemon or
any of the commands that build things [2].
Since Guix is ultimately a build-from-source system, there is currently
no way to disable building from source.
[...]
On Thu, Nov 09, 2017 at 09:58:30PM -0800, Chris Marusich wrote:
> Anecdotally, I swear I've seen guix build some things from source even
> when I did not specify --fallback. Has anybody else seen that occur?
That's expected. If substitutes are enabled, when running a command that
builds things, Guix asks the substitute servers what can be substituted.
If some thing is not available as a substitute, Guix will build it.
However, if a substitute is reported to be available, but then the
substitution fails for any reason, Guix will stop.
'--fallback' is relevant in this case, and is meant to work around flaky
substitute servers, network connections, etc. The documentation says:
"When substituting a pre-built binary fails, fall back to building
packages locally." [2]
Substition is considered to fail when Guix is expecting a substitute but
the server returns 404, 504, or some other unexpected problem occurs. It
is not considered to fail if the server initially reports that no
substitute is available.
[0] Not more than a few months behind, I'd guess.
[1]
https://www.gnu.org/software/guix/manual/html_node/Invoking-guix-archive.html
[2] --no-substitutes and --fallback are "common build options":
https://www.gnu.org/software/guix/manual/html_node/Common-Build-Options.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-10 16:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 8:16 successful installation, but problems updating Marco van Hulten
2017-11-06 9:43 ` Carlo Zancanaro
2017-11-06 20:06 ` Marco van Hulten
2017-11-07 9:20 ` Ludovic Courtès
2017-11-07 10:58 ` Marco van Hulten
2017-11-08 1:37 ` Marco van Hulten
2017-11-09 7:45 ` Marco van Hulten
2017-11-09 13:19 ` Ludovic Courtès
2017-11-09 19:27 ` Marco van Hulten
2017-11-09 20:46 ` Marco van Hulten
2017-11-09 20:53 ` Mathieu Othacehe
2017-11-10 7:26 ` Marco van Hulten
2017-11-10 16:35 ` Leo Famulari
2017-11-11 22:23 ` Marco van Hulten
2017-11-12 1:26 ` Leo Famulari
2017-11-06 10:18 ` Thomas Sigurdsen
2017-11-10 5:58 ` Chris Marusich
2017-11-10 7:23 ` Carlo Zancanaro
2017-11-10 16:28 ` Leo Famulari [this message]
2017-11-10 23:30 ` Chris Marusich
2017-11-11 15:29 ` myglc2
2017-11-11 17:05 ` Chris Marusich
2017-11-11 18:06 ` myglc2
2017-11-12 1:29 ` Leo Famulari
2017-11-12 3:36 ` myglc2
2017-11-12 4:45 ` Leo Famulari
2017-11-12 11:10 ` Chris Marusich
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=20171110162818.GA11031@jasmine.lan \
--to=leo@famulari.name \
--cc=cmmarusich@gmail.com \
--cc=help-guix@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.