From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] host-tz-database: Version bump. 2022a -> 2022f.
Date: Fri, 18 Nov 2022 22:07:40 +0100 [thread overview]
Message-ID: <20221118210740.1521688-1-christian.melki@t2data.com> (raw)
Bunch of bugfixes to zones and code.
IMO, the most notable one is 64-bit time_t on 32-bit platforms.
Needs glibc 2.34+, since that optionally supports the same.
That allows 32-bit platforms to support timestamps after 2038.
To force 32-bit time_t, -D_TIME_BITS=32 must be used.
Not that any of this matter much, since tzcode binaries
don't make it to target. Just a curiosity thing.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/host-tz-database.make | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/rules/host-tz-database.make b/rules/host-tz-database.make
index fa3f7a652..373399694 100644
--- a/rules/host-tz-database.make
+++ b/rules/host-tz-database.make
@@ -17,10 +17,10 @@ HOST_PACKAGES-$(PTXCONF_HOST_TZ_DATABASE) += host-tz-database
#
HOST_TZ_DATABASE := tz-database
HOST_TZ_DATABASE_DIR := $(HOST_BUILDDIR)/$(HOST_TZ_DATABASE)
-HOST_TZ_DATABASE_VERSION:= 2022a
+HOST_TZ_DATABASE_VERSION:= 2022f
TZCODE_VERSION := $(HOST_TZ_DATABASE_VERSION)
-TZCODE_MD5 := fdc790effd7b01d29837fb27b3e81672
+TZCODE_MD5 := 3c253af4570d72e7df6950ecede5dc80
TZCODE := tzcode$(TZCODE_VERSION)
TZCODE_SUFFIX := tar.gz
TZCODE_URL := \
@@ -31,7 +31,7 @@ TZCODE_DIR := $(HOST_TZ_DATABASE_DIR)
TZCODE_STRIP_LEVEL := 0
TZDATA_VERSION := $(HOST_TZ_DATABASE_VERSION)
-TZDATA_MD5 := 081662184f3b902f8e5d96816568432e
+TZDATA_MD5 := 7dbb997b73a0504b61a83a85988d7771
TZDATA := tzdata$(TZDATA_VERSION)
TZDATA_SUFFIX := tar.gz
TZDATA_URL := \
--
2.34.1
next reply other threads:[~2022-11-18 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 21:07 Christian Melki [this message]
2022-11-22 13:20 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20221118210740.1521688-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--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