Sorry, I made a mistake and the actual diff result is,
| zone |
local time |
by
2020d utc time |
by
2021a utc time |
|
| America/Adak |
2022-11-01 00:00:00 |
2022-11-01 09:00:00 |
2022-11-01 10:00:00 |
|
| America/Anchorage |
2022-11-01 00:00:00 |
2022-11-01 08:00:00 |
2022-11-01 09:00:00 |
|
| America/Asuncion |
2022-10-01 00:00:00 |
2022-10-01 04:00:00 |
2022-10-01 03:00:00 |
|
| America/Atka |
2022-11-01 00:00:00 |
2022-11-01 09:00:00 |
2022-11-01 10:00:00 |
but the problem still exists. I have put my analysis tool and its code in the docker image, "damon0708/zic:v0.3". The tool is writen in golang and easy to be used.
# ./main -h
-l string
local time need to transfer (default "2022-11-01 00:00:00")
-path string
used to parse timezone (default "/usr/share/zoneinfo")
-tz string
the timezone you want transfer (default "America/Adak")
After making the zoneinfo
in path "/app/zoneinfo",
# ./main -l "2022-11-01 00:00:00" -path
"/usr/share/zoneinfo" -tz "America/Adak"
UTC: 2022-11-01 09:00:00 +0000 UTC
# ./main -l "2022-11-01 00:00:00"
-path "/app/zoneinfo" -tz "America/Adak"
UTC: 2022-11-01 10:00:00 +0000 UTC
The tool uses the golang standard
library "time", which can be specified
the zoneinfo path by the env "ZONEINFO". So I don't think it is the problem of the tool.
发件人: Paul Eggert <eggert@cs.ucla.edu>
发送时间: 2021年3月4日 17:13
收件人: 汪蒙蒙（木之） <wangmm@tuya.com>
抄送: Time zone mailing list <tz@iana.org>
主题: Re: 回复: [tz] zoneinfo generating issues
On 3/3/21 11:03 PM, 汪蒙蒙（木之） wrote:
> the check showed no diff in America/Adak America/Anchorage
> America/Asuncion America/Atka
In that case I don't see how the tzdb distribution (either code or data)
can be the problem here. If I understand things correctly, you say it's
producing TZif files like America/Adak that are identical to those of
previous releases, but that your analysis tool is behaves differently on
those two identical TZif files. I expect you'll have to look into the
problem on your end.