[Bug 10181] New: tzset mishandles version 3 tzdb format
bugzilla at busybox.net
bugzilla at busybox.net
Mon Aug 7 16:26:16 UTC 2017
https://bugs.busybox.net/show_bug.cgi?id=10181
Bug ID: 10181
Summary: tzset mishandles version 3 tzdb format
Product: uClibc
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at uclibc.org
Reporter: eggert at cs.ucla.edu
CC: uclibc-cvs at uclibc.org
Target Milestone: ---
Created attachment 7171
--> https://bugs.busybox.net/attachment.cgi?id=7171&action=edit
untested patch to support tzdb version 3 files
This bug report responds to the following thread on the tz mailing list:
http://mm.icann.org/pipermail/tz/2017-August/025205.html
The issue is that tzdb version 3 format extends version 2 slightly, in that the
POSIX-style TZ strings at the binary-file's end are allowed to have start times
that range from -167:59:59 to 167:59:59, instead of the POSIX-specified
00:00:00 through 24:59:59. This is needed to support the predicted future time
zone settings for Israel and Western Greenland, which have the following TZ
string values in current tzdb:
Asia/Jerusalem 'IST-2IDT,M3.4.4/26,M10.5.0'
America/Godthab '<-03>3<-02>,M3.5.0/-2,M10.5.0/-1'
Although POSIX currently does not require support for these strings, they are
widely supported by other C libraries including glibc, and it should be easy to
fix uClibc-ng to support them too. Proposed patch attached. I don't use uClibc
so I have not tested it.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the uClibc-cvs
mailing list