From: Leo Famulari <leo@famulari.name>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>,
Guix-devel <guix-devel-bounces+me=tobias.gr@gnu.org>
Subject: Re: [PATCH 4/4] environment: Add '--debug' flag.
Date: Wed, 20 Jul 2016 00:17:13 -0400 [thread overview]
Message-ID: <20160720041713.GD21435@jasmine> (raw)
In-Reply-To: <CAL1_imnO7izwehfhRmER=pWN-Ze2zEOtmEv_xqTRhCN2r8Xsyw@mail.gmail.com>
On Tue, Jul 19, 2016 at 09:02:58PM +0200, David Craven wrote:
> > 1. I'd like to use overlay fs (like docker) and create a new overlay
> > for each phase to easily revert a phase.
>
> I think this might also help to debug build reproducibility issues, by
> finding out which phase is introducing them. (Or is it always
> obvious?)
In general, the idea of being able to move between phases like that is
really cool. I don't have any experience with overlayfs, so I can't
comment on that detail.
I wouldn't say it's ever obvious where a reproducibility bug is
introduced, but many of them are timestamps, sometimes with an English
string attached, and that code is usually easy to find.
Thankfully, the Reproducible Builds project has a useful database of
bugs they've found:
https://anonscm.debian.org/git/reproducible/notes.git
next prev parent reply other threads:[~2016-07-20 4:17 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 16:49 [PATCH 0/4] Dipping my toes into guix source David Craven
2016-07-19 16:49 ` [PATCH 1/4] lint: Add packages with suffix ':bin' to 'inputs-should-be-native' David Craven
2016-07-20 10:37 ` Ludovic Courtès
2016-07-20 10:50 ` David Craven
2016-07-20 11:19 ` Efraim Flashner
2016-07-21 12:24 ` Ludovic Courtès
2016-07-21 13:22 ` Vincent Legoll
2016-07-21 16:06 ` Ludovic Courtès
2016-07-21 19:27 ` Tobias Geerinckx-Rice
2016-07-22 13:32 ` Ludovic Courtès
2016-07-22 14:07 ` Vincent Legoll
2016-07-19 16:49 ` [PATCH 2/4] gnu: Rename 'glib' label to 'glib:bin' where appropriate David Craven
2016-07-22 12:57 ` Ludovic Courtès
2016-07-22 13:03 ` David Craven
2016-07-22 17:55 ` David Craven
2016-07-19 16:49 ` [PATCH 3/4] lint: Add 'inputs-should-be-sorted' check David Craven
2016-07-21 13:17 ` Eric Bavier
2016-07-21 16:00 ` Ludovic Courtès
2016-07-19 16:49 ` [PATCH 4/4] environment: Add '--debug' flag David Craven
2016-07-19 17:14 ` Thompson, David
2016-07-19 18:00 ` Tobias Geerinckx-Rice
2016-07-19 18:10 ` David Craven
2016-07-19 19:02 ` David Craven
2016-07-19 19:06 ` Thompson, David
2016-07-19 19:15 ` David Craven
2016-07-20 4:17 ` Leo Famulari [this message]
2016-07-20 10:35 ` Ludovic Courtès
2016-07-20 10:56 ` David Craven
2016-07-19 20:11 ` Danny Milosavljevic
2016-07-20 7:18 ` Alex Kost
2016-07-20 7:35 ` Vincent Legoll
2016-07-20 9:15 ` Pjotr Prins
2016-07-22 19:54 ` Customising linux-libre (was: [PATCH 4/4] environment: Add '--debug' flag.) Tobias Geerinckx-Rice
2016-07-22 19:58 ` Vincent Legoll
2016-07-22 20:00 ` David Craven
2016-07-22 20:03 ` Vincent Legoll
2016-07-22 20:15 ` Customising linux-libre Tobias Geerinckx-Rice
2016-07-22 20:50 ` David Craven
2016-07-22 20:11 ` Tobias Geerinckx-Rice
2016-07-23 10:38 ` Ludovic Courtès
2016-07-21 12:22 ` [PATCH 4/4] environment: Add '--debug' flag Ludovic Courtès
2016-07-21 12:30 ` David Craven
2016-07-21 16:03 ` Ludovic Courtès
2016-07-21 16:12 ` David Craven
2016-07-21 16:38 ` 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=20160720041713.GD21435@jasmine \
--to=leo@famulari.name \
--cc=david@craven.ch \
--cc=guix-devel-bounces+me=tobias.gr@gnu.org \
--cc=guix-devel@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.
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).