unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 55273@debbugs.gnu.org
Subject: bug#55273: failed to compute the derivation for Guix (version: "b80ca672de936a76368de6e6ea0b28505e74d420"; system: "x86_64-linux";
Date: Sat, 7 May 2022 23:42:06 +0000	[thread overview]
Message-ID: <202205072342.07311.luke@dashjr.org> (raw)
In-Reply-To: <f72f8a56bd046073b58540e0875afaec7a27b6c2.camel@telenet.be>

--cores=1 didn't help. Any other workaround I can try for now?
(Bypass check stage?)

On Friday 06 May 2022 19:40:57 Maxime Devos wrote:
> Luke Dashjr schreef op vr 06-05-2022 om 18:49 [+0000]:
> > FWIW, `guix pull` always fails with this for me. This is a qemu VM,
> > freshly installed from guix-system-install-1.3.0.x86_64-linux.iso
> > with --no-substitutes (and hand-fixing the texlive patch URI issues).
>
> I'm guessing this might be some reproducibility problem caused by
> parallelism, so to work-around the issue, maybe try "guix pull --
> cores=1".  I can't reproduce locally.
>
> Greetings,
> Maxime.





  parent reply	other threads:[~2022-05-07 23:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 13:33 bug#55273: failed to compute the derivation for Guix (version: "b80ca672de936a76368de6e6ea0b28505e74d420"; system: "x86_64-linux"; Luke Dashjr
2022-05-06 17:57 ` Maxime Devos
2022-05-06 17:58   ` Maxime Devos
2022-05-06 18:49     ` Luke Dashjr
2022-05-06 19:40       ` Maxime Devos
2022-05-06 20:14         ` Maxime Devos
2022-05-06 20:23           ` Maxime Devos
2022-05-07 23:42         ` Luke Dashjr [this message]
2022-05-06 18:09   ` Maxime Devos
2022-05-06 18:23     ` bug#55273: guile-git@0.5.2 (irreproducibly?) fails to build and output is non-deterministic Maxime Devos
2022-07-12 14:08       ` bug#55273: guile-git is not reproducible Maxim Cournoyer

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=202205072342.07311.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=55273@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).