all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 74112-done@debbugs.gnu.org,  Jakob Kirsch <jakob.kirsch@web.de>,
	 Simon Tournier <zimon.toutoune@gmail.com>,
	 Hilton Chain <hako@ultrarare.space>,
	Guix Devel <guix-devel@gnu.org>
Subject: Re: [bug#74112] bug#74204: [bug#74112] Guix is not reproducible
Date: Wed, 18 Dec 2024 18:19:29 +0900	[thread overview]
Message-ID: <8734ilpcv2.fsf@gmail.com> (raw)
In-Reply-To: <87o72ip20w.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 14 Nov 2024 11:01:35 +0100")

Hi,

Ludovic Courtès <ludo@gnu.org> writes:

[...]

>> Perhaps we should set the default parallel-build? to #f in the
>> guile-build-system at least in the meantime, with a prominent comment as
>> to why and a reference to the upstream issue?  Many Guile packages use
>> the gnu-build-system so that wouldn't cover all of them like
>> 'guix'... I'm not sure.
>
> Sounds good to me: packages using ‘guile-build-system’ are usually
> relatively small so the impact is negligible.

That's now tackled in #74909.

-- 
Thanks,
Maxim


      reply	other threads:[~2024-12-18  9:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 18:38 bug#74204: Guix is not reproducible Jakob Kirsch via Bug reports for GNU Guix
2024-10-30 18:06 ` [bug#74112] [PATCH] Fix determinism issue in guix package Jakob Kirsch via Guix-patches via
2024-11-05 10:31   ` bug#74204: Guix is not reproducible Hilton Chain via Bug reports for GNU Guix
2024-11-05 10:31     ` [bug#74112] " Hilton Chain via Guix-patches via
2024-11-05 15:25     ` bug#74204: " Hilton Chain via Bug reports for GNU Guix
2024-11-07 17:54       ` bug#74204: [bug#74112] " Simon Tournier
2024-11-10  9:11         ` Maxim Cournoyer
2024-11-14 10:01           ` Ludovic Courtès
2024-12-18  9:19             ` 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=8734ilpcv2.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=74112-done@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=hako@ultrarare.space \
    --cc=jakob.kirsch@web.de \
    --cc=ludo@gnu.org \
    --cc=zimon.toutoune@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.