From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 5/6] tz: version bump 2017c -> 2018e
Date: Tue, 26 Jun 2018 16:02:29 +0200 [thread overview]
Message-ID: <20180626140229.g3tkathjlfrgydv4@pengutronix.de> (raw)
In-Reply-To: <20180626065652.18064-6-ada@thorsis.com>
On Tue, Jun 26, 2018 at 08:56:51AM +0200, Alexander Dahl wrote:
> This includes the usual changes to past and future timestamps.
>
> Additional things of interest:
>
> * Since 2018a builders no longer heed to specify -DHAVE_SNPRINTF, we may
> want to revert ee06ca66eb later.
>
> * Since 2018a default install locations of the upstream package changed.
> However we already set and use TZDIR and that should still be
> sufficient for the ptxdist use case.
>
> * Since 2018 parallelized builds with -j should be safe.
>
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
Tested-by: Roland Hieber <r.hieber@pengutronix.de>
> ---
> rules/host-tz-database.make | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/rules/host-tz-database.make b/rules/host-tz-database.make
> index ce245feb5..03b4bd906 100644
> --- a/rules/host-tz-database.make
> +++ b/rules/host-tz-database.make
> @@ -20,8 +20,8 @@ HOST_PACKAGES-$(PTXCONF_HOST_TZ_DATABASE) += host-tz-database
> HOST_TZ_DATABASE := tz-database
> HOST_TZ_DATABASE_DIR := $(HOST_BUILDDIR)/$(HOST_TZ_DATABASE)
>
> -TZCODE_VERSION := 2017c
> -TZCODE_MD5 := 2fe6986231db5182c61d565021a0cd7b
> +TZCODE_VERSION := 2018e
> +TZCODE_MD5 := c4d7df0fff7ba5588b32c5f27e2caf97
> TZCODE := tzcode$(TZCODE_VERSION)
> TZCODE_SUFFIX := tar.gz
> TZCODE_URL := \
> @@ -31,8 +31,8 @@ $(TZCODE_SOURCE) := TZCODE
> TZCODE_DIR := $(HOST_TZ_DATABASE_DIR)
> TZCODE_STRIP_LEVEL := 0
>
> -TZDATA_VERSION := 2017c
> -TZDATA_MD5 := 1e751e7e08f8b68530674f04619d894d
> +TZDATA_VERSION := 2018e
> +TZDATA_MD5 := 97d654f4d7253173b3eeb76a836dd65e
> TZDATA := tzdata$(TZDATA_VERSION)
> TZDATA_SUFFIX := tar.gz
> TZDATA_URL := \
> --
> 2.11.0
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Roland Hieber | r.hieber@pengutronix.de |
Pengutronix e.K. | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-06-26 14:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 6:56 [ptxdist] [PATCH 0/6] timezone cleanup and tz update Alexander Dahl
2018-06-26 6:56 ` [ptxdist] [PATCH 1/6] timezone: Remove menu entry 'Mideast' Alexander Dahl
2018-06-26 6:56 ` [ptxdist] [PATCH 2/6] timezone: Cleanup timezone file removal Alexander Dahl
2018-06-26 13:50 ` Roland Hieber
2018-06-26 14:01 ` Alexander Dahl
2018-06-26 14:04 ` Alexander Dahl
2018-06-26 14:05 ` Roland Hieber
2018-06-26 6:56 ` [ptxdist] [PATCH 3/6] timezone: Order entries Alexander Dahl
2018-06-26 6:56 ` [ptxdist] [PATCH 4/6] timezone: Add missing zoneinfo entries Alexander Dahl
2018-06-26 6:56 ` [ptxdist] [PATCH 5/6] tz: version bump 2017c -> 2018e Alexander Dahl
2018-06-26 14:02 ` Roland Hieber [this message]
2018-06-26 6:56 ` [ptxdist] [PATCH 6/6] Revert "host-tz-database: use snprintf provided by the host compiler" Alexander Dahl
2018-06-26 14:03 ` Roland Hieber
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=20180626140229.g3tkathjlfrgydv4@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox