[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
** Changed in: tzdata (Ubuntu Xenial)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Fix Released
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
Hi. I have Ubuntu 16 Xenial servers. Is there any way I can update tzdata?
Up till now, I've noticed that my version is from Jan 2021 after running apt
update and install tzdata, so I figure Xenial won't update further than that.
Can this be fixed in some way?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
Hi, at this time (02 Sept 10:45 Chilean time), the package currently 20%
phased (in Jammy), meaning it will be 100% phased in 8 x 6h = 48h if the
phasing is still 6 hours per 10%, which is roughly 10 hours after the
original DST for Chile. So some people will have their clocks incorrect
for some time. Is it possible to skip phasing for this package?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
This bug was fixed in the package tzdata - 2022c-0ubuntu0.18.04.0
---
tzdata (2022c-0ubuntu0.18.04.0) bionic; urgency=medium
* New upstream release (LP: #1986984):
- Chile will spring forward on 2022-09-11, not 2022-09-04
- Iran no longer observes DST
* d/po/*.po: change Kiev msgids to Kyiv to reflect upstream change
-- Simon Chopin Tue, 30 Aug 2022 10:20:23 +0200
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
This bug was fixed in the package tzdata - 2022c-0ubuntu0.20.04.0
---
tzdata (2022c-0ubuntu0.20.04.0) focal; urgency=medium
* New upstream release (LP: #1986984):
- Chile will spring forward on 2022-09-11, not 2022-09-04
- Iran no longer observes DST
* Update ICU data to latest (2022b)
* d/po/*.po: change Kiev msgids to Kyiv to reflect upstream change
-- Simon Chopin Tue, 30 Aug 2022 10:16:55 +0200
** Changed in: tzdata (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: tzdata (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
This bug was fixed in the package tzdata - 2022c-0ubuntu0.22.04.0
---
tzdata (2022c-0ubuntu0.22.04.0) jammy; urgency=medium
* New upstream release (LP: #1986984):
- Chile will spring forward on 2022-09-11, not 2022-09-04
- Iran no longer observes DST
* Update ICU data to latest (2022b)
* d/po/*.po: change Kiev msgids to Kyiv to reflect upstream change
-- Simon Chopin Tue, 30 Aug 2022 10:04:54 +0200
** Changed in: tzdata (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
We've tried this with the Chile timezone and it worked fine.
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date -s "10 SEP 2022 23:59:00"
Sat Sep 10 23:59:00 -04 2022
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date
Sat Sep 10 23:59:03 -04 2022
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date
Sun Sep 11 01:00:02 -03 2022
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date -s "3 SEP 2022 23:59:00"
Sat Sep 3 23:59:00 -04 2022
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date
Sun Sep 4 00:00:18 -04 2022
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
I've retried the mtail test.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
I verified the upload on Jammy, Focal and Bionic via fresh LXC
containers, using the attached script.
For the ESM releases, it has been handled by sbeattie from the Security
Team. As I understand, the packages are already available in the ESM
security PPA (I don't have access to it).
** Attachment added: "validate.sh"
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+attachment/5612734/+files/validate.sh
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-jammy
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
https://wiki.ubuntu.com/StableReleaseUpdates#tzdata says "Uploads should
also be made to any releases supported via ESM". I see a bug task but
nothing in the queue. What are your plans on this, please?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
Hello Jason, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.22.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: tzdata (Ubuntu Jammy)
Status: Confirmed => Fix Committed
** Tags added: verification-needed verification-needed-jammy
** Changed in: tzdata (Ubuntu Focal)
Status: Confirmed => Fix Committed
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
Apologies for the metadata bug traffic, I hadn't realized there were
duplicates, and actually use different bug numbers in the SRU and devel
uploads. Marking this manually as released on Kinetic, as the SRU
uploads use this bug number.
** Changed in: tzdata (Ubuntu Kinetic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Confirmed
Status in tzdata source package in Focal:
Confirmed
Status in tzdata source package in Jammy:
Confirmed
Status in tzdata source package in Kinetic:
Fix Released
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
Please proceed! Approved.
** Changed in: tzdata (Ubuntu Kinetic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Confirmed
Status in tzdata source package in Focal:
Confirmed
Status in tzdata source package in Jammy:
Confirmed
Status in tzdata source package in Kinetic:
Triaged
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
** Changed in: tzdata (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Focal)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Confirmed
Status in tzdata source package in Focal:
Confirmed
Status in tzdata source package in Jammy:
Confirmed
Status in tzdata source package in Kinetic:
Triaged
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
This update has been prepared in the following PPA:
https://launchpad.net/~schopin/+archive/ubuntu/tzdata
The kinetic upload has been prepared as a full merge from Debian,
however I kept the other series' diff as small as possible by doing a
plain "upstream update". Notably, I didn't pick up the Debian changes
renaming Kiev to Kyiv in the older releases.
You'll note that the ICU data has only been updated 'til 2022b. That's
because they haven't picked up 2022c yet, and probably won't since that
last release is more of a bugfix release, with no data changes.
** Also affects: tzdata (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Also affects: tzdata (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: tzdata (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: tzdata (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: tzdata (Ubuntu Focal)
Status: New => Confirmed
** Changed in: tzdata (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Confirmed
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Confirmed
Status in tzdata source package in Focal:
Confirmed
Status in tzdata source package in Jammy:
Confirmed
Status in tzdata source package in Kinetic:
Confirmed
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
** Summary changed:
- Availability of tzdata 2022c for Ubuntu 20.04
+ [FFe] tzdata 2022c update
** Description changed:
- tzdata 2022b and 2022c were just released that includes some timezone
- changes for Chile. According to the tzdata lib listed for Ubuntu 20.04,
- the latest package is 2022a. Any idea when 2022b or 2022c will be
- available? Chile made a change to the start of their daylight savings
- and pushed it from Sept 4th to the 11th, so we really need our servers
- updated before the 4th.
+ 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/$timezone_that_changed' (this needs to be greped for in
+ /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
+ compared to the same output after the updated package got installed. If
+ those are different the verification is considered done.
+
+ [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(TimeZone.createTimeZone("America/Santiago"))
+ always_before = datetime(2022, 9, 1)
+ now_before = datetime(2022, 9, 8)
+ always_after = datetime(2022, 9, 12)
+ assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
+ assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
+
+ 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]
+ tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Confirmed
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/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[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(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
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]
tzdata 2022b and 2022c were
