tzdata: Update to version 2023b

Message ID 20230327160954.2648286-3-adolf.belka@ipfire.org
State Accepted
Commit 127e0b465b48182f1afd0612740b5d3ef0baf8cd
Headers
Series tzdata: Update to version 2023b |

Commit Message

Adolf Belka March 27, 2023, 4:09 p.m. UTC
  - Update from version 2022g to 2023b
- Update of rootfile not required
- Changelog
Release 2023b - 2023-03-23 19:50:38 -0700
  Briefly:
    Lebanon delays the start of DST this year.
  Changes to future timestamps
    This year Lebanon springs forward April 20/21 not March 25/26.
    (Thanks to Saadallah Itani.)
Release 2023a - 2023-03-22 12:39:33 -0700
  Briefly:
    Egypt now uses DST again, from April through October.
    This year Morocco springs forward April 23, not April 30.
    Palestine delays the start of DST this year.
    Much of Greenland still uses DST from 2024 on.
    America/Yellowknife now links to America/Edmonton.
    tzselect can now use current time to help infer timezone.
    The code now defaults to C99 or later.
    Fix use of C23 attributes.
  Changes to future timestamps
    Starting in 2023, Egypt will observe DST from April's last Friday
    through October's last Thursday.  (Thanks to Ahmad ElDardiry.)
    Assume the transition times are 00:00 and 24:00, respectively.
    In 2023 Morocco's spring-forward transition after Ramadan
    will occur April 23, not April 30.  (Thanks to Milamber.)
    Adjust predictions for future years accordingly.  This affects
    predictions for 2023, 2031, 2038, and later years.
    This year Palestine will delay its spring forward from
    March 25 to April 29 due to Ramadan.  (Thanks to Heba Hamad.)
    Make guesses for future Ramadans too.
    Much of Greenland, represented by America/Nuuk, will continue to
    observe DST using European Union rules.  When combined with
    Greenland's decision not to change the clocks in fall 2023,
    America/Nuuk therefore changes from -03/-02 to -02/-01 effective
    2023-10-29 at 01:00 UTC.  (Thanks to Thomas M. Steenholdt.)
    This change from 2022g doesn't affect timestamps until 2024-03-30,
    and doesn't affect tm_isdst until 2023-03-25.
  Changes to past timestamps
    America/Yellowknife has changed from a Zone to a backward
    compatibility Link, as it no longer differs from America/Edmonton
    since 1970.  (Thanks to Almaz Mingaleev.)  This affects some
    pre-1948 timestamps.  The old data are now in 'backzone'.
  Changes to past time zone abbreviations
    When observing Moscow time, Europe/Kirov and Europe/Volgograd now
    use the abbreviations MSK/MSD instead of numeric abbreviations,
    for consistency with other timezones observing Moscow time.
  Changes to code
    You can now tell tzselect local time, to simplify later choices.
    Select the 'time' option in its first prompt.
    You can now compile with -DTZNAME_MAXIMUM=N to limit time zone
    abbreviations to N bytes (default 255).  The reference runtime
    library now rejects POSIX-style TZ strings that contain longer
    abbreviations, treating them as UTC.  Previously the limit was
    platform dependent and abbreviations were silently truncated to
    16 bytes even when the limit was greater than 16.
    The code by default is now designed for C99 or later.  To build in
    a C89 environment, compile with -DPORT_TO_C89.  To support C89
    callers of the tzcode library, compile with -DSUPPORT_C89.  The
    two new macros are transitional aids planned to be removed in a
    future version, when C99 or later will be required.
    The code now builds again on pre-C99 platforms, if you compile
    with -DPORT_TO_C89.  This fixes a bug introduced in 2022f.
    On C23-compatible platforms tzcode no longer uses syntax like
    'static [[noreturn]] void usage(void);'.  Instead, it uses
    '[[noreturn]] static void usage(void);' as strict C23 requires.
    (Problem reported by Houge Langley.)
    The code's functions now constrain their arguments with the C
    'restrict' keyword consistently with their documentation.
    This may allow future optimizations.
    zdump again builds standalone with ckdadd and without setenv,
    fixing a bug introduced in 2022g.  (Problem reported by panic.)
    leapseconds.awk can now process a leap seconds file that never
    expires; this might be useful if leap seconds are discontinued.
  Changes to commentary
    tz-link.html has a new section "Coordinating with governments and
    distributors".  (Thanks to Neil Fuller for some of the text.)
    To improve tzselect diagnostics, zone1970.tab's comments column is
    now limited to countries that have multiple timezones.
    Note that leap seconds are planned to be discontinued by 2035.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 lfs/tzdata | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
  

Patch

diff --git a/lfs/tzdata b/lfs/tzdata
index 300ed35ad..fb954471f 100644
--- a/lfs/tzdata
+++ b/lfs/tzdata
@@ -24,7 +24,7 @@ 
 
 include Config
 
-VER        = 2022g
+VER        = 2023b
 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 = 582b79cc2317d27f3883042cbca25801397d9e2808ad8d3a340017d635372ef20316ce646a25a43b0ea5d4024841b54925ecc4510613295c39c28647989645cb
-tzcode$(TZCODE_VER).tar.gz_BLAKE2 = b67bb2020913c57cc6bc68d231c53ba645b95305256065e2645bce3b0d71adfaea865ed9bf40f1ec3b4a73aad7e6c48f5ecd0895de6e2d69bed6113d6b579e26
+tzdata$(TZDATA_VER).tar.gz_BLAKE2 = 2738f4248882c771b85de7001ce350136df904ff978e2b5b77c28b4b2a9034b3b5a4fcfa87cc472299f701209922ecc21219e5d1bdeb1c87124988979d2f9672
+tzcode$(TZCODE_VER).tar.gz_BLAKE2 = a6b8f7706114257d1ed28651f59b099a4f1f830c55f53de270a2438639b5ca61145f8561eb487d4a745833f7782e61b0478cb81517a00e42539638337bae3120
 
 install : $(TARGET)