unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <marius@gnu.org>
To: Igor Gajsin <igor@gajsin.name>
Cc: 42005@debbugs.gnu.org, Igor Gajsin <igor@gajsin.name>
Subject: bug#42005: guix pull has been failed
Date: Wed, 24 Jun 2020 16:33:49 +0200	[thread overview]
Message-ID: <87bll88rea.fsf@gnu.org> (raw)
In-Reply-To: <868sgc227p.fsf@gajsin.name>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

Igor Gajsin <igor@gajsin.name> writes:

> I think I found the root cause. Please, see the output of
>
> guix build --cores=1
> /gnu/store/d2v7gzbcv9by7zw8q39v0drff1q8q9da-util-linux-2.35.1.drv
>
> in the attachment.

Right.  This is the same issue as
<https://issues.guix.gnu.org/issue/41384>.

TL;DR: Upgrade (or downgrade) your kernel.  Or enable substitutes.

>> Also, did you intentionally disable binary substitutes?
>
> I use it as a separate package manager in Ubuntu and I use it 'as
> it'. Literally, I configure nothing.

How did you install Guix?  The installer script asks at the end whether
to enable binary substitutes or not: choosing no will require you to
build everything from source.

If you wish to enable transparent substitutes of pre-built packages from
the build farm, you can run this command:

  sudo guix archive --authorize < /var/guix/profiles/per-user/root/current-guix/share/guix/ci.guix.gnu.org.pub

Hope this helps!  :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2020-06-24 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 10:31 bug#42005: guix pull has been failed Igor Gajsin
2020-06-22 17:03 ` Marius Bakke
2020-06-24 10:22   ` Igor Gajsin
2020-06-24 14:33     ` Marius Bakke [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

  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=87bll88rea.fsf@gnu.org \
    --to=marius@gnu.org \
    --cc=42005@debbugs.gnu.org \
    --cc=igor@gajsin.name \
    /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).