unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Kai Mertens <kmx@posteo.net>
Cc: 37865@debbugs.gnu.org
Subject: bug#37865: guix pull: error: You found a bug:
Date: Wed, 23 Oct 2019 11:50:44 +0200	[thread overview]
Message-ID: <874kzzx023.fsf@gnu.org> (raw)
In-Reply-To: <20191023085503.7af886c5.kmx@posteo.net> (Kai Mertens's message of "Wed, 23 Oct 2019 08:55:03 +0200")

Hi,

Kai Mertens <kmx@posteo.net> skribis:

> On Tue, 22 Oct 2019 23:21:58 +0200
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Hi Kai,
>> 
>
> Hello Ludovic,
>
>> Kai Mertens <kmx@posteo.net> skribis:
>> 
>> > unfortunately, I do not manage to update my GNU Guix version via “guix
>> > pull”. The command fails with the listed message after being executed
>> > for about 16hours.  
>> 
>> Did you enable substitutes from <https://ci.guix.gnu.org>?
>> See <https://guix.gnu.org/manual/en/html_node/Substitutes.html>.
>> 
>
> hmm, I did not enable substitutes explicitly in the command line, but
> as far as I remember, I allowed guix to use substitutes when I set it
> up some time ago. Is there a handy command that helps me to check the
> current configuration? Anyway, I was not using option --no-substitutes.

If you installed it long ago, it could be that you authorized
substitutes from hydra.gnu.org (the former CI server, discontinued in
June¹) but not from ci.guix.gnu.org.

So you would need to check:

  1. which substitute URL guix-daemon is using;

  2. which keys are authorized in /etc/guix/acl.

The above chapter of the manual has more info on this.

LMK how it goes!

¹ https://lists.gnu.org/archive/html/info-guix/2019-06/msg00001.html

> Ahh, you are right. And please accept my apologies, as I did not see
> the essential hint:
>
>> command "make" "check" "-j" "2" failed with status 2
>> note: build failure may have been caused by lack of free disk space
>> builder for `/gnu/store/wswfwmyrbd39blimabdkm46z6b138rlc-tar-1.32.drv' failed with exit code 1
>> @ build-failed /gnu/store/wswfwmyrbd39blimabdkm46z6b138rlc-tar-1.32.drv - 1 builder for `/gnu/store/wswfwmyrbd39blimabdkm46z6b138rlc-tar-1.32.drv' failed with exit code 1
>> cannot build derivation `/gnu/store/fpfj0ds2vd7vapp54dkf09jipl0mkzgw-ghostscript-9.27.drv': 1 dependencies couldn't be built
>> [...]
>
> Indeed, at the time of failure, the root partition had only about 2.8G
> space left. But /tmp had something like 9G in spare. I wonder if I can
> tell guix to use as much tmp-space as applicable?

Guix needs space in /gnu/store to store the actual build results, and it
needs space in /tmp when it’s building stuff.

Building ‘tar’, for example, consumes quite a bit of space (in /tmp)
because its test suite runs on large files.

> I will try to enlarge the root partition and try again.
> Would you mind to give a recommendation for its size?

It depends on your use case of course, but most likely you’ll need at
least a dozen GiB.

But first, I recommend figuring out the substitute story so you don’t
have to build everything locally!

Thanks,
Ludo’.

  reply	other threads:[~2019-10-23  9:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22  6:34 bug#37865: guix pull: error: You found a bug: Kai Mertens
2019-10-22 21:21 ` Ludovic Courtès
2019-10-23  6:55   ` Kai Mertens
2019-10-23  9:50     ` Ludovic Courtès [this message]
2019-10-23 14:26       ` Kai Mertens
2019-10-23 16:55         ` Efraim Flashner
2019-10-24 11:34           ` Kai Mertens
2019-10-24 11:44             ` Efraim Flashner
2019-10-24 20:49             ` Bengt Richter
2019-10-25  6:55               ` Bengt Richter
2019-10-27  7:54               ` Kai Mertens
2019-10-27 11:52                 ` Bengt Richter
2019-11-16  1:52                   ` Kai Mertens
2019-10-24 17:43         ` Ludovic Courtès

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=874kzzx023.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=37865@debbugs.gnu.org \
    --cc=kmx@posteo.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).