From: Marco van Hulten <marco@hulten.org>
To: help-guix@gnu.org
Subject: Re: successful installation, but problems updating
Date: Mon, 06 Nov 2017 21:06:13 +0100 [thread overview]
Message-ID: <20171106210540.0271775c@jasniac.instanton> (raw)
In-Reply-To: <87vainu4h3.fsf@zancanaro.id.au>
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
Hello,
Thank you Carl and Thomas for the clear explanation.
Still one issue remains.
Op 06 nov 20:43 schreef Carlo Zancanaro:
> > 'guix pull' ends with a compilation error:
> >
> >> guix pull: error: build failed: build of
> >> `/gnu/store/*-guix-latest.drv' failed
>
> This isn't enough to tell me what's happened, unfortunately. I'm not
> sure what the common failure cases are for this, but hopefully someone
> else will know.
This was a bit meager description. This is the full output on the
terminal:
```
root@watson ~# guix pull
Starting download of /tmp/guix-file.F5p3in
From https://git.savannah.gnu.org/cgit/guix.git/snapshot/master.tar.gz...
….tar.gz 2.3MiB/s 00:06 | 13.8MiB transferred
unpacking '/gnu/store/5qcf02fjmi4y4chh3c07ardvjlw355gw-guix-latest.tar.gz'...
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
The following derivation will be built:
/gnu/store/nd19z0mxhj81p1pc5f86ahxkzih6z2mg-guix-latest.drv
updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%g'... 0.0%
copying and compiling to '/gnu/store/4gs1fivs32qw3xrn5z1dq3hr9xmblv18-guix-latest' with Guile 2.2.2...
loading... 26.0% of 646 filesrandom seed for tests: 1509990307
compiling... 75.2% of 646 filesbuilding of `/gnu/store/nd19z0mxhj81p1pc5f86ahxkzih6z2mg-guix-latest.drv' timed out after 3600 seconds of silence
guix pull: error: build failed: build of `/gnu/store/nd19z0mxhj81p1pc5f86ahxkzih6z2mg-guix-latest.drv' failed
root@watson ~# echo $?
1
```
After some time during the compilation process, my system freezes for a
long time (CapsLock doesn't light up, cannot move mouse cursor, cannot
switch to vc...). After about an hour the system is responsive again.
- Marco
[-- Attachment #2: OpenPGP digitale handtekening --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-11-06 20:06 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 [this message]
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
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=20171106210540.0271775c@jasniac.instanton \
--to=marco@hulten.org \
--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).