From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: zimoun <zimon.toutoune@gmail.com>,
rb-general@lists.reproducible-builds.org
Cc: guix-devel@gnu.org
Subject: Re: Reproducibility of "core" packages in GNU Guix
Date: Mon, 02 May 2022 07:29:05 -0700 [thread overview]
Message-ID: <87r15ct3da.fsf@contorta> (raw)
In-Reply-To: <87mtg082jj.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
On 2022-05-02, zimoun wrote:
> On Mon, 02 May 2022 at 06:11, Vagrant Cascadian <vagrant@reproducible-builds.org> wrote:
>> $ guix challenge --diff=none $(cat guix-base-set)
...
>> The fact that the guix and guile packages do not build reproducibly is a
>> little disappointing as they're both so central to guix itself; I
>> suspect parallelism triggers those reproducibility issues(from
>> experience with Debian), though that may just reveal other issue in
>> guile itself.
>
> About Guix, probably bug#44835 [1] for one, I guess. And note this old
> Guile bug#20272 [2] for two, which implies unreproducible Guix.
>
> 1: <http://issues.guix.gnu.org/issue/44835>
This one is regarding build paths, and since guix normalizes the build
path in the build environment, it should not affect builds in guix...
> 2: <https://issues.guix.gnu.org/issue/20272>
But this one definitely touches on the parallelism issue!
Thanks for the links! I remembered commenting on them... just didn't
find the links with a quick search...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-05-02 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wnfagvnp.fsf@contorta>
2022-05-02 13:11 ` Reproducibility of "core" packages in GNU Guix Vagrant Cascadian
2022-05-02 13:52 ` zimoun
2022-05-02 14:29 ` Vagrant Cascadian [this message]
2022-06-02 3:12 ` Vagrant Cascadian
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=87r15ct3da.fsf@contorta \
--to=vagrant@reproducible-builds.org \
--cc=guix-devel@gnu.org \
--cc=rb-general@lists.reproducible-builds.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 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).