Brooks Harris via tz wrote in <6b9dbf10-cd1e-4b45-94aa-e4935de035d8@edlmax.com>: |On 2026-10-16 07:54 AM, Michelle Bastian wrote: |> There was a recorded message from the ITU-T saying they are in full \ |> support. The IERS recorded message also gave their support, and their \ |> commitment to keep providing UT1. |> |> Re the one hour difference being supposedly non-controversial, as \ |> Tim pointed out. This seems to be the response to those who raised \ |> questions about the broader public,…
On 2026-10-16 07:54 AM, Michelle Bastian wrote: > There was a recorded message from the ITU-T saying they are in full support. The IERS recorded message also gave their support, and their commitment to keep providing UT1. > > Re the one hour difference being supposedly non-controversial, as Tim pointed out. This seems to be the response to those who raised questions about the broader public, and whether standards bodies had the right to make civil time discontinuous with Earth rotation in this…
On 2026-10-15 14:07, Paul Eggert wrote: > I expect that he'll modify the file to either drop the expiry date, > change it to some date far in the future. In case it helps with that choice: we tested both options, and also letting the file lapse, against nine consumers that read leap-seconds.list (or Leap_Second.dat) directly. That is seven programs: chrony in two versions, and astropy once per file format. Each test file was the current IERS file with only the expiry changed or removed: in…
There was a recorded message from the ITU-T saying they are in full support. The IERS recorded message also gave their support, and their commitment to keep providing UT1. Re the one hour difference being supposedly non-controversial, as Tim pointed out. This seems to be the response to those who raised questions about the broader public, and whether standards bodies had the right to make civil time discontinuous with Earth rotation in this way. It does make me think of this claim from Pavel…
On Thu, 15 Oct 2026 at 13:36, Tim Parenti wrote: > The motion was carried unanimously. > CSRD news release here… https://www.csrd.bc.ca/m/newsflash/home/detail/2486 Patch to commentary attached. -- Tim Parenti
On 2026-10-15 09:24 PM, Paul Eggert wrote: > On 2026-10-15 17:51, Brooks Harris wrote: >> The ITU-R has to revise Recommendation TF 460 too. > > Yes, although as I understand it leap seconds are dead and the ITU-R's > revision process will merely dot the Is and cross the Ts. The 2023 ITU > World Radiocommunication Conference passed Resolution 655 > (REV.WRC-23), which agreed with the General Conference on Weights and > Measures (CGPM) on this topic. These two groups work have a formal >…
On 2026-10-15 17:51, Brooks Harris wrote: > The ITU-R has to revise Recommendation TF 460 too. Yes, although as I understand it leap seconds are dead and the ITU-R's revision process will merely dot the Is and cross the Ts. The 2023 ITU World Radiocommunication Conference passed Resolution 655 (REV.WRC-23), which agreed with the General Conference on Weights and Measures (CGPM) on this topic. These two groups work have a formal memorandum of understanding about working together[2], and ITU-R…
I advise not to getting to far ahead. The ITU-R has to revise Recommendation TF 460 too. The WP 7A working group is meeting  sometime between 2027-02-22 and 2027-03-04: ITU-R Events https://www.itu.int/en/events/Pages/Calendar-Events.aspx?sector=ITU-R On 2026-10-15 08:24 PM, Paul Eggert via tz wrote: > On 2026-10-15 14:07, Paul Eggert via tz wrote: >> I've written the director of the IERS's Earth Orientation Center >> about this, as he maintains leap-seconds.list. > > On further thought,…
> On Oct 15, 2026, at 2:57 PM, Bradley White wrote: > > On Thu, Oct 15, 2026 at 5:04 PM Guy Harris via tz > wrote: >> The one thing for which the leap second data could be useful is converting "seconds that have elapsed since the POSIX epoch, yeah, even counting leap seconds" time stamps for values in the past to UTC. > > See time2posix(), which converts a "right" time_t (seconds that have elapsed since the POSIX epoch, yeah, even counting leap seconds) to a "posix" time_t, which can then…
On 2026-10-15 14:07, Paul Eggert via tz wrote: > I've written the director of the IERS's Earth Orientation Center about this, as he maintains leap-seconds.list. On further thought, now that leap seconds have been discontinued we should change zic to not put leap second table expiry info into the TZif output file, as per Internet RFC 9636 §3.2. I wrote the IERS EOC director about this too. We can also shrink TZ_MAX_LEAPS a bit, now that the number of leap seconds is capped. We should update the…
On Thu, Oct 15, 2026 at 5:04 PM Guy Harris via tz wrote: > The one thing for which the leap second data could be useful is converting > "seconds that have elapsed since the POSIX epoch, yeah, even counting leap > seconds" time stamps for values in the past to UTC. See time2posix(), which converts a "right" time_t (seconds that have elapsed since the POSIX epoch, yeah, even counting leap seconds) to a "posix" time_t, which can then easily be converted to UTC.
On 2026-10-15 13:53, Tim Parenti via tz wrote: > Since we began downstreaming that file from IERS since 2024, the question > is more for them. I've written the director of the IERS's Earth Orientation Center about this, as he maintains leap-seconds.list. I expect that he'll modify the file to either drop the expiry date, change it to some date far in the future.
On Oct 15, 2026, at 1:53 PM, Tim Parenti via tz wrote: > In the much longer-term, since you can never just throw away the 27 leap seconds that have happened, the question becomes just about as philosophical as the decision itself. Not many bothered picking 'right' over 'posix' anyway, and once we can essentially fix right = posix + 27, newer systems won't necessarily need to care that leap seconds were ever a thing. The one thing for which the leap second data could be useful is converting…
On Thu, 15 Oct 2026 at 14:56, Garrett Wollman via tz wrote: > A question then becomes, what happens to the leapseconds file and the > expiration dates within? Since we began downstreaming that file from IERS since 2024, the question is more for them. Presumably not much changes in the short-term, as the "continuous UTC" official takes effect on 20 May 2027, but eventually some far-future expiration date is likely chosen and/or possibly the format of the file changes. In the much longer-term,…
On 2026-10-15 02:55 PM, Garrett Wollman via tz wrote: > I have just seen it reported that the CGPM has officially moved to end > leap seconds. > > A question then becomes, what happens to the leapseconds file and the > expiration dates within? Presumably it will no longer be updated, but > there are a number of tools (like ntpd) that currently make use of the > file and complain when it is out of date. > > https://www.doi.org/10.59161/CGPM2026RES5E > > -GAWollman > How an accelerating Earth led…
I have just seen it reported that the CGPM has officially moved to end leap seconds. A question then becomes, what happens to the leapseconds file and the expiration dates within? Presumably it will no longer be updated, but there are a number of tools (like ntpd) that currently make use of the file and complain when it is out of date. https://www.doi.org/10.59161/CGPM2026RES5E -GAWollman
On Tue, 22 Sept 2026 at 16:17, Tim Parenti wrote: > Routley moved a superseding resolution to adopt UTC−6 (Mountain Daylight > Time) in alignment with the Regional District of East Kootenay; to direct > staff to work with school districts, the surrounding rural areas, and the > provincial Ministry of Transportation and Transit to work on various safety > and streetlighting concerns; and to commit to reviewing time observance in > October 2027, "including ongoing dialogue with [RDEK], community…
On 2026-10-14 13:12, Paul Eggert wrote: > None of these names need to be user-visible, so I would say that's more > of a bug in Grafana than in TZDB. And it's not the only bug: Grafana > doesn't list either Asia/Kolkata or America/Coyhaique in the file you > mentioned. So I suggest send them bug reports about the issue: they > should add Asia/Kolkata and America/Coyhaique, and remove the three > Russian spellings for Ukrainian names. I created a Grafana PR along those lines, here:…
Apple pushed an over-the-air time zone update across my Apple devices prompted by a notification saying there is Updated Time Zone information. Winnipeg's time zone has now been updated to UTC-5 year-round. Good to know that this has been pushed at least to Canadian users!
On 2026-10-14 01:19, Khikmet Kerimov wrote: > The remaining problem is downstream: users such as Grafana list > 'Europe/Zaporozhye' in their timezone pickers None of these names need to be user-visible, so I would say that's more of a bug in Grafana than in TZDB. And it's not the only bug: Grafana doesn't list either Asia/Kolkata or America/Coyhaique in the file you mentioned. So I suggest send them bug reports about the issue: they should add Asia/Kolkata and America/Coyhaique, and remove the…
Thanks to Paul for the "Europe/Uzhgorod, Europe/Zaporozhye now just links" removal of the dubious backzone entries - that cleanup makes sense. This v2 supersedes my 12 October proposal: it is rebased onto main, including that removal, and the '#=' form is dropped as unneeded now that the backzone Zones are gone; the new names are plain links to Kyiv time, next to the existing old-spelling lines. The remaining problem is downstream: users such as Grafana list 'Europe/Zaporozhye' in their…
On 2026-10-11 23:29, Khikmet Kerimov via tz wrote: > This patch adds compatibility links `Europe/Uzhhorod` and > `Europe/Zaporizhzhia` for the existing backzone identifiers Thanks for reporting the problem. Those two names are based on bad data and are present in 'backzone' only for TZDB historical reasons. As there's significant opportunity for confusion due to their presence in 'backzone', it's better to remove the wrong 'backzone' entries than to magnify the effects of their bad data.…
On 2026-10-12 00:29, Khikmet Kerimov via tz wrote: > This patch adds compatibility links `Europe/Uzhhorod` and `Europe/Zaporizhzhia` > for the existing backzone identifiers `Europe/Uzhgorod` and `Europe/Zaporozhye`, > using the `#=` form already used for `Pacific/Ponape` and `Pacific/Truk`. > > The new spellings follow the official Ukrainian national romanization approved > by Resolution No. 55 of the Cabinet of Ministers of Ukraine (27 January 2010) > and the MFA of Ukraine #CorrectUA campaign…
On Tue, 13 Oct 2026 at 13:39, Aoun Khan via tz wrote: > Ontario is set to move parts of the province’s northwest region to > permanent daylight time in order to align with Manitoba, Indigenous Affairs > Minister Greg Rickford told The Canadian Press. > > Rickford says the province intends to make a regulatory change in the Time > Act on Nov. 1 to allow regions west of the 90th meridian to align with > Manitoba. On Tue, 13 Oct 2026 at 13:59, Chris Walton via tz wrote: > The provincial government…
>Microsoft's announcement does not mention other versions of MS-Windows that are still supported, including Windows 11 (21H2, 22H2, 26H1, 26H2) https://support.microsoft.com/en-us/servicing/os/windows-11/2026/10/kb5127648-windows-11-24h2-25h2-26h2-security-update Above indicates the new timezone will be available for 26H2 at least: >[Date and Time] This update introduces the new (UTC-05:00) Manitoba time zone to support Manitoba’s November 1, 2026, time zone change.…
> and, if Bionic's code is based on the tzdb code, the tzdb code It is: https://cs.android.com/android/platform/superproject/main/+/main:bionic/libc/tzcode/;drc=7dbddd38ddddaab7a61b5fb943510e21c6aa8c61 On Thu, 8 Oct 2026 at 21:05, Guy Harris via tz wrote: > "We didn't count servers, Macs or laptops, which would push the number > higher." > > Not quite sure what they meant by "Macs or laptops", given that 1) the > laptop on which I'm typing this *is* a Mac and 2) most laptops are probably >…
The provincial government has issued a written news release: https://news.ontario.ca/en/release/1008130/ontario-moving-to-permanent-daylight-saving-time-in-parts-of-northwestern-ontario -chris On Tue, Oct 13, 2026 at 1:39 PM Aoun Khan via tz wrote: > > https://www.cp24.com/news/canada/2026/10/13/ontario-to-move-northwest-regions-to-permanent-daylight-time/ > > https://www.ctvnews.ca/northern-ontario/article/ontario-to-move-northwest-regions-to-permanent-daylight-time/ > > Ontario is set to move…