From: Juro Bystricky <juro.bystricky@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: jurobystricky@hotmail.com
Subject: [PATCH 0/1] python-xcbgen: improve reproducibility
Date: Fri, 6 Apr 2018 12:57:20 -0700 [thread overview]
Message-ID: <1523044641-56994-1-git-send-email-juro.bystricky@intel.com> (raw)
This patch addresses the last remaining non-reproducible package for
core-image-minimal (with current "sumo").
A short explanation:
When building core-image-minimal in two different folders with current "sumo"
(http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=sumo ) :
$ source oe-build-env build_1
local.conf:
PACKAGE_CLASSES="package_deb package_rpm package_ipk"
MACHINE="qemux86-64"
$ bitbake core-image-minimal
and
$ source oe-build-env build_2
local.conf:
PACKAGE_CLASSES="package_deb package_rpm package_ipk"
MACHINE="qemux86-64"
$ bitbake core-image-minimal
After binary comparing all packages in build_1/tmp/deploy/[ipk,rpm.deb] to
build_2/tmp/deploy/[ipk,rpm,deb], we get these results:
IPK DEB RPM
Same: 0 0 0
Different: 3952 3952 3952
Total: 3952 3952 3952
Repeating the same with (same host):
$ source oe-build-env build_repro_1
local.conf:
PACKAGE_CLASSES="package_deb package_rpm package_ipk"
MACHINE="qemux86-64"
INHERIT+="reproducible_build"
$ bitbake core-image-minimal
and
$ source oe-build-env build_repro_2
local.conf:
PACKAGE_CLASSES="package_deb package_rpm package_ipk"
MACHINE="qemux86-64"
INHERIT+="reproducible_build"
$ bitbake core-image-minimal
After binary comparing all packages in build_repro_1/tmp/deploy/[ipk,rpm.deb] to
build_repro_2/tmp/deploy/[ipk,rpm,deb], we get these results:
IPK DEB RPM
Same: 3951 3951 3951
Different: 1 1 1
Total: 3952 3952 3952
The remaining package that does not build reproducibly is python-xcbgen.
This is because the package contains .pyc files which contain build-time timestamps.
The python files are compiled with host Python3, which may or may not support
SOURCE_DATE_EPOCH. However, both oe-core python-native and python3-native do support
SOURCE_DATE_EPOCH, so to build the package reproducibly all we need to do is
compile the python files with python3-native. Ideally, we would use python3-native
unconditionally, but building python3-native itself can be computationally quite expensive.
So, as a compromise, we use python3-native only when BUILD_REPRODUCIBLE_BINARIES = '1'
host Python3 otherwise.
Juro Bystricky (1):
python-xcbgen_1.12: improve reproducibility
meta/recipes-graphics/xorg-proto/xcb-proto_1.12.bb | 5 +++++
1 file changed, 5 insertions(+)
--
2.7.4
next reply other threads:[~2018-04-06 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 19:57 Juro Bystricky [this message]
2018-04-06 19:57 ` [PATCH 1/1] python-xcbgen_1.12: improve reproducibility Juro Bystricky
2018-04-11 0:02 ` Burton, Ross
2018-04-11 15:26 ` Bystricky, Juro
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=1523044641-56994-1-git-send-email-juro.bystricky@intel.com \
--to=juro.bystricky@intel.com \
--cc=jurobystricky@hotmail.com \
--cc=openembedded-core@lists.openembedded.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