From: Martin Jansa <martin.jansa@gmail.com>
To: "Bystricky, Juro" <juro.bystricky@intel.com>
Cc: "jurobystricky@hotmail.com" <jurobystricky@hotmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] Reproducible binaries
Date: Wed, 26 Apr 2017 20:33:06 +0200 [thread overview]
Message-ID: <20170426183306.GF3258@jama> (raw)
In-Reply-To: <CA+chaQe4o+LKRV5voXOhoPoWEGjx2cmXedsagmQEgouAP6jMvQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]
On Wed, Apr 26, 2017 at 07:52:02PM +0200, Martin Jansa wrote:
> What about passing the seed value (currently created based on last commit
> in repo you're building from - which doesn't need to be oe-core repository
> right?) to make it easier for people to pass whatever value works for them?
> even some constant value in DISTRO config.
It looks like some words disappeared when I clicked the send button.
Well I don't have any buttons in mutt so that might be the reason.
I wasnted to say "passing the seed value" through some separate variable
which is easy to override from somewhere else.
e.g.
export PRELINK_TIMESTAMP=`git log -1 --pretty=%ct `
in image-prelink.bbclass:prelink_image() is a bit difficult to override.
>
> On Wed, Apr 26, 2017 at 6:43 PM, Bystricky, Juro <juro.bystricky@intel.com>
> wrote:
>
> >
> > > But not for 2 different builds with slightly modified metadata (e.g.
> > > just because top commit is different in whatever build repository you're
> > > running from even when it doesn't have any effect in your image), right?
> > >
> >
> > This may be addressed in the future. Presently, the goal is to ensure that
> > if we
> > use identical repositories we get identical results. This should not depend
> > on the time/date, build folder or even Linux distro. By identical results
> > I mean binary identical comparison of the resulting "deploy" folders.
> > (images, packages, licenses). So for example, there should be no binary
> > differences
> > between the two images of core-image-minimal.rootfs.ext4.
> > In your case (slightly different repos), the difference would be presented
> > as different time stamps for /etc/version and /etc/timestamp only.
> >
> >
> > > So it doesn't fix the files-in-image.txt differences as described in:
> > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=5866
> > >
> >
> > Eventually it will. There is still ways to go and this patch set is just
> > the first
> > kick at the can.
> >
> >
> >
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2017-04-26 18:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 18:14 [PATCH 0/4] Reproducible binaries Juro Bystricky
2017-04-25 18:14 ` [PATCH 1/4] bitbake.conf: new variable BUILD_REPRODUCIBLE_BINARIES Juro Bystricky
2017-04-25 18:14 ` [PATCH 2/4] base.bbclass: initial support for binary reproducibility Juro Bystricky
2017-04-25 18:14 ` [PATCH 3/4] image-preling.bbclass: support " Juro Bystricky
2017-04-25 18:14 ` [PATCH 4/4] rootfs-postcommands.bbclass: " Juro Bystricky
2017-04-25 18:36 ` [PATCH 0/4] Reproducible binaries Martin Jansa
2017-04-25 19:24 ` Bystricky, Juro
2017-04-26 7:42 ` Martin Jansa
2017-04-26 16:43 ` Bystricky, Juro
2017-04-26 17:52 ` Martin Jansa
2017-04-26 18:22 ` Khem Raj
2017-04-26 18:33 ` Martin Jansa [this message]
2017-04-26 19:50 ` Bystricky, Juro
2017-04-27 9:50 ` Joshua Lock
2017-04-27 15:14 ` Bystricky, Juro
2017-04-25 23:22 ` Trevor Woerner
2017-04-26 7:25 ` Patrick Ohly
2017-04-26 16:27 ` 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=20170426183306.GF3258@jama \
--to=martin.jansa@gmail.com \
--cc=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