All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/2] Makefile: Add SOURCE_DATE_TZ
Date: Wed, 26 Aug 2015 12:01:30 +0200	[thread overview]
Message-ID: <1440583290.2524.1.camel@collins> (raw)
In-Reply-To: <CAFOYHZBq-Nkf+wqcq7PHzTp85LTm+uG+hoMkFQvsBXaGTTTDEw@mail.gmail.com>

Le mercredi 26 ao?t 2015 ? 21:08 +1200, Chris Packham a ?crit :
> On Wed, Aug 26, 2015 at 12:09 AM, Paul Kocialkowski <contact@paulk.fr> wrote:
> > Le jeudi 13 ao?t 2015 ? 18:08 +1200, Chris Packham a ?crit :
> >> Along with SOURCE_DATE_EPOCH SOURCE_DATE_TZ can be used to recreate a
> >> build with a specific date timestamp. This allows the verification of
> >> source supplied with a pre-compiled binary.
> >>
> >> If SOURCE_DATE_EPOCH is supplied SOURCE_DATE_TZ can be used to specify
> >> what will appear in the output of the version command. If SOURCE_DATE_TZ
> >> is not specified UTC will be used.  SOURCE_DATE_TZ on it's own will not
> >> have an affect.
> >
> > I advise against merging this patch given Ximin Luo's comments on v1, at
> > least until this has been properly discussed with the reproducible team
> > and a precise meaning for it has been agreed on.
> >
> 
> I'm happy to go along with that. 1/2 of this series was the "fix". 2/2
> just kind of came up as part of the discussion that followed. Tom, can
> you handle that or do you want me to send a v4 of the series with just
> the first patch?
> 
> Just for my own understanding is the "reproducible team" a u-boot
> thing or a debian thing? I'm not really active in any of the debian
> projects so maybe someone there should pick this up if it's a debian
> thing.

Well, I'm referring to the reproducible team at Debian, but since
they're working with upstream (and they're apparently the only group of
people to do that work), I think it's fair to say they're the reference
when it comes to reproducible builds.

> >> Signed-off-by: Chris Packham <judge.packham@gmail.com>
> >> ---
> >> This is a quick proof of concept that allows some control of how the
> >> timezone is displayed. Now you can do something like
> >>
> >>   make SOURCE_DATE_EPOCH=12345678 SOURCE_DATE_TZ=America/Los_Angeles
> >>
> >>
> >> Changes in v3:
> >> - Drop RFC
> >>
> >> Changes in v2: None
> >>
> >>  Makefile | 7 ++++---
> >>  README   | 9 ++++++---
> >>  2 files changed, 10 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/Makefile b/Makefile
> >> index 3ff063a..609b595 100644
> >> --- a/Makefile
> >> +++ b/Makefile
> >> @@ -1281,9 +1281,10 @@ endef
> >>  define filechk_timestamp.h
> >>       (if test -n "$${SOURCE_DATE_EPOCH}"; then \
> >>               SOURCE_DATE="@$${SOURCE_DATE_EPOCH}"; \
> >> -             LC_ALL=C date -u -d "$${SOURCE_DATE}" +'#define U_BOOT_DATE "%b %d %C%y"'; \
> >> -             LC_ALL=C date -u -d "$${SOURCE_DATE}" +'#define U_BOOT_TIME "%T"'; \
> >> -             LC_ALL=C date -u -d "$${SOURCE_DATE}" +'#define U_BOOT_TZ "%z"'; \
> >> +             SOURCE_TZ="$${SOURCE_DATE_TZ:-UTC}"; \
> >> +             TZ="$${SOURCE_TZ}" LC_ALL=C date -d "$${SOURCE_DATE}" +'#define U_BOOT_DATE "%b %d %C%y"'; \
> >> +             TZ="$${SOURCE_TZ}" LC_ALL=C date -d "$${SOURCE_DATE}" +'#define U_BOOT_TIME "%T"'; \
> >> +             TZ="$${SOURCE_TZ}" LC_ALL=C date -d "$${SOURCE_DATE}" +'#define U_BOOT_TZ "%z"'; \
> >>       else \
> >>               LC_ALL=C date +'#define U_BOOT_DATE "%b %d %C%y"'; \
> >>               LC_ALL=C date +'#define U_BOOT_TIME "%T"'; \
> >> diff --git a/README b/README
> >> index 1bcb63c..d2e3e94 100644
> >> --- a/README
> >> +++ b/README
> >> @@ -5087,11 +5087,14 @@ Reproducible builds
> >>  In order to achieve reproducible builds, timestamps used in the U-Boot build
> >>  process have to be set to a fixed value.
> >>
> >> -This is done using the SOURCE_DATE_EPOCH environment variable.
> >> -SOURCE_DATE_EPOCH is to be set on the build host's shell, not as a configuration
> >> -option for U-Boot or an environment variable in U-Boot.
> >> +This is done using the SOURCE_DATE_EPOCH and SOURCE_DATE_TZ environment
> >> +variables. These are to be set on the build host's shell, not as a
> >> +configuration option for U-Boot or an environment variable in U-Boot.
> >>
> >>  SOURCE_DATE_EPOCH should be set to a number of seconds since the epoch, in UTC.
> >> +SOURCE_DATE_TZ will default to UTC but can be set to another timezone and is
> >> +used to determine how the date is displayed (tzselect(1) can be used to
> >> +determine an appropriate value).
> >>
> >>  Building the Software:
> >>  ======================
> >

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150826/39380ba1/attachment.sig>

  parent reply	other threads:[~2015-08-26 10:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13  6:08 [U-Boot] [PATCH v3 1/2] Makefile: Use correct timezone for U_BOOT_TZ Chris Packham
2015-08-13  6:08 ` [U-Boot] [PATCH v3 2/2] Makefile: Add SOURCE_DATE_TZ Chris Packham
2015-08-25 12:09   ` Paul Kocialkowski
2015-08-26  9:08     ` Chris Packham
2015-08-26  9:29       ` [U-Boot] about reproducible builds (was Re: [PATCH v3 2/2] Makefile: Add SOURCE_DATE_TZ) Holger Levsen
2015-08-26 10:01       ` Paul Kocialkowski [this message]
2015-08-27 11:50       ` [U-Boot] [PATCH v3 2/2] Makefile: Add SOURCE_DATE_TZ Tom Rini
2015-08-25 10:22 ` [U-Boot] [PATCH v3 1/2] Makefile: Use correct timezone for U_BOOT_TZ Andreas Bießmann
2015-08-25 12:10 ` Paul Kocialkowski
2015-08-28 21:02 ` [U-Boot] [U-Boot, v3, " Tom Rini

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=1440583290.2524.1.camel@collins \
    --to=contact@paulk.fr \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.