From: Andreas Rammhold <andi@notmuch.email>
To: 20272@debbugs.gnu.org
Subject: bug#20272: Support reproducible builds
Date: Mon, 1 Jun 2020 22:45:51 +0200 [thread overview]
Message-ID: <20200601204550.4mevbvzltq5pqzru@wrt> (raw)
In-Reply-To: <87twws88hr.fsf@gnu.org>
I've just stumpled upon this as within Nixpkgs we have a pending [PR]
that references this issue. Since it reads as if it should be solved in
Guile 2.1+ but still occurs for us in nixpkgs when using parallel builds
(aka using multiple cores in a single build) I thought it might be a
good to get in touch.
Updating our expression to Guile 3.0.2 did not fix the reproducibility
issues either (when built using multiple cores).
I've just now tried a Guix 1.1.0 QEMU image and invoked `guix build
--round=2 -K guile --check -c 8` and it also wasn't reproducible. A
bunch of .go files showed differences between the builds.
Am I missings something?
Would gladly help if there is something I can do.
[PR]: https://github.com/NixOS/nixpkgs/pull/78778
next prev parent reply other threads:[~2020-06-01 20:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 11:48 bug#20272: Support reproducible builds Ludovic Courtès
2016-02-04 2:41 ` Mark H Weaver
2016-02-04 9:35 ` Ludovic Courtès
2016-06-20 15:46 ` Andy Wingo
2016-02-11 7:09 ` Mark H Weaver
2016-02-12 16:29 ` Mark H Weaver
2016-06-20 15:48 ` Andy Wingo
2016-06-23 19:22 ` Andy Wingo
2016-11-03 6:54 ` Jan Nieuwenhuizen
2016-11-14 21:44 ` Jan Nieuwenhuizen
2016-12-14 16:25 ` Ludovic Courtès
2016-12-14 23:32 ` Ludovic Courtès
2016-12-14 23:42 ` Ludovic Courtès
2016-12-20 23:00 ` Ludovic Courtès
2016-12-21 23:53 ` Ludovic Courtès
2016-12-30 21:00 ` Ludovic Courtès
2017-03-07 19:55 ` Ludovic Courtès
2017-02-28 13:26 ` Andy Wingo
2017-03-05 20:49 ` Ludovic Courtès
2017-03-06 20:13 ` Andy Wingo
2020-06-01 20:45 ` Andreas Rammhold [this message]
2020-06-02 12:25 ` Andreas Rammhold
[not found] ` <87o8lcu1v8.fsf@gmail.com>
2020-11-24 4:44 ` Vagrant Cascadian
2023-11-17 20:28 ` Bernhard M. Wiedemann
2024-04-08 17:27 ` Thompson, David
2024-04-09 4:02 ` Bernhard M. Wiedemann
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200601204550.4mevbvzltq5pqzru@wrt \
--to=andi@notmuch.email \
--cc=20272@debbugs.gnu.org \
/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.
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).