From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] tzdata: Update to version 2023c
Date: Wed, 30 Aug 2023 16:17:38 +0200 [thread overview]
Message-ID: <20230830141742.2723629-7-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230830141742.2723629-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
- Update from version 2023b to 2023c
- Update of rootfile not required.
- Changelog
Release 2023c - 2023-03-28 12:42:14 -0700
Changes to past and future timestamps
Model Lebanon's DST chaos by reverting data to tzdb 2023a.
(Thanks to Rany Hany for the heads-up.)
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/tzdata | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/tzdata b/lfs/tzdata
index fb954471f..2893584b3 100644
--- a/lfs/tzdata
+++ b/lfs/tzdata
@@ -24,7 +24,7 @@
include Config
-VER = 2023b
+VER = 2023c
TZDATA_VER = $(VER)
TZCODE_VER = $(VER)
@@ -45,8 +45,8 @@ objects = tzdata$(TZDATA_VER).tar.gz tzcode$(TZCODE_VER).tar.gz
tzdata$(TZDATA_VER).tar.gz = $(DL_FROM)/tzdata$(TZDATA_VER).tar.gz
tzcode$(TZCODE_VER).tar.gz = $(DL_FROM)/tzcode$(TZCODE_VER).tar.gz
-tzdata$(TZDATA_VER).tar.gz_BLAKE2 = 2738f4248882c771b85de7001ce350136df904ff978e2b5b77c28b4b2a9034b3b5a4fcfa87cc472299f701209922ecc21219e5d1bdeb1c87124988979d2f9672
-tzcode$(TZCODE_VER).tar.gz_BLAKE2 = a6b8f7706114257d1ed28651f59b099a4f1f830c55f53de270a2438639b5ca61145f8561eb487d4a745833f7782e61b0478cb81517a00e42539638337bae3120
+tzdata$(TZDATA_VER).tar.gz_BLAKE2 = 8a50aa5f338565d86b8fa5428c138b251bd8dcc3ea66c144b49625d02c5c7aa27f1ace66babd36f10f75cf5eb832ec327b9c2e8adb0384c450130d1ee8c45562
+tzcode$(TZCODE_VER).tar.gz_BLAKE2 = 707ae61740543f3a61520f67176c391ba1e4a8d7858ede4cadd837935be9a9aeb5cf8914049838aaed2f57d7dc4e1df33f29913e143d23deb58011b3e103aade
install : $(TARGET)
--
2.42.0
next prev parent reply other threads:[~2023-08-30 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 14:17 [PATCH] foomatic: Update engine to 4.0.13 and db to 20230828 Adolf Belka
2023-08-30 14:17 ` [PATCH] tcl: Update to version 8.6.13 Adolf Belka
2023-08-30 14:17 ` [PATCH] tor: Update to version 0.4.8.4 Adolf Belka
2023-08-30 14:17 ` [PATCH] traceroute: Update to version 2.1.2 Adolf Belka
2023-08-30 14:17 ` [PATCH] transmission: Update to version 4.0.4 Adolf Belka
2023-08-30 14:17 ` [PATCH] tshark: Update to version 4.0.8 Adolf Belka
2023-08-30 14:17 ` Adolf Belka [this message]
2023-08-30 14:17 ` [PATCH] util-linux: Update to version 2.39.2 Adolf Belka
2023-08-30 14:17 ` [PATCH] whois: Update to version 5.5.18 Adolf Belka
2023-08-30 14:17 ` [PATCH] wireless-regdb: Update to version 2023-05-03 Adolf Belka
2023-08-30 14:17 ` [PATCH] xinetd: Update to version 2.3.15.4 Adolf Belka
2023-08-30 16:26 ` Michael Tremer
2023-08-30 21:55 ` Adolf Belka
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=20230830141742.2723629-7-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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