SUSE-RU-2024:2689-1: important: Recommended update for timezone

SLE-UPDATES null at suse.de
Thu Aug 1 08:30:07 UTC 2024



# Recommended update for timezone

Announcement ID: SUSE-RU-2024:2689-1  
Rating: important  
References:

  * bsc#1219236

  
Affected Products:

  * SUSE Linux Enterprise Server 11 SP4
  * SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE 11-SP4

  
  
An update that has one fix can now be installed.

## Description:

This update for timezone fixes the following issues:

  * timezone was updated to version 2024a:

  * 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
    (bsc#1219236)

  * Palestine springs forward a week later than previously predicted in 2024 and
    2025. Change spring-forward predictions to the second Saturday after
    Ramadan, not the first; this also affects other predictions starting in
    2039.
  * Asia/Ho_Chi_Minh's 1955-07-01 transition occurred at 01:00 not 00:00.
  * From 1947 through 1949, Toronto's transitions occurred at 02:00 not 00:00.
  * In 1911 Miquelon adopted standard time on June 15, not May 15.
  * 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.
  * 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.
  * strftime %s now uses tm_gmtoff if available.
  * The strftime man page documents which struct tm members affect which
    conversion specs, and that tzset is called.

## Patch Instructions:

To install this SUSE update use the SUSE recommended installation methods like
YaST online_update or "zypper patch".  
Alternatively you can run the command listed for your product:

  * SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE 11-SP4  
    zypper in -t patch SUSE-SLE-SERVER-11-SP4-LTSS-EXTREME-CORE-2024-2689=1

  * SUSE Linux Enterprise Server 11 SP4  
    zypper in -t patch SUSE-SLE-SERVER-11-SP4-LTSS-EXTREME-CORE-2024-2689=1

## Package List:

  * SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE 11-SP4 (x86_64)
    * timezone-2024a-0.52.51.1
  * SUSE Linux Enterprise Server 11 SP4 LTSS EXTREME CORE 11-SP4 (noarch)
    * timezone-java-2024a-0.52.51.1
  * SUSE Linux Enterprise Server 11 SP4 (x86_64)
    * timezone-2024a-0.52.51.1
  * SUSE Linux Enterprise Server 11 SP4 (noarch)
    * timezone-java-2024a-0.52.51.1

## References:

  * https://bugzilla.suse.com/show_bug.cgi?id=1219236

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/sle-updates/attachments/20240801/b6c0e303/attachment.htm>


More information about the sle-updates mailing list