From: Mark H Weaver <mhw@netris.org>
To: Alberto EFG <albertoefg@posteo.mx>
Cc: 35012@debbugs.gnu.org
Subject: bug#35012: Can't install icecat
Date: Thu, 28 Mar 2019 21:57:21 -0400 [thread overview]
Message-ID: <87mule7883.fsf@netris.org> (raw)
In-Reply-To: <87d0md8lya.fsf@posteo.mx>
Hi Alberto,
> It keeps failing no matter what. I have about 200gb of disk space and
> 8gb of RAM. This is the error I always get:
>
> $ guix package -c 7 --upgrade icecat --substitute-urls="https://ci.guix.info"
> substitute: updating substitutes from 'https://ci.guix.info'... 100.0%
> substitute: updating substitutes from 'https://ci.guix.info'... 100.0%
> downloading from https://ci.guix.info/nar/qlwg5lyxnnj68kw2agx4z5fr2b6vxpdc-icecat-60.6.1-guix1.tar.xz...
>
> icecat-60.6.1-guix1.tar.xz 303.0MiB 1.8MiB/s 02:47 [##################] 100.0%
>
> building /gnu/store/jpg44cnp64hzdi2hislnid40jdr3kkhp-rust-1.24.1.drv...
> \ 'install' phasenote: build failure may have been caused by lack of free disk space
As other people have mentioned, this substitute should now be available,
but I wanted to add that builds are performed in /tmp by default, and
that's likely the reason you ran out of disk space, even though your
root partition has plenty of space.
If you'd like builds to be performed somewhere else, e.g. /var/tmp, then
you should arrange for the TMPDIR environment variable to be set
appropriately when launching 'guix-daemon'.
Regards,
Mark
next prev parent reply other threads:[~2019-03-29 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 19:39 bug#35012: Can't install icecat Alberto EFG
2019-03-26 23:09 ` Björn Höfling
2019-03-27 11:14 ` Danny Milosavljevic
2019-03-27 14:49 ` Ludovic Courtès
2019-03-29 1:57 ` Mark H Weaver [this message]
2019-03-29 5:11 ` Alberto EFG
2019-03-29 9:20 ` Björn Höfling
2019-03-29 21:34 ` Alberto EFG
2019-03-30 6:14 ` Mark H Weaver
2020-11-30 20:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mule7883.fsf@netris.org \
--to=mhw@netris.org \
--cc=35012@debbugs.gnu.org \
--cc=albertoefg@posteo.mx \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.