unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Leo Famulari <leo@famulari.name>
To: myglc2 <myglc2@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: successful installation, but problems updating
Date: Sat, 11 Nov 2017 20:29:04 -0500	[thread overview]
Message-ID: <20171112012904.GC13886@jasmine.lan> (raw)
In-Reply-To: <86bmk8rfz9.fsf@gmail.com>

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

On Sat, Nov 11, 2017 at 10:29:30AM -0500, myglc2 wrote:
> On 11/10/2017 at 15:30 Chris Marusich writes:
> > Thank you for the clarification.  This is what I did not understand.  I
> > read the manual and got the impression that when --fallback has not been
> > given, if a given substitute cannot be found (regardless of whether or
> > not a substitute server claimed to provide one), then Guix will not
> > build it.  I see now that my understanding was mistaken.
> 
> I had this mistaken impression too.

It's important to remember that Guix is a build-from-source system. The
use of pre-compiled binaries is an optimization made possible by the
functional package model.

> +When substitutes are enabled (the default) and a substitute is not
> +available the build will take place locally. If a substitute is
> +available but substitution fails, e.g., the substitute server returns
> +404, 504, times out, or some other unexpected problem occurs, guix stops
> +and reports an error unless --fallback or --keep-going options are
> +specified.

To clarify, the default status of substitutes is different for Guix
(default disabled) and GuixSD (default enabled).

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

  parent reply	other threads:[~2017-11-12  1:29 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
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 [this message]
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

  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=20171112012904.GC13886@jasmine.lan \
    --to=leo@famulari.name \
    --cc=help-guix@gnu.org \
    --cc=myglc2@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.
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).