From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Hilton Chain <hako@ultrarare.space>,
Jakob Kirsch <jakob.kirsch@web.de>,
Guix Devel <guix-devel@gnu.org>,
74112-done@debbugs.gnu.org, 74204-done@debbugs.gnu.org
Subject: Re: bug#74204: [bug#74112] Guix is not reproducible
Date: Sun, 10 Nov 2024 18:11:38 +0900 [thread overview]
Message-ID: <87a5e7xxkl.fsf@gmail.com> (raw)
In-Reply-To: <87pln70w16.fsf@gmail.com> (Simon Tournier's message of "Thu, 07 Nov 2024 18:54:29 +0100")
Hi Simon,
Simon Tournier <zimon.toutoune@gmail.com> writes:
> Hi,
>
> On Tue, 05 Nov 2024 at 23:25, Hilton Chain via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
>
>>> I can confirm the reproducibility issue.
>>>
>>> I have two x86_64-linux machines building guix to verify the fix, I'll apply
>>> your patch once they produce matching outputs.
>>
>> Took me quite a while to build 5 rounds. :)
>>
>> --8<---------------cut here---------------start------------->8---
>> $ guix hash --serializer=nar /gnu/store/fs7x07jfn7igpkwv3alrs9by21q70y13-guix-1.4.0-26.5ab3c4c
>> 0kh87wb4qn97kwzrf4igal71cjvv143j6jr2y3dwfzcy1madj1ll
>> --8<---------------cut here---------------end--------------->8---
>>
>> Applied #74112 as 4c56d0cccdc44e12484b26332715f54768738c5f, thanks!
>
> Maybe I am missing something. To my knowledge, .go files produced by
> Guile are not always reproducible, see bug#20272 [1]. And, from my
> understanding, Guix cannot be reproducible until this bug had been
> fixed. Therefore, I am not convinced that this patch is worth under
> this frame considering the build-time penalty it brings.
>
> That’s said, maybe it’s better than nothing and the package ’guix’ is
> barely built after all. I do not know.
>
> What people think?
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.
It'd be nicer to fix the underlying guile issue (again?), but I doubt
many people are up to this.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-11-10 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZykUqu7t4WuUF9kj@kernelpanicroom>
[not found] ` <ZyJ1wSX6cPIdnLpN@kernelpanicroom>
[not found] ` <87fro6yntj.wl-hako@ultrarare.space>
[not found] ` <87ed3pzora.wl-hako@ultrarare.space>
2024-11-07 17:54 ` bug#74204: [bug#74112] Guix is not reproducible Simon Tournier
2024-11-10 9:11 ` Maxim Cournoyer [this message]
2024-11-14 10:01 ` Ludovic Courtès
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=87a5e7xxkl.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=74112-done@debbugs.gnu.org \
--cc=74204-done@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=hako@ultrarare.space \
--cc=jakob.kirsch@web.de \
--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 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).