From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Howard Subject: bug#24993: Documentation: 'guix pull' needed during SD installation Date: Wed, 23 Nov 2016 08:25:27 -0900 Message-ID: References: <7d52d8ee-c253-685b-1871-f908850ee606@alaskasi.com> <20161123044607.GA23298@jasmine> <0cf83259-2c5d-ae51-5697-02299251051c@alaskasi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53456) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c9bJ8-0001tO-GC for bug-guix@gnu.org; Wed, 23 Nov 2016 12:26:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c9bJ4-0004bJ-2p for bug-guix@gnu.org; Wed, 23 Nov 2016 12:26:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:52343) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c9bJ3-0004b1-UT for bug-guix@gnu.org; Wed, 23 Nov 2016 12:26:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1c9bJ3-000807-PA for bug-guix@gnu.org; Wed, 23 Nov 2016 12:26:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <0cf83259-2c5d-ae51-5697-02299251051c@alaskasi.com> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Leo Famulari Cc: 24993@debbugs.gnu.org The error is: " guix substitute: error: download from 'https://mirror.hydra.gnu.org/nar/zrwslk773<...snip...>e2fsck-static-1.42.13' failed 410, "Gone" killing process 859 guix system: error: build failed: some substitutes for the outputs of derivation `/gnu/store/kjzga<...snip...>-e2fsck-static-1.42..13.drv' failed (usually happens due to networking issues); try `--fallback' to build derivation from source " Sorry for snipping the file names, but I have to type it all in manually to this email. On 11/23/2016 07:46 AM, Christopher Howard wrote: > Hi. What I remember happening was that on some package I got an error > something like "could not get package such-and-such, may be caused by > network errors" which wasn't fixed by running the command again. Then I > ran with --fallback as recommended, but then it seemed to be building > the entire gnome desktop from source. After a few hours of this it was > still compiling low-level gnome packages, so I gave up, and the folks at > #guix irc suggested guix pull. > > To be honest, I can't remember which package it was. I'll try again with > a fresh installation. > > On 11/22/2016 07:46 PM, Leo Famulari wrote: >> On Tue, Nov 22, 2016 at 01:25:57PM -0900, Christopher Howard wrote: >> >> Welcome Christopher! >> >>> In the online installation docs at >>> , >>> please insert the command 'guix pull' before the "guix system init" >>> command. Otherwise installation can fail due to missing binary packages, >>> which creates confusion for newbie installers like myself. Thank you! >> >> Can you give more detail about the problems you ran into? We want `guix >> system init` to "just work". >> >> In general, if some binary fails to be substituted [0], adding >> --fallback to the command should cause the package to be built from >> source, working around the issue. >> >> I think that running `guix pull` before `guix system init` is not the >> right choice for newbies, although there are some trade-offs [1]. >> >> Most new users will be installing from the binary GuixSD installer >> offered on our web site. This installer is built from a Git commit that >> we have tested to ensure that everything should work. We strive to keep >> our master branch "deployable", but of course we make mistakes >> sometimes. `guix pull` draws from the HEAD commit of the master branch, >> and so new users might end up with a broken system as their first >> experience. GuixSD is extremely robust once installed — you can always >> roll-back — so it's a good idea to initialize from a known good commit >> and then update. >> >> Additionally, it's likely that we will not yet have built binary >> substitutes for the most recent changes on the master branch, so new >> users will end up building some things from source if they use `guix >> pull`. >> >> [0] Guix is a hybrid of build-from-source and binary package management >> systems. It's really a build-from-source distro, but we offer so-called >> "binary substitutes", and they are transparently substituted for a >> source build if they are available and the user has authorized our >> substitutes server. But, if Guix expects a package to be substituted >> and something goes wrong, the action will fail. Using --fallback works >> around this and builds from source even when the substitution fails. >> >> [1] I think the main drawback of installing from the release tag without >> `guix pull` is that the initial generation of the GuixSD system will be >> lacking important upstream bug fixes. I think users should `guix pull && >> guix system reconfigure` immediately after initializing the system. Guix >> actually nags users to do this: >> >> http://git.savannah.gnu.org/cgit/guix.git/tree/guix/scripts/system.scm?id=08b3e4a97066c9baaf39e3df7c2dd9c39e693ead#n577 >> > -- Christopher Howard, Computer Assistant Alaska Satellite Internet 3239 La Ree Way, Fairbanks, AK 99709 907-451-0088 or 888-396-5623 (toll free) fax: 888-260-3584 mailto:christopher@alaskasi.com http://www.alaskasatelliteinternet.com