From: "Ludovic Courtès" <ludo@gnu.org>
To: Lars Bilke <lars.bilke@ufz.de>
Cc: Sharlatan Hellseher <sharlatanus@gmail.com>,
Andreas Enge <andreas@enge.fr>,
71821-done@debbugs.gnu.org, 57005-don@debbugs.gnu.org,
Eric Bavier <bavier@posteo.net>
Subject: bug#71821: [PATCH v3] gnu: petsc: scrub build machine specifics
Date: Fri, 26 Jul 2024 19:24:35 +0200 [thread overview]
Message-ID: <87msm4awx8.fsf@gnu.org> (raw)
In-Reply-To: <891ca7832b5e73ee35d277ad1f7fe0f070dace8b.1721636747.git.lars.bilke@ufz.de> (Lars Bilke's message of "Mon, 22 Jul 2024 10:25:47 +0200")
Hi Lars,
Lars Bilke <lars.bilke@ufz.de> skribis:
> Resending patch because of CI failure.
>
> 'Libraries compiled on' does not have to be removed since PETSc 3.9:
>
> https: //gitlab.com/petsc/petsc/-/commit/a970bd748978a4e12790be7c36b10e832ec0149f
>
> Also merged all add-after 'install phases into `clean-install.
>
> Change-Id: I41d82339e43187d7dc7e3fc189a338784c363c68
>
> sort source files in generated makefiles for reproducibility
>
> Change-Id: I86e5b9cd0d7184019617bd8ae9a23eaf459891d7
I applied this patch; however, I took the liberty to leave out phase
merges, which are unrelated to the reproducibility issue and should be
discussed separately, for the sake of clarity (though in general I would
recommend short, focused phases rather than large hard-to-override
phases).
Pushed as 31fe177a97bacec643180cc5bcf8805a6cb07481.
Thanks!
Ludo’.
prev parent reply other threads:[~2024-07-26 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 12:47 [bug#71821] [PATCH] gnu: petsc: make it reproducible Lars Bilke
2024-06-28 13:08 ` [bug#71821] [PATCH v2] gnu: petsc: scrub build machine specifics Lars Bilke
2024-07-22 8:25 ` [bug#71821] [PATCH v3] " Lars Bilke
2024-07-26 17:24 ` Ludovic Courtès [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=87msm4awx8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=57005-don@debbugs.gnu.org \
--cc=71821-done@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=bavier@posteo.net \
--cc=lars.bilke@ufz.de \
--cc=sharlatanus@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.