Chile is delaying the DST by one week for 2022
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tzdata (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
Bionic |
Confirmed
|
Undecided
|
Unassigned | ||
Focal |
Confirmed
|
Undecided
|
Unassigned | ||
Jammy |
Confirmed
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
High
|
Unassigned |
Bug Description
New timezone data, with the following timezones impacted:
- Chile will spring forward on 2022-09-11, not 2022-09-04 (America/Santiago)
- Iran no longer observes DST (Asia/Tehran)
Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/
[Test Case for all releases]
1) zdump -v America/Santiago | grep 'Sep.*2022'
-> should indicate Sep 11, not Sep 4
2) zdump -v Asia/Tehran | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(
assert(
The assertions would crash on 2022a.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-)
Nothing should be returned by the above command.
[Original report]
Chile is delaying the start of Daylight Saving Time (DST) by one week this year [1],[2].
DST timezone in Chile will start on midnight of September 11th; and will end on April 1st, 2023.
Debian's 2022c-1 and 2022b-1 versions of tzdata contain the fix for this.
Upstream commit :
https:/
We need to fix this in all or releases back to Xenial.
[1] https:/
[2] https:/
Changed in tzdata (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.