From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 00/18] Reproducible builds
Date: Wed, 23 Nov 2016 13:54:35 +0100 [thread overview]
Message-ID: <3668997.WEC4FqhPHV@sagittea> (raw)
In-Reply-To: <20161123132414.30eade0d@free-electrons.com>
Hello Thomas,
On Wednesday 23 November 2016 13:24:14 Thomas Petazzoni wrote:
> Hello,
>
> On Wed, 23 Nov 2016 12:08:00 +0100, J?r?me Pouiller wrote:
> > This series try to continue work initiated by Gilles Chanteperdrix:
> > http://lists.busybox.net/pipermail/buildroot/2016-April/thread.html#160064
> > http://lists.busybox.net/pipermail/buildroot/2016-June/thread.html#163905
> >
> > I dropped some patchs from original series because either:
> > - I handled things differently (timestamps in images, support SOURCE_DATE_EPOCH
> > in gcc, ...)
> > - I didn't had time to test them them (sysroot, cpio, cdrkit, iso9660,...)
> > - They doesn't seems necessary anymore (libtool, libgcrypt, libgpg-error, ...)
> >
> > This version focuses on timestamps. It provide good enough results as soon as
> > OUTDIR and TOPDIR are the same. Indeed build path appear in plenty of files.
> > Only patch called "remove full path from .pyc" try to solve this issue. Another
> > big step could be done by removing rpaths from ELF generated with libtool.
> >
> > Other thing known to break reproducibility:
> > - use of lzop (it unconditionally include timestamps in result)
> > - /!\ since we build our own toolchain and toolchain include BR2_FULL_VERSION,
> > ccache is incompatible with reproducible
> >
> > Since this feature is experimental I did not (yet) reported these
> > incompatibilities in menuconfig.
>
> What are the changes between v2 and v3? There is no changelog, either
> in the cover letter nor in the patches themselves. It would be useful
> to have a changelog.
Oops, I have forgotten --notes. I resend soon.
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
prev parent reply other threads:[~2016-11-23 12:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 11:08 [Buildroot] [PATCH v3 00/18] Reproducible builds Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 01/18] reproducibility: generate SOURCE_DATE_EPOCH Jérôme Pouiller
2016-11-23 11:15 ` Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 02/18] reproducible: fix DATE/TIME macros in toolchain-wrapper Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 03/18] reproducible: add '-n' to gzip invocations Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 04/18] fs/tar: make results reproducible Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 05/18] reproducibility/linux: override build timestamp Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 06/18] reproducibility/linux: inhibit build-id Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 07/18] reproducibility/busybox: disable build timestamps Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 08/18] reproducible: lock modification times in $TARGET_DIR Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 09/18] fakedate: new package Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 10/18] core: do not reset DEPENDENCIES_HOST_PREREQ in dependencies.mk Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 11/18] reproducible: enable fakedate Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 12/18] pycompile: allow to force compilation Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 13/18] python2: generate reproducible .pyc Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 14/18] python3: " Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 15/18] python2: remove full path from .pyc Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 16/18] python3: " Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 17/18] reproducible: improve help text Jérôme Pouiller
2016-11-23 11:08 ` [Buildroot] [PATCH v3 18/18] reproducible: fix coding style Jérôme Pouiller
2016-11-23 12:24 ` [Buildroot] [PATCH v3 00/18] Reproducible builds Thomas Petazzoni
2016-11-23 12:54 ` Jérôme Pouiller [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=3668997.WEC4FqhPHV@sagittea \
--to=jezz@sysmic.org \
--cc=buildroot@busybox.net \
/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