all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Pierre-Henry Fröhring" <contact@phfrohring.com>
Cc: GNU Debbugs <control@debbugs.gnu.org>, 54247@debbugs.gnu.org
Subject: bug#54247: "guix pull error: You found a bug"
Date: Sun, 06 Mar 2022 21:38:53 -0500	[thread overview]
Message-ID: <87mti2zdtu.fsf@gmail.com> (raw)
In-Reply-To: <a49c1ff92265efd3b3e7050d49f7c5b68f9df51f.camel@phfrohring.com> ("Pierre-Henry Fröhring"'s message of "Sat, 05 Mar 2022 11:23:34 +0100")

Hello,

Pierre-Henry Fröhring <contact@phfrohring.com> writes:

>       Thanks for the report.
>
>       It appears this happened while ci.guix.gnu.org (Cuirass) was down; I wonder
>       what the error was though.  Could you please try the following:
>
>       –8<—————cut here—————start————->8— $ guix build
>       /gnu/store/6yhwysy1x5zc5s4xbdar2sayqc20fwdl-compute-guix-derivation
>       –8<—————cut here—————end—————>8—
>
>       To retry building the problematic derivation?  And attach the full compressed
>       log here.
>
>       Thank you,
>
>       Maxim
>
> Thank you for the swift answer Maxim. Executing :
>
> ┌────
> │ guix build /gnu/store/6yhwysy1x5zc5s4xbdar2sayqc20fwdl-compute-guix-derivation
> └────
>
> yielded nothing.
>
> Executing :
>
> ┌────
> │ guix pull
> └────
>
> yielded the same result as above.
>
> I resized the tiny VPS to a bigger one just above and it worked. Here is the new "size" of
> the VPS :
>
>       Basic - Premium AMD, Shared CPU, 1 vCPU, 2 GB, 25 GB, 2 TB

Glad it worked now.  What was the original system specifications?  I
suspect a lack of RAM, perhaps.

> May I suggest a kind of warning or test for hardware requirements when `guix' is used ?

That's a good suggestion, but I'm guessing difficult to implement ('guix
pull' may complete with very little memory used or a lot, depending on
the availability of substitutes).

For you specific needs (low specs), I'd suggest using this your
~/.config/guix/channels.scm file:

--8<---------------cut here---------------start------------->8---
     (use-modules (guix ci))

     (list (channel-with-substitutes-available
            %default-guix-channel
            "https://ci.guix.gnu.org"))
--8<---------------cut here---------------end--------------->8---

As documented in '(guix) Channels with Substitutes'.

I hope that helps,

Maxim




      reply	other threads:[~2022-03-07  3:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 21:35 bug#54247: "guix pull error: You found a bug" Pierre-Henry Fröhring
2022-03-05  3:40 ` Maxim Cournoyer
2022-03-05 10:23   ` Pierre-Henry Fröhring
2022-03-07  2:38     ` Maxim Cournoyer [this message]

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=87mti2zdtu.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=54247@debbugs.gnu.org \
    --cc=contact@phfrohring.com \
    --cc=control@debbugs.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 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.