From: Dipl. I. S. G. B. <se...@us...> - 2024-11-08 18:30:04
|
It is not THE CLOCK PATTERN "%Z", but the TZ-NAME in many timezone-definitions in library/tzdata got "%z" in 8.6.15, instead of for instance "±0100"... As mentioned in the ticket, the regression was [9275edd424971958] [2] and how one can see, that affects many tzdata files. To be more clear, all scan- and format-attempts could be affected, where current TZ (and the timestamp) would match or result to such zone blocks, for instance: % clock format [clock seconds] -timezone :Pacific/Norfolk; Sat Nov 09 06:17:17 %Z 2024 % clock format [clock seconds] -timezone :Etc/GMT-1; Fri Nov 08 20:17:18 %Z 2024 Regards, Serg. 08.11.2024 18:00, Harald Oehlmann wrote: > Sergey has reported the following issue: > > https://core.tcl-lang.org/tcl/info/2c237beffbace823 [1] > Sergey sees this as very critical and as a reason to quickly re-release 8.6.16. > The clock pattern "%z" is giving wrong answers which is felt as critical. Links: ------ [1] https://core.tcl-lang.org/tcl/info/2c237beffbace823 [2] https://core.tcl-lang.org/tcl/info/9275edd424971958 |