all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Eric Gade <eric.gade@gmail.com>
Cc: 75134-done@debbugs.gnu.org
Subject: bug#75134: Issue with guix pull
Date: Wed, 01 Jan 2025 01:23:41 +0100	[thread overview]
Message-ID: <87o70rqt4i.fsf@pelzflorian.de> (raw)
In-Reply-To: <CA+CiqoXXsYN7H-V7Uom__k-GcS1kDO9u+95iA2PN7xCEaWjkwQ@mail.gmail.com> (Eric Gade's message of "Mon, 30 Dec 2024 12:24:24 -0500")

Glad to hear --cores=1 helped!

I have seen some strange behavior in x86_64 qemu VMs, but also --cores=1
did help me build rust-1.54 bootstrap on x86_64.  It also might be a bug
in guix-daemon, perhaps only in the old 1.4.0 revision, judging from how
the error message says store protocol error.

I will close this bug and not investigate further, but if you want to
investigate, you could try if, after upgrading your system with `guix
system reconfigure`, the command

guix build --check --no-grafts /gnu/store/6cmb5svslbgrhmbg6mkh40x5rnzfvqsg-graphviz-minimal-7.0.1.drv

continues to fail and maybe file a more specific bug that the
graphviz-minimal package must specify that it can be built on one core
only.  That is
‘#:parallel-build?’
‘#:parallel-tests?’
might have to be false.  At least if someone can observe this outside a
VM.  On my four core riscv Visionfive2, `guix build --check --no-grafts
graphviz-minimal` succeeds, though.

Regards,
Florian




      reply	other threads:[~2025-01-01  0:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26 21:25 bug#75134: Issue with guix pull Eric Gade
2024-12-28 12:23 ` pelzflorian (Florian Pelz)
2024-12-28 15:34   ` Eric Gade
2024-12-29 13:15     ` pelzflorian (Florian Pelz)
2024-12-30 17:24       ` Eric Gade
2025-01-01  0:23         ` pelzflorian (Florian Pelz) [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=87o70rqt4i.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=75134-done@debbugs.gnu.org \
    --cc=eric.gade@gmail.com \
    /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.