From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Felix Lechner <felix.lechner@lease-up.com>,
Julien Lepiller <julien@lepiller.eu>,
Suhail <suhail@bayesians.ca>,
Help-Guix mailing list <help-guix@gnu.org>
Subject: Re: Unable to build "Ten Years Reproducibility Challenge" paper
Date: Wed, 01 Nov 2023 11:09:38 -0700 [thread overview]
Message-ID: <87bkcdjqfx.fsf@wireframe> (raw)
In-Reply-To: <87msvyb0vx.fsf@lease-up.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On 2023-10-31, Felix Lechner via wrote:
> On Tue, Oct 31 2023, Julien Lepiller wrote:
>
>> You could skip tests, but that would build a different derivation
>> tree, so it might affect reproducibility
>
> Those shortfalls are a consequence of our packaging habits. In an ideal
> world, would running a test suite ever build a different derivation?
Ideally, no... and there are some things in a package, such as synopsis
and description, which do not affect the build; I suspect it would take
considerably more fiddling to exclude tests derivation hash
calculation...
> Should it ever affect a package's reproducibility?
Should build-time tests affect reproducibility? No, surely not!
Do they in practice? Most definitely yes. :(
> Please bear with me as I again belabor the same point without receiving
> public support. Building packages should be separate from testing them.
In general, I agree... sort of.
I do see value in build-time tests preventing a build from
succeeding... being a way to ensure that a broken build does not
actually get distributed.
You could completely separate out the tests, and set up some other
mechanism to prevent broken things from getting distributed, but that is
considerably more complicated.
I guess the question comes down to which corner-cases do you choose to
cater to?
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-11-01 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 18:44 Unable to build "Ten Years Reproducibility Challenge" paper Suhail
2023-10-31 13:03 ` Julien Lepiller
2023-11-01 3:36 ` Felix Lechner via
2023-11-01 18:09 ` Vagrant Cascadian [this message]
2023-11-02 12:13 ` Simon Tournier
2023-10-31 15:19 ` Simon Tournier
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 16:47 Suhail
2023-11-01 17:06 Suhail
2023-11-01 19:11 ` Simon Tournier
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=87bkcdjqfx.fsf@wireframe \
--to=vagrant@reproducible-builds.org \
--cc=felix.lechner@lease-up.com \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=suhail@bayesians.ca \
/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.