Bug 33125

Suggested advisory:
========================

The updated packages update the timezone database to 2024a. Notable changes are:
  - Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  - Palestine springs forward a week later after Ramadan.

References:
https://lwn.net/Articles/970315/
========================

Updated packages in core/updates_testing:
========================
timezone-2024a-1.mga9
timezone-java-2024a-1.mga9

from SRPM:
timezone-2024a-1.mga9.src.rpm

Assignee: bugsquad => qa-bugs
Version: Cauldron => 9
Whiteboard: MGA9TOO => (none)
Status: NEW => ASSIGNED

This not look like a security bug, the last https://bugs.mageia.org/show_bug.cgi?id=31851 similar update I find is not marked as securirty

Keywords: (none) => feedback

I agree: I really hesitated to set this bug as a security issue but finally did it because Debian did the same.

They may have done it because it was required by some other security update (like java).

OK demoting from security level then

---

mga9-64, Plasma
clean update, no issue noted (Sweden)

CC: (none) => fri
Keywords: feedback => (none)
QA Contact: security => (none)
Component: Security => RPM Packages

RH mageia 9 x86_64

 LC_ALL=C urpmi --auto --auto-update
medium "QA Testing (32-bit)" is up-to-date
medium "QA Testing (64-bit)" is up-to-date
medium "Core Release (distrib1)" is up-to-date
medium "Core Updates (distrib3)" is up-to-date
medium "Nonfree Release (distrib11)" is up-to-date
medium "Nonfree Updates (distrib13)" is up-to-date
medium "Tainted Release (distrib21)" is up-to-date
medium "Tainted Updates (distrib23)" is up-to-date
medium "Core 32bit Release (distrib31)" is up-to-date
medium "Core 32bit Updates (distrib32)" is up-to-date
medium "Nonfree 32bit Release (distrib36)" is up-to-date
medium "Tainted 32bit Release (distrib41)" is up-to-date
medium "Tainted 32bit Updates (distrib42)" is up-to-date


installing timezone-2024a-1.mga9.x86_64.rpm timezone-java-2024a-1.mga9.noarch.rpm from //home/katnatek/qa-testing/x86_64
Preparing...                     ##################################################################################################
      1/2: timezone-java         ##################################################################################################
      2/2: timezone              ##################################################################################################
      1/2: removing timezone-java-6:2023c-1.mga9.noarch
                                 ##################################################################################################
      2/2: removing timezone-6:2023c-1.mga9.x86_64
                                 ##################################################################################################

Make the same test in bug#31851 comment#6

timedatectl
               Local time: mié 2024-04-24 13:43:00 CST
           Universal time: mié 2024-04-24 19:43:00 UTC
                 RTC time: mié 2024-04-24 13:43:00
                Time zone: America/Mexico_City (CST, -0600)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: yes

Warning: The system is configured to read the RTC time in the local time zone.
         This mode cannot be fully supported. It will create various problems
         with time zone changes and daylight saving time adjustments. The RTC
         time is never updated, it relies on external facilities to maintain it.
         If at all possible, use RTC in UTC by calling
         'timedatectl set-local-rtc 0'.

Never use before, but the time information looks good

Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0133.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0133.html