Package: tzdata
Version: 2026b-0+deb12u1
Severity: normal
X-Debbugs-Cc: [email protected]

Dear Maintainer,

What led up to the situation?

I am using Debian 12 (Bookworm/oldstable) with tzdata 2026b-0+deb12u1.
The IANA tzdata 2026c release introduced a change making Morocco
UTC+0 year-round from 2026-09-20. Debian already provides tzdata 2026c
for newer releases, but Bookworm still provides 2026b.

What exactly did you do?

I configured the system timezone as Africa/Casablanca and checked it
after 2026-09-20 using:

timedatectl

What was the outcome?

The system reports:

Time zone: Africa/Casablanca (+01, +0100)

because the Bookworm tzdata package does not contain the new Moroccan
timezone rule.

What outcome did you expect instead?

I expected Africa/Casablanca to report UTC+0 after 2026-09-20, in accordance
with Morocco's current civil-time rules and the corresponding IANA tzdata
2026c rule.

Could tzdata 2026c (or the corresponding timezone correction) be made
available for Debian 12 Bookworm/oldstable?

-- System Information:
Debian Release: 12.15
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-53-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.82

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
  tzdata/Zones/Pacific:
  tzdata/Zones/Atlantic:
  tzdata/Zones/Asia:
  tzdata/Zones/America:
  tzdata/Zones/Australia:
  tzdata/Zones/US:
* tzdata/Areas: Africa
  tzdata/Zones/Antarctica:
* tzdata/Zones/Etc: UTC
  tzdata/Zones/Indian:
  tzdata/Zones/Arctic:
  tzdata/Zones/Europe:
* tzdata/Zones/Africa: Casablanca

Reply via email to