From: Kai Mertens <kmx@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37865@debbugs.gnu.org
Subject: bug#37865: guix pull: error: You found a bug:
Date: Wed, 23 Oct 2019 08:55:03 +0200 [thread overview]
Message-ID: <20191023085503.7af886c5.kmx@posteo.net> (raw)
In-Reply-To: <87sgnkwk5l.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3100 bytes --]
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 it run for 16 hours, it may be that substitutes were disabled or
> unavailable for some reason, and that Guix went ahead and started
> building lots of things, eventually failing.
Hmm, shall I try
guix pull --substitute-urls=https://ci.guix.gnu.org
next time?
>
> Perhaps the lines before the error showed the actual build issue?
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 pull: error: You found a bug: the program
> > '/gnu/store/vi260mff4pp4svm3rwz7lcq7kcdxa03k-compute-guix-derivation'
> > failed to compute the derivation for Guix (version:
> > "f0bbf894a1f935c1e0109f35899acb6dfcb977f2"; system: "i686-linux";
> > host version: "2e62ba46e2dc6f27398a65eb157b4ce711ff0e6b";
> > pull-version: 1). Please report it by email to <bug-guix@gnu.org>.
>
> I tried reproducing it by doing:
>
> guix pull --commit=2e62ba46e2dc6f27398a65eb157b4ce711ff0e6b
> -p /tmp/old-guix /tmp/old-guix/bin/guix pull
> --commit=f0bbf894a1f935c1e0109f35899acb6dfcb977f2 -p /tmp/old-to-new
>
> but that worked.
>
> So I guess the problem has to do with a transient build failure or
> something.
>
I will try to enlarge the root partition and try again.
Would you mind to give a recommendation for its size?
Thanks for your immediate, kind response!!
best regards
Kai
--
Kai Mertens <kmx@posteo.net>
OpenPGP Key-ID: 0x40B15AB4B05B5BF1 on keys.gnupg.net
Key fingerprint = 7C83 0A80 01FF 679C 6E8E AFD3 40B1 5AB4 B05B 5BF1
What is that? Please check: https://emailselfdefense.fsf.org/en/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-23 14:11 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 [this message]
2019-10-23 9:50 ` Ludovic Courtès
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=20191023085503.7af886c5.kmx@posteo.net \
--to=kmx@posteo.net \
--cc=37865@debbugs.gnu.org \
--cc=ludo@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.
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).