tzdata: Update to version 2024a

  - Update from version 2023d to 2024a
- Update of rootfile not required
- Changelog
    2024a
	  Briefly:
	    Kazakhstan unifies on UTC+5 beginning 2024-03-01.
	    Palestine springs forward a week later after Ramadan.
	    zic no longer pretends to support indefinite-past DST.
	    localtime no longer mishandles Ciudad Juárez in 2422.
	  Changes to future timestamps
	    Kazakhstan unifies on UTC+5.  This affects Asia/Almaty and
	     Asia/Qostanay which together represent the eastern portion of the
	     country that will transition from UTC+6 on 2024-03-01 at 00:00 to
	     join the western portion.  (Thanks to Zhanbolat Raimbekov.)
	    Palestine springs forward a week later than previously predicted
	     in 2024 and 2025.  (Thanks to Heba Hamad.)  Change spring-forward
	     predictions to the second Saturday after Ramadan, not the first;
	     this also affects other predictions starting in 2039.
	  Changes to past timestamps
	    Asia/Ho_Chi_Minh's 1955-07-01 transition occurred at 01:00
	     not 00:00.  (Thanks to Đoàn Trần Công Danh.)
	    From 1947 through 1949, Toronto's transitions occurred at 02:00
	     not 00:00.  (Thanks to Chris Walton.)
	    In 1911 Miquelon adopted standard time on June 15, not May 15.
	  Changes to code
	    The FROM and TO columns of Rule lines can no longer be "minimum"
	     or an abbreviation of "minimum", because TZif files do not support
	     DST rules that extend into the indefinite past - although these
	     rules were supported when TZif files had only 32-bit data, this
	     stopped working when 64-bit TZif files were introduced in 1995.
	     This should not be a problem for realistic data, since DST was
	     first used in the 20th century.  As a transition aid, FROM columns
	     like "minimum" are now diagnosed and then treated as if they were
	     the year 1900; this should suffice for TZif files on old systems
	     with only 32-bit time_t, and it is more compatible with bugs in
	     2023c-and-earlier localtime.c.  (Problem reported by Yoshito
	     Umaoka.)
	    localtime and related functions no longer mishandle some
	     timestamps that occur about 400 years after a switch to a time
	     zone with a DST schedule.  In 2023d data this problem was visible
	     for some timestamps in November 2422, November 2822, etc. in
	     America/Ciudad_Juarez.  (Problem reported by Gilmore Davidson.)
	    strftime %s now uses tm_gmtoff if available.  (Problem and draft
	     patch reported by Dag-Erling Smørgrav.)
	  Changes to build procedure
	    The leap-seconds.list file is now copied from the IERS instead of
	     from its downstream counterpart at NIST, as the IERS version is
	     now in the public domain too and tends to be more up-to-date.
	     (Thanks to Martin Burnicki for liaisoning with the IERS.)
	  Changes to documentation
	    The strftime man page documents which struct tm members affect
	     which conversion specs, and that tzset is called.  (Problems
	     reported by Robert Elz and Steve Summit.)

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

Reviewed-by: Michael Tremer <michael.tremer@ipfire.org>

