From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: successful installation, but problems updating Date: Sat, 11 Nov 2017 09:05:59 -0800 Message-ID: <878tfcbv9k.fsf@gmail.com> References: <20171106091656.6e775deb@graviton.instanton> <20171106111829.1e07b138@hitpoints.browniehive.net> <87fu9mptdl.fsf@gmail.com> <20171110162818.GA11031@jasmine.lan> <8760ahpv8x.fsf@gmail.com> <86bmk8rfz9.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39206) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eDZEN-0008I8-LW for help-guix@gnu.org; Sat, 11 Nov 2017 12:06:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eDZEJ-0000vP-L3 for help-guix@gnu.org; Sat, 11 Nov 2017 12:06:07 -0500 Received: from mail-pg0-x230.google.com ([2607:f8b0:400e:c05::230]:55043) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eDZEJ-0000vB-EQ for help-guix@gnu.org; Sat, 11 Nov 2017 12:06:03 -0500 Received: by mail-pg0-x230.google.com with SMTP id c123so1656231pga.11 for ; Sat, 11 Nov 2017 09:06:03 -0800 (PST) In-Reply-To: <86bmk8rfz9.fsf@gmail.com> (myglc2@gmail.com's message of "Sat, 11 Nov 2017 10:29:30 -0500") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: myglc2 Cc: "help-guix@gnu.org" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable myglc2 writes: > On 11/10/2017 at 15:30 Chris Marusich writes: > >> Hi Leo, >> >> Leo Famulari 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{substi= tutes}---they are > substitutes for local build results. In many cases, downloading a > substitute is much faster than building things locally. >=20=20 > +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. >=20=20 > @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. >=20=20 > @item --substitute-urls=3D@var{urls} > @anchor{client-substitute-urls} I think I like the way you wrote it better. I'm fine with that. I was hoping not to add to the already-voluminous paragraphs about Substitutes at the top of section 3.3, but honestly as long as this info is in the manual, I'm happy. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAloHLfcACgkQ3UCaFdgi Rp3Z7hAAmeyMVE1wORVqXB3Mjnyk0chfLPrkwLKEV0eSuFcIU1oI2i3XlAPDAVHv C9RMcKEAt2DAE08LYWna/aF5EFxXRkKxEPQ3W2K0MDq2xVoyL3mSXDyrELgs2SKX /73zODaiPtLuH/ZbPZ5NiymkKGpxl5YTgxt2EtDIBquhZL4k3dMJj49ZgyPB8gmf 5QRvopqgIssr1lppk29rQ8pboRThPTy+kPiNU09m6bj+Xn/Yjqc24jm2boV3+c47 8ZkAyuAzbCYM9OPCqw5VFxXoYA0UMqgiLBCGYDZSvu74aQkVqlzeoRWgKf3/pU1N DyH/wF+rMNQHEByJdMuPko0tgcps4M1dGuehVbds32w0TX99vKxw3X1KE2XsXeVn T3ZSCqCStYXscrMt17sM1Wl6ETQ7kBOsK66/RuN1SSKOutZ5dNpp6/ioQHpkrNlH G7KsF0/JFeHk8+o1KRZUDGA3TkK1cNjQIclGYEK0/9Dnc0q+RJ1i6wpYN7TAc+Pb nslhcptYGCVEAz4bZgWf9wM6IG67hMavTIAc7CwM0OYHwGdOphapid+73sQDdmB2 Ed+Tq2AMPE1SoqbyZLGTPEkSK1pzKbqX0GgekUldVwCdXU760H0ZDkZwSdM/Ioha uCXbyjd+/0arK6dZlKhT/9P1EhpH1hAX1jM3xcFKGz4IAmH0GZc= =ND7K -----END PGP SIGNATURE----- --=-=-=--