unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Brian Woodcox <bw@inskydata.com>
Cc: help-guix@gnu.org
Subject: Re: *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS ***
Date: Wed, 31 Oct 2018 14:35:46 -0400	[thread overview]
Message-ID: <87y3ae6k0y.fsf@netris.org> (raw)
In-Reply-To: <33017962-EFD3-4931-A7FA-22EC3E25B073@inskydata.com> (Brian Woodcox's message of "Wed, 31 Oct 2018 09:42:25 -0600")

Brian Woodcox <bw@inskydata.com> writes:

> So I have been trying to install GuixSD 0.15.0 for a few days now.
>
> My first problem was not setting
> —substitutes-urls=“https://berlin.guixsd.org.  So that fixed one
> problem.
>
> My other problem is try as I might, I cannot get either guile-2.2.3 or
> guile-2.2.4 to install.
>
> It always hangs when trying to do the tests after writing all the *.go
> files, (which by the way takes a long time).

What are the last messages visible at the point where it gets stuck?
It would be helpful to see the tail of the build log.

Since I've not seen other reports of this problem, my first guess is
that the problem is specific to builds done within VirtualBox, for some
reason.  It would be useful to know which test is getting stuck.  Since
VirtualBox requires a non-free compiler for part of its build, I don't
use it myself.  I use QEMU instead.

Also, normally you would not need to build Guile, but would simply
download a binary substitute for Guile.  However, our primary build farm
is currently offline due to a recent disk failure, and our newer build
farm (berlin.guixsd.org) unfortunately does not have a complete set of
substitutes for 0.15.0, but only for the most popular or most recently
built ones.

So, this is a temporary issue while we wait for the FSF sysadmins to
finish migrating hydra.gnu.org to a new disk array, which will probably
be another few days.  I'm sorry for the inconvenience.

> So are there any work arounds to disable the tests for guile-2.2.x so
> I can get this operating system operational?

In theory it could be done, but disabling tests would be a change to the
Guile package, and therefore a change to the derivations of all packages
built on top of Guile, which in Guix is *everything* because Guile is
used to execute our build recipes.

As a result, if you did this, you would not be able to find *any* binary
substitutes from our official servers, because you'd be asking for
different derivations than the ones built by our build farm.

  parent reply	other threads:[~2018-10-31 18:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 15:42 *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS *** Brian Woodcox
2018-10-31 17:41 ` Leo Famulari
2018-10-31 18:23   ` Brian Woodcox
2018-10-31 18:35 ` Mark H Weaver [this message]
2018-10-31 18:47   ` Brian Woodcox
2018-11-01  7:35     ` Mark H Weaver
2018-10-31 20:50   ` Brian Woodcox
2018-10-31 21:54     ` George Clemmer
2018-10-31 22:30       ` Brian Woodcox
2018-10-31 23:44         ` George Clemmer
2018-11-01  2:33           ` Mark H Weaver
2018-11-01  3:35             ` George Clemmer
2018-10-31 22:47       ` Mark H Weaver
2018-10-31 23:57         ` George Clemmer
2018-11-01  0:09           ` George Clemmer
2018-11-06 15:27             ` swedebugia
2018-11-06 18:24               ` George Clemmer
2018-11-07 11:40                 ` swedebugia
2018-11-07 13:01                   ` George Clemmer
2018-11-07 15:16         ` Christopher Lemmer Webber
2018-11-01  1:35     ` Mark H Weaver
2018-11-01  2:58       ` Brian Woodcox
2018-11-06  5:14       ` Mark H Weaver
2018-11-06 17:08         ` Brian Woodcox
2018-11-06 23:22           ` Brian Woodcox

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=87y3ae6k0y.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=bw@inskydata.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).