> On 25 Apr 2024, at 22:43, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> - Update from version 2023d to 2024a
> - Update of rootfile not required
> - Changelog
>    2024a
>  Briefly:
>    Kazakhstan unifies on UTC+5 beginning 2024-03-01.
>    Palestine springs forward a week later after Ramadan.
>    zic no longer pretends to support indefinite-past DST.
>    localtime no longer mishandles Ciudad Juárez in 2422.
>  Changes to future timestamps
>    Kazakhstan unifies on UTC+5.  This affects Asia/Almaty and
>     Asia/Qostanay which together represent the eastern portion of the
>     country that will transition from UTC+6 on 2024-03-01 at 00:00 to
>     join the western portion.  (Thanks to Zhanbolat Raimbekov.)
>    Palestine springs forward a week later than previously predicted
>     in 2024 and 2025.  (Thanks to Heba Hamad.)  Change spring-forward
>     predictions to the second Saturday after Ramadan, not the first;
>     this also affects other predictions starting in 2039.
>  Changes to past timestamps
>    Asia/Ho_Chi_Minh's 1955-07-01 transition occurred at 01:00
>     not 00:00.  (Thanks to Đoàn Trần Công Danh.)
>    From 1947 through 1949, Toronto's transitions occurred at 02:00
>     not 00:00.  (Thanks to Chris Walton.)
>    In 1911 Miquelon adopted standard time on June 15, not May 15.
>  Changes to code
>    The FROM and TO columns of Rule lines can no longer be "minimum"
>     or an abbreviation of "minimum", because TZif files do not support
>     DST rules that extend into the indefinite past - although these
>     rules were supported when TZif files had only 32-bit data, this
>     stopped working when 64-bit TZif files were introduced in 1995.
>     This should not be a problem for realistic data, since DST was
>     first used in the 20th century.  As a transition aid, FROM columns
>     like "minimum" are now diagnosed and then treated as if they were
>     the year 1900; this should suffice for TZif files on old systems
>     with only 32-bit time_t, and it is more compatible with bugs in
>     2023c-and-earlier localtime.c.  (Problem reported by Yoshito
>     Umaoka.)
>    localtime and related functions no longer mishandle some
>     timestamps that occur about 400 years after a switch to a time
>     zone with a DST schedule.  In 2023d data this problem was visible
>     for some timestamps in November 2422, November 2822, etc. in
>     America/Ciudad_Juarez.  (Problem reported by Gilmore Davidson.)
>    strftime %s now uses tm_gmtoff if available.  (Problem and draft
>     patch reported by Dag-Erling Smørgrav.)
>  Changes to build procedure
>    The leap-seconds.list file is now copied from the IERS instead of
>     from its downstream counterpart at NIST, as the IERS version is
>     now in the public domain too and tends to be more up-to-date.
>     (Thanks to Martin Burnicki for liaisoning with the IERS.)
>  Changes to documentation
>    The strftime man page documents which struct tm members affect
>     which conversion specs, and that tzset is called.  (Problems
>     reported by Robert Elz and Steve Summit.)
> 
> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
> ---
> lfs/tzdata | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/lfs/tzdata b/lfs/tzdata
> index 921c5e66c..05c9a257f 100644
> --- a/lfs/tzdata
> +++ b/lfs/tzdata
> @@ -1,7 +1,7 @@
> ###############################################################################
> #                                                                             #
> # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2007-2023  IPFire Team  <info@ipfire.org>                     #
> +# Copyright (C) 2007-2024  IPFire Team  <info@ipfire.org>                     #
> #                                                                             #
> # This program is free software: you can redistribute it and/or modify        #
> # it under the terms of the GNU General Public License as published by        #
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 2023d
> +VER        = 2024a
> 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 = b79be37a8a258745d162a575c795ee6476b4fa5f6d2f7b562d9431a238eca276a1747a983778291184fc6e40a0c1f5e6284d41290fd6d1d3bd3118bda83f426e
> -tzcode$(TZCODE_VER).tar.gz_BLAKE2 = 3e759de2e1dfe033bb98b5af5239631ef5dc33e25b6aeb95ab3e6041d5db3dd1b1cb8b210f072bc0d671117f2ad162cdcdcb3ecae97aa2d3be3bc2e809845666
> +tzdata$(TZDATA_VER).tar.gz_BLAKE2 = 5ec49bbce704411a1d8b3f018b0d8f6c7de24c5600e0cb6c61a7ee29b4a49b1e502d23b40bce6584ea0aa9b66327321608cbabb994071ec4ca2b3a496aa2d621
> +tzcode$(TZCODE_VER).tar.gz_BLAKE2 = f3b8d1e7735ad858d071df564a8e11ac4d252b97a5729fa6c282112ff3903f7d35897735920b4466a926ef647dc283356879134046805411c694efd3fd89b282
> 
> install : $(TARGET)
> 
> -- 
> 2.44.0
>