|
1 | 1 | News for the tz database |
2 | 2 |
|
| 3 | +Release 2022f - 2022-10-28 18:04:57 -0700 |
| 4 | + |
| 5 | + Briefly: |
| 6 | + Mexico will no longer observe DST except near the US border. |
| 7 | + Chihuahua moves to year-round -06 on 2022-10-30. |
| 8 | + Fiji no longer observes DST. |
| 9 | + Move links to 'backward'. |
| 10 | + In vanguard form, GMT is now a Zone and Etc/GMT a link. |
| 11 | + zic now supports links to links, and vanguard form uses this. |
| 12 | + Simplify four Ontario zones. |
| 13 | + Fix a Y2438 bug when reading TZif data. |
| 14 | + Enable 64-bit time_t on 32-bit glibc platforms. |
| 15 | + Omit large-file support when no longer needed. |
| 16 | + In C code, use some C23 features if available. |
| 17 | + Remove no-longer-needed workaround for Qt bug 53071. |
| 18 | + |
| 19 | + Changes to future timestamps. |
| 20 | + |
| 21 | + Mexico will no longer observe DST after 2022, except for areas |
| 22 | + near the US border that continue to observe US DST rules. |
| 23 | + On 2022-10-30 at 02:00 the Mexican state of Chihuahua moves |
| 24 | + from -07 (-06 with DST) to year-round -06, thus not changing |
| 25 | + its clocks that day. The new law states that Chihuahua |
| 26 | + near the US border no longer observes US DST. |
| 27 | + |
| 28 | + Fiji will not observe DST in 2022/3. (Thanks to Shalvin Narayan.) |
| 29 | + For now, assume DST is suspended indefinitely. |
| 30 | + |
| 31 | + Changes to data |
| 32 | + |
| 33 | + Move links to 'backward' to ease and simplify link maintenance. |
| 34 | + This affects generated data only if you use 'make BACKWARD='. |
| 35 | + |
| 36 | + GMT is now a Zone and Etc/GMT a link instead of vice versa, |
| 37 | + as GMT is needed for leap second support whereas Etc/GMT is not. |
| 38 | + However, this change exposes a bug in TZUpdater 2.3.2 so it is |
| 39 | + present only in vanguard form for now. |
| 40 | + |
| 41 | + Vanguard form now uses links to links, as zic now supports this. |
| 42 | + |
| 43 | + Changes to past timestamps |
| 44 | + |
| 45 | + Simplify four Ontario zones, as most of the post-1970 differences |
| 46 | + seem to have been imaginary. (Problem reported by Chris Walton.) |
| 47 | + Move America/Nipigon, America/Rainy_River, and America/Thunder_Bay |
| 48 | + to 'backzone'; backward-compatibility links still work, albeit |
| 49 | + with some different timestamps before November 2005. |
| 50 | + |
| 51 | + Changes to code |
| 52 | + |
| 53 | + zic now supports links to links regardless of input line order. |
| 54 | + For example, if Australia/Sydney is a Zone, the lines |
| 55 | + Link Australia/Canberra Australia/ACT |
| 56 | + Link Australia/Sydney Australia/Canberra |
| 57 | + now work correctly, even though the shell commands |
| 58 | + ln Australia/Canberra Australia/ACT |
| 59 | + ln Australia/Sydney Australia/Canberra |
| 60 | + would fail because the first command attempts to use a link |
| 61 | + Australia/Canberra that does not exist until after the second |
| 62 | + command is executed. Previously, zic had unspecified behavior if |
| 63 | + a Link line's target was another link, and zic often misbehaved if |
| 64 | + a Link line's target was a later Link line. |
| 65 | + |
| 66 | + Fix line number in zic's diagnostic for a link to a link. |
| 67 | + |
| 68 | + Fix a bug that caused localtime to mishandle timestamps starting |
| 69 | + in the year 2438 when reading data generated by 'zic -b fat' when |
| 70 | + distant-future DST transitions occur at times given in standard |
| 71 | + time or in UT, not the usual case of local time. This occurs when |
| 72 | + the corresponding .zi Rule lines specify DST transitions with TO |
| 73 | + columns of 'max' and AT columns that end in 's' or 'u'. The |
| 74 | + number 2438 comes from the 32-bit limit in the year 2038, plus the |
| 75 | + 400-year Gregorian cycle. (Problem reported by Bradley White.) |
| 76 | + |
| 77 | + On glibc 2.34 and later, which optionally supports 64-bit time_t |
| 78 | + on platforms like x86 where time_t was traditionally 32 bits, |
| 79 | + default time_t to 64 instead of 32 bits. This lets functions like |
| 80 | + localtime support timestamps after the year 2038, and fixes |
| 81 | + year-2038 problems in zic when accessing files dated after 2038. |
| 82 | + To continue to limit time_t to 32 bits on these platforms, use |
| 83 | + "make CFLAGS='-D_TIME_BITS=32'". |
| 84 | + |
| 85 | + In C code, do not enable large-file support on platforms like AIX |
| 86 | + and macOS that no longer need it now that tzcode does not use |
| 87 | + off_t or related functions like 'stat'. Large-file support is |
| 88 | + still enabled by default on GNU/Linux, as it is needed for 64-bit |
| 89 | + time_t support. |
| 90 | + |
| 91 | + In C code, prefer C23 keywords to pre-C23 macros for alignof, |
| 92 | + bool, false, and true. Also, use the following C23 features if |
| 93 | + available: __has_include, unreachable. |
| 94 | + |
| 95 | + zic no longer works around Qt bug 53071, as the relevant Qt |
| 96 | + releases have been out of support since 2019. This change affects |
| 97 | + only fat TZif files, as thin files never had the workaround. |
| 98 | + |
| 99 | + zdump no longer modifies the environ vector when compiled on |
| 100 | + platforms lacking tm_zone or when compiled with -DUSE_LTZ=0. |
| 101 | + This avoid undefined behavior on POSIX platforms. |
| 102 | + |
| 103 | + |
3 | 104 | Release 2022e - 2022-10-11 11:13:02 -0700 |
4 | 105 |
|
5 | 106 | Briefly: |
|
0 commit comments