From: myglc2 <myglc2@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: successful installation, but problems updating
Date: Sat, 11 Nov 2017 10:29:30 -0500 [thread overview]
Message-ID: <86bmk8rfz9.fsf@gmail.com> (raw)
In-Reply-To: <8760ahpv8x.fsf@gmail.com> (Chris Marusich's message of "Fri, 10 Nov 2017 15:30:22 -0800")
On 11/10/2017 at 15:30 Chris Marusich writes:
> Hi Leo,
>
> Leo Famulari <leo@famulari.name> writes:
>
>> 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.
Hi Leo, this is a wonderful clarification of behavior that has confused
me for 1.5 years!
>
> 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.
>
> I've attached a patch which tries to clarify this in the manual. What
> do you think of it?
Hey Chris,
How about saying what Leo said right up front in the substitutes
section. This allows the --fallback addition to be more brief.
Rough draft below.
WDYT? - George
1 file changed, 9 insertions(+), 2 deletions(-)
doc/guix.texi | 11 +++++++++--
modified doc/guix.texi
@@ -2120,6 +2120,13 @@ server. We call these pre-built items @dfn{substitutes}---they are
substitutes for local build results. In many cases, downloading a
substitute is much faster than building things locally.
+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.
+
Substitutes can be anything resulting from a derivation build
(@pxref{Derivations}). Of course, in the common case, they are
pre-built package binaries, but source tarballs, for instance, which
@@ -5192,8 +5199,8 @@ derivations has failed.
Do not build the derivations.
@item --fallback
-When substituting a pre-built binary fails, fall back to building
-packages locally.
+Attempt to build locally instead of issuing an error when substitutes
+are enabled and the substitution of a pre-built binary fails.
@item --substitute-urls=@var{urls}
@anchor{client-substitute-urls}
next prev parent reply other threads:[~2017-11-11 15: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 [this message]
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
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=86bmk8rfz9.fsf@gmail.com \
--to=myglc2@gmail.com \
--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.
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).