October 2021 - tz - lists.iana.org

(no subject)
by Cool Gab19 Nov. 8, 2024

Nov. 8, 2024

can you add Philippine Daylight Time on your Database I think it was missing from the list of the time zones please reply immediately if solved thanks...

4 8

Re: [tz] Morocco : Ramdan Time Change 2021
by Paul Eggert March 15, 2023

March 15, 2023

On 3/19/21 3:15 AM, Semlali Naoufal wrote: > At the moment, we have no official government announcement to this effect. But, logically, the change to the GMT schedule should be made on the night of April 10-11, 2021 (last weekend before Ramadan). Yes, that's been the tzdb prediction too, ever since tzdb version 2018h (2018-12-23). For the record, here are tzdb's current predictions Morocco transitions during the next five years. Sun Apr 11 01:59:59 2021 UT = Sun Apr 11 02:59:59 2021 +01 Sun Apr 11 02:00:00 2021 UT = Sun Apr 11 02:00:00 2021 +00 Sun May 16 01:59:59 2021 UT = Sun May 16 01:59:59 2021 +00 Sun May 16 02:00:00 2021 UT = Sun May 16 03:00:00 2021 +01 Sun Mar 27 01:59:59 2022 UT = Sun Mar 27 02:59:59 2022 +01 Sun Mar 27 02:00:00 2022 UT = Sun Mar 27 02:00:00 2022 +00 Sun May 8 01:59:59 2022 UT = Sun May 8 01:59:59 2022 +00 Sun May 8 02:00:00 2022 UT = Sun May 8 03:00:00 2022 +01 Sun Mar 19 01:59:59 2023 UT = Sun Mar 19 02:59:59 2023 +01 Sun Mar 19 02:00:00 2023 UT = Sun Mar 19 02:00:00 2023 +00 Sun Apr 30 01:59:59 2023 UT = Sun Apr 30 01:59:59 2023 +00 Sun Apr 30 02:00:00 2023 UT = Sun Apr 30 03:00:00 2023 +01 Sun Mar 10 01:59:59 2024 UT = Sun Mar 10 02:59:59 2024 +01 Sun Mar 10 02:00:00 2024 UT = Sun Mar 10 02:00:00 2024 +00 Sun Apr 14 01:59:59 2024 UT = Sun Apr 14 01:59:59 2024 +00 Sun Apr 14 02:00:00 2024 UT = Sun Apr 14 03:00:00 2024 +01 Sun Feb 23 01:59:59 2025 UT = Sun Feb 23 02:59:59 2025 +01 Sun Feb 23 02:00:00 2025 UT = Sun Feb 23 02:00:00 2025 +00 Sun Apr 6 01:59:59 2025 UT = Sun Apr 6 01:59:59 2025 +00 Sun Apr 6 02:00:00 2025 UT = Sun Apr 6 03:00:00 2025 +01 Sun Feb 15 01:59:59 2026 UT = Sun Feb 15 02:59:59 2026 +01 Sun Feb 15 02:00:00 2026 UT = Sun Feb 15 02:00:00 2026 +00 Sun Mar 22 01:59:59 2026 UT = Sun Mar 22 01:59:59 2026 +00 Sun Mar 22 02:00:00 2026 UT = Sun Mar 22 03:00:00 2026 +01 Sun Feb 7 01:59:59 2027 UT = Sun Feb 7 02:59:59 2027 +01 Sun Feb 7 02:00:00 2027 UT = Sun Feb 7 02:00:00 2027 +00 Sun Mar 14 01:59:59 2027 UT = Sun Mar 14 01:59:59 2027 +00 Sun Mar 14 02:00:00 2027 UT = Sun Mar 14 03:00:00 2027 +01 Sun Jan 23 01:59:59 2028 UT = Sun Jan 23 02:59:59 2028 +01 Sun Jan 23 02:00:00 2028 UT = Sun Jan 23 02:00:00 2028 +00 Sun Mar 5 01:59:59 2028 UT = Sun Mar 5 01:59:59 2028 +00 Sun Mar 5 02:00:00 2028 UT = Sun Mar 5 03:00:00 2028 +01 Sun Jan 14 01:59:59 2029 UT = Sun Jan 14 02:59:59 2029 +01 Sun Jan 14 02:00:00 2029 UT = Sun Jan 14 02:00:00 2029 +00 Sun Feb 18 01:59:59 2029 UT = Sun Feb 18 01:59:59 2029 +00 Sun Feb 18 02:00:00 2029 UT = Sun Feb 18 03:00:00 2029 +01 Sun Dec 30 01:59:59 2029 UT = Sun Dec 30 02:59:59 2029 +01 Sun Dec 30 02:00:00 2029 UT = Sun Dec 30 02:00:00 2029 +00 Sun Feb 10 01:59:59 2030 UT = Sun Feb 10 01:59:59 2030 +00 Sun Feb 10 02:00:00 2030 UT = Sun Feb 10 03:00:00 2030 +01 Sun Dec 22 01:59:59 2030 UT = Sun Dec 22 02:59:59 2030 +01 Sun Dec 22 02:00:00 2030 UT = Sun Dec 22 02:00:00 2030 +00

3 9

United States Senate reintroduced Sunshine Protection Act, enabling Permanent DST
by Phake Nick Nov. 14, 2022

Nov. 14, 2022

I don't quite understand the legal text of the bill itself [2], but according to my reading, it seems like the bill will end DST across the entire US by shifting the standard time forward an hour, except in states/territories/area that currently doesn't enact DST, which they can choose to follow the new standard time or old standard time? 1: https://www.rubio.senate.gov/public/index.cfm/2021/3/rubio-colleagues-reint… 2: https://www.rubio.senate.gov/public/_cache/files/d34c77c0-acea-4074-bc57-14…

18 26

Re: [tz] iana build failures on Windows
by Paul Eggert Nov. 2, 2022

Nov. 2, 2022

On 4/19/21 7:09 AM, Manuela Friedrich wrote: > I had to include signal.h in zic.c to prevent the following error: > > zic.c(610): error C2061: syntax error: identifier 'got_signal' This is a portability bug recently introduced to zic.c. I installed the first attached patch to fix it. > The I needed to resolved error > > zic.obj : error LNK2019: unresolved external symbol tz_time referenced in function random_dirent This appears to be another recent portability bug. It's related to a portability problem you reported on MS-Windows in response to which in 2018d I committed a patch that introduced RESERVE_STD_EXT_IDS: https://github.com/eggert/tz/commit/24b45243c5210b4196987fdd06e6c288c358a268 When I recently added the randomish filename code to the development version, I neglected to deal with RESERVE_STD_EXT_IDS. The second attached patch should fix this issue. Please give the two patches a try, as I don't use MS-Windows and can't easily test these patches on that platform. > a test run of zdump -v produced way more output than in the last release, the Linux output seems to have become longer too, but maybe this is still under development. That change is intentional, and was caused by this: https://github.com/eggert/tz/commit/ac07b446a3afaa4cb1ae11a91785a201c91f6351 along with some neighboring commits. Thanks for reporting the problems, and I hope the current development version of tzdb addresses the issues you mentioned.

5 23

Re: [tz] Wrong name of timezone
by Pierpaolo Bernardi April 11, 2022

April 11, 2022

Il giorno 25 ottobre 2021, alle ore 16:58, Igor Melnyk via tz <tz(a)iana.org> ha scritto: >But Ukraine has the Ukrainian language and Kiev is in russian language. The correct name of the capital city of Ukraine is Kyiv. Kiev is English language, as every other name in the db, not russian. It is only a coincidence that the English name is more similar to russian than to Ukrainian.

6 5

Re: [tz] Change Request: Europe/Kiev to Europe/Kyiv
by John Hawkinson March 18, 2022

March 18, 2022

I do not think we have handled this well; we have not given Victor Perov a good answer. Indeed, to some extent we've made it a "runaround." We can do better. We should take the time to write up a good lengthy explanation of the issues ("boilerplate"), because this a really important issue of concern to many people in the world and the project has indeed thought about it pretty carefully. Dismissing the inquiries because they are repetitive makes it seem like we haven't, and that unnecessarily upsets peopl. Victor Perev: I don't have time for a full write-up right now, but please consult the archives of the tz list (http://mm.icann.org/pipermail/tz/ or perhaps https://www.google.com/search?q=site%3Amm.icann.org%2Fpipermail%2Ftz%2F+kyiv which returns 203 results). The tz project is very conservative in its judgment for when the predominant English spelling of a city has changed, and so far the project has judged that Kiev is still preferred. We discussed it when major English newspapers and style guides changed from Kiev to Kyiv last year (prompted by the US presidential impeachment, which lead to a lot of discussion about Kyiv in America), and we will probably continue to discuss it as time goes on. But we've thought about it and discussed it a lot. The answers you got don't explain that, and that means we have not done a good a job as we should have. Sorry about that. In particular, I think Brian Inglis's answer was actually incorrect in a way that really matters ("Kiev is the correct English spelling"). There are multiple correct English spellings. It used to be that Kiev was the only one, but Kyiv is gaining popularity more and more. Paul Eggert <eggert(a)cs.ucla.edu> wrote on Sat, 15 Aug 2020 at 18:19:08 EDT in <cefc7f01-a3e9-f2a4-9ab9-5288147f994a(a)cs.ucla.edu>: > Thanks for bringing that to the mailing list (if I could shut off GitHub > pull requests I would). Although you cannot do so, we can handle them a little bit better. Please see https://docs.github.com/en/github/building-a-strong-community/creating-a-pu… You can create a template that explains to a would-be pull request submitter than pull requests will be closed and the project uses the mailing list for development discussions. ("I understand that the tz project does not use pull requests on github, and that if I enter a pull request here, it will be closed and I will be directed to send email to tz(a)iana.org.") For the particular case of regular, recurring issues, it may be worth while to keep one of #15, #26, and #27 open and mark the others as a duplicate of it, so that it is easier for newcomers to understand that this issue has been carefully considered and is not a simple oversight. https://github.com/eggert/tz/pulls?q=kiev Also, not to pick on Brian (again), but if the project policy is not to use github pull requests, it's not great to respond to pull requests on their substance, because it bifurcates the discussion and makes it seem like we actually do use pull requests ("except when we don't"). So what seems like a helpful thing may not be. -- jhawk(a)alum.mit.edu John Hawkinson

10 13

Pre-1970 data
by Stephen Colebourne Nov. 12, 2021

Nov. 12, 2021

How can this project successfully handle pre-1970 data? Why have I focussed so much on IDs and their value to tzdb? Intro ------- In previous threads I've focussed on IDs, and laid out different ways to describe the groups of IDs we have. For now, lets focus solely on the two main groups - region IDs, which represent abstract regions where clocks have been the same since 1970 - non-region IDs, which represent locations where tzdb has, at some point, added an ID The key observation is that the segregation between these two groups of IDs *did not exist* until around 2014. It was only in 2018 that the ISO country rule was removed. It has only been since 2014 or so that IDs have been merged. What tzdb previously offered was a set of IDs, based on a simple rule - "ID as needed for post-1970 data, with at least one per ISO country". Full history was available for each of these (whether accurate or not). What has happened since is a split, where no split previously existed. A split which favours some locations over others. The recent mailing list debates merely represent the cumulation of this favouritism. The irony is that the merges are being done in the name of equity and fairness, when the outcome has actually been the exact opposite - picking favourites, and denigrating everywhere else. That the approach to picking favourites is according to a standardised largest city rule isn't really that relevant here - it is the outcome that is unfair, not the process. If region IDs were of different appearance (eg. numeric or textually different) then the issues would not have arisen. The mistake was taking a fully functional and fully integral set of IDs, and bifurcating it into two groups. The split was actually a huge change in the policy of tzdb, which has been added drip by drip, rather than something that was ever fully appreciated up front. FWIW, it is clear to me that there is an aspect of imposing a US-centric timezone system on other parts of the world. The recent tzdb approach of focussing entirely on timezone regions makes perfect sense for the US, where region boundaries do not follow state lines, and ordinary members of the public need to be aware of whether they are in US/Mountain or US/Central. This simply isn't the timezone model in many other parts of the world. In places like Europe and Asia, the timezone is driven primarily by the country you live in - an ordinary member of the public in Iceland is never going to associate with some abstract timezone region stretching down the Atlantic that is not named, not legally defined and is little more than a random outcome based on tzdb's choice of 1970. Even in somewhere like Norway, an ordinary member of the public will understand that although they follow CET, their timezone is actually driven by their Government in Oslo. The brilliance of the original rule - "ID as needed for post-1970 data, with at least one per ISO country" - was that it seamlessly handled *both* models of timezone in one unified set of IDs. Removal of the ISO country part has completely destabilised that balance. As a constraint to this thread, tzdb really needs to offer one standard view of data, not command line flags that allow different views. If downstream projects end up with different views of the data, it makes tzdb a much less reliable source. (tzdb can be packaged in different ways on the same machine, for example it is undesirable for Postgres' internal tzdb and the OS tzdb to diverge for the same version). Given this, what needs to be nailed down is what is the default data set that tzdb publishes - there isn't really much point in talking about compile time flags, or that the contents of backzone could be used by someone. Lets look at seven options for pre-1970 data: Pre-1970 data for regions only ----------------------------------------- 1) Pre-1970 data for regions only - Despite looking identical to other IDs, region IDs are treated as special/favoured - Pre-1970 data for non-region IDs is of no importance whatsoever, thus most get pre-1970 data from another country/continent - The split between region and non-region locations is fully completed - the US-centric timezone model is dominant - An end user in Iceland is supposed to use Africa/Abidjan, Europe/Reykjavik is treated as a historical mistake of tzdb kept around only for backwards compatibility Pre-1970 data for most IDs ------------------------------------ 2) Pre-1970 data for each ID meeting the rule "ID as needed for post-1970 data, with at least one per ISO country" - The split between region and non-region locations is healed - High quality data from places like Iceland and Norway is retained, but low quality data from elsewhere is restored - The pre-1970 data is simply viewed as the best available data for the each location which can be improved over time - Most end-users in Iceland would expect tzdb to provide pre-1970 data from Iceland, not the Ivory Coast 3) Pre-1970 data for for all IDs that currently exist except true aliases - This is very similar to #2, but would include something like Montreal which was effectively mistakenly added to tzdb - This doesn't seem as desirable as #2 4) Pre-1970 data for any ID where the pre-1970 data is high quality - Subjective on quality, which doesn't seem like a great idea - It does avoid bringing bad quality data back into the main tzdb distribution - On balance, #2 has fewer places for debate to arise 5) Pre-1970 data for all IDs that currently exist except true aliases, plus a *new* set of IDs representing regions - As per #2, but adding IDs like "Region/12345" or "Region/Berlin" - Regions should contain post-1970 data only, as the region is by definition only meaningful post-1970 - It is not entirely clear what this solves over just going with #2 - This option is connected to Russ' proposals [1], although he suggests a bigger split between timekeeping data and ID naming - Perhaps it makes sense if the new region IDs were internal and not normally seen by end users? Remove pre-1970 data from general use ------------------------------------------------------- 6) No pre-1970 data whatsoever, all IDs are post-1970 only - Project policy is that tzdb is focussed on post-1970 data only - Paul repeatedly tells us that pre-1970 data is unreliable, and people shouldn't use it - Pre-1970 data would not be deleted, but would not be available in most downstreams - The split between region and non-region locations is effectively healed - End users lose access to pre-1970 data, which is particularly notable in some locations where that data is reliable, eg London - It is unknown at this point what the user impact is of removing pre-1970 data from major financial/business centres (no major location has yet been merged) 7) No existing IDs get pre-1970 data, but a *new* set of IDs are created containing it - As per #5, the existing IDs get no pre-1970 data and the split between region and non-region locations is healed - New IDs, such as "Historic/Europe/London" or "Historic/Africa/Abidjan" get created for each of the main IDs - The historic IDs include pre-1970 data, the standard IDs do not - There is a mechanical transformation between the historic and non-historic IDs - Whether downstreams do or do not include the historic IDs is their choice, potentially based on available space - The data provided by the standard non-historic IDs remains the same whether the downstream includes the historic IDs or not (a Good Thing) - Users have to deliberately opt-in to get pre-1970 data, which might make them think about the accuracy issue Notes -------- - I'm not discussing adding new IDs simply to represent locations whose clocks differ only before 1970. I don't personally think that is a job for tzdb, and even if it is, it is a job for a different thread. - I'm not discussing what value is returned prior to 1970 when pre-1970 data is removed. That would be a job for a different thread. - Link vs Zone is not important for this discussion. Summary ------------- After a few weeks of thinking, these are the options I've come up with. Feel free to suggest another option or variant if you think I've missed anything obvious. I believe that was a disaster that the brilliant "ID as needed for post-1970 data, with at least one per ISO country" rule was removed. It has created needless division, bifurcating a unified set of ID into region and non-region IDs and creating backwards compatibility issues in the data of many locations. IMO, there are two basic models of timezones in the world, and moving tzdb from one that supported both to one that only supports the US-centric model is simply a mistake that needs correcting. As such, my preference would be to adopt option 2. Option 6 or 7 could work, and might be the best choices if we had a clean slate or if there was some hidden pressure that the list is unaware of to remove pre-1970 data, but they are risky options given we do not know the impact on end-users in major financial/business centres. Stephen [1] https://mm.icann.org/pipermail/tz/2021-September/030518.html

23 59

event of interest: Future of Europe debates – The end of DST: how can it be placed back to the European agenda?
by BASTIAN Michelle Oct. 28, 2021

Oct. 28, 2021

Hi all, I was just at events for the Barcelona Time Use initiative time use week 2021 and the panel on changing DST in Europe was very interesting and I thought some of you might want to take a look. It is free to sign up and you can access recordings of all the events including the one on time zones/DST. Description and link below. Loved that there was lots of talk about there being no problem having many more time zones in Europe as ‘our computers handle all of that for us now’. https://timeuseweek.beplanet.tv/en/ Future of Europe debates – The end of DST: how can it be placed back to the European agenda? In 2019, the European Parliament agreed to end the biannual clock change. Nevertheless, the Member States have not been able to achieve an agreement on which time zone has to be adopted. This debate explores how can we place back the debate on the European and Member States agenda. Representative of European Parliament Pending to confirm Maria Nikolopoulou European social and economic council Ticia Luengo International Association for Natural Time Till Roenneberg World Federation of Societies for Chronobiology Best, Michelle. --- Dr Michelle Bastian Mid-Career Fellow, Independent Social Research Foundation (Project info<https://www.isrf.org/fellows-projects/michelle-bastian/>) Senior Lecturer in Environmental Humanities ESALA, Edinburgh College of Art, University of Edinburgh The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.

3 2

Re: [tz] tzcode2021e: uninitialized variable in localtime.c
by Paul Eggert Oct. 27, 2021

Oct. 27, 2021

On 10/22/21 07:49, Christos Zoulas wrote: > My linter reports "prevcorr" is uninitialized in the if statement > below the comment that starts "To avoid other botches". Thanks for mentioning that. This prompted me to find an obscure bug in localtime that would cause it to access an uninitialized local variable (which is undefined behavior) in cases involving 32-bit time_t code reading malformed 64-bit data. I installed the attached patch to fix the bug, and I hope this also pacifies your linter.

2 1

[PROPOSED] Be more generous when dealing with v1 data
by Paul Eggert Oct. 27, 2021

Oct. 27, 2021

* NEWS: Mention this. * localtime.c (tzloadbody): In version 2 and later files, do not attempt to validate the version 1 header and data block; instead, ignore them except for the purpose of skipping over them, as per a recommendation in RFC 8536 section 4. Also, when the TZif file is version 1 and we break out near the end of the loop, do so only after altering nread and memmoving any later data; this avoids having later code attempt to parse the version 1 header as if it were a TZ string. --- NEWS | 6 +++++ localtime.c | 71 +++++++++++++++++++++++++++++++---------------------- 2 files changed, 47 insertions(+), 30 deletions(-) diff --git a/NEWS b/NEWS index d4a9823..0f684f7 100644 --- a/NEWS +++ b/NEWS @@ -14,6 +14,12 @@ Unreleased, experimental changes Fix bug when 32-bit time_t code reads malformed 64-bit TZif data. (Problem reported by Christos Zoulas.) + When reading a version 2 or later TZif file, the TZif reader now + validates the version 1 header and data block only enough to skip + over them, as recommended by RFC 8536 section 4. Also, the TZif + reader no longer mistakenly attempts to parse a version 1 TZIf + file header as a TZ string. + Release 2021e - 2021-10-21 18:41:00 -0700 diff --git a/localtime.c b/localtime.c index 6d736b2..39ef6e3 100644 --- a/localtime.c +++ b/localtime.c @@ -434,35 +434,45 @@ tzloadbody(char const *name, struct state *sp, bool doextend, if (close(fid) < 0) return errno; for (stored = 4; stored <= 8; stored *= 2) { - int_fast32_t ttisstdcnt = detzcode(up->tzhead.tzh_ttisstdcnt); - int_fast32_t ttisutcnt = detzcode(up->tzhead.tzh_ttisutcnt); - int_fast64_t prevtr = -1; - int_fast32_t prevcorr; - int_fast32_t leapcnt = detzcode(up->tzhead.tzh_leapcnt); - int_fast32_t timecnt = detzcode(up->tzhead.tzh_timecnt); - int_fast32_t typecnt = detzcode(up->tzhead.tzh_typecnt); - int_fast32_t charcnt = detzcode(up->tzhead.tzh_charcnt); - char const *p = up->buf + tzheadsize; - /* Although tzfile(5) currently requires typecnt to be nonzero, - support future formats that may allow zero typecnt - in files that have a TZ string and no transitions. */ - if (! (0 <= leapcnt && leapcnt < TZ_MAX_LEAPS - && 0 <= typecnt && typecnt < TZ_MAX_TYPES - && 0 <= timecnt && timecnt < TZ_MAX_TIMES - && 0 <= charcnt && charcnt < TZ_MAX_CHARS - && (ttisstdcnt == typecnt || ttisstdcnt == 0) - && (ttisutcnt == typecnt || ttisutcnt == 0))) - return EINVAL; - if (nread - < (tzheadsize /* struct tzhead */ - + timecnt * stored /* ats */ + char version = up->tzhead.tzh_version[0]; + bool skip_datablock = stored == 4 && version; + int_fast32_t datablock_size; + int_fast32_t ttisstdcnt = detzcode(up->tzhead.tzh_ttisstdcnt); + int_fast32_t ttisutcnt = detzcode(up->tzhead.tzh_ttisutcnt); + int_fast64_t prevtr = -1; + int_fast32_t prevcorr; + int_fast32_t leapcnt = detzcode(up->tzhead.tzh_leapcnt); + int_fast32_t timecnt = detzcode(up->tzhead.tzh_timecnt); + int_fast32_t typecnt = detzcode(up->tzhead.tzh_typecnt); + int_fast32_t charcnt = detzcode(up->tzhead.tzh_charcnt); + char const *p = up->buf + tzheadsize; + /* Although tzfile(5) currently requires typecnt to be nonzero, + support future formats that may allow zero typecnt + in files that have a TZ string and no transitions. */ + if (! (0 <= leapcnt && leapcnt < TZ_MAX_LEAPS + && 0 <= typecnt && typecnt < TZ_MAX_TYPES + && 0 <= timecnt && timecnt < TZ_MAX_TIMES + && 0 <= charcnt && charcnt < TZ_MAX_CHARS + && 0 <= ttisstdcnt && ttisstdcnt < TZ_MAX_TYPES + && 0 <= ttisutcnt && ttisutcnt < TZ_MAX_TYPES)) + return EINVAL; + datablock_size + = (timecnt * stored /* ats */ + timecnt /* types */ + typecnt * 6 /* ttinfos */ + charcnt /* chars */ + leapcnt * (stored + 4) /* lsinfos */ + ttisstdcnt /* ttisstds */ - + ttisutcnt)) /* ttisuts */ + + ttisutcnt); /* ttisuts */ + if (nread < tzheadsize + datablock_size) + return EINVAL; + if (skip_datablock) + p += datablock_size; + else { + if (! ((ttisstdcnt == typecnt || ttisstdcnt == 0) + && (ttisutcnt == typecnt || ttisutcnt == 0))) return EINVAL; + sp->leapcnt = leapcnt; sp->timecnt = timecnt; sp->typecnt = typecnt; @@ -578,13 +588,14 @@ tzloadbody(char const *name, struct state *sp, bool doextend, ttisp->tt_ttisut = *p++; } } - /* - ** If this is an old file, we're done. - */ - if (up->tzhead.tzh_version[0] == '\0') - break; - nread -= p - up->buf; - memmove(up->buf, p, nread); + } + + nread -= p - up->buf; + memmove(up->buf, p, nread); + + /* If this is an old file, we're done. */ + if (!version) + break; } if (doextend && nread > 2 && up->buf[0] == '\n' && up->buf[nread - 1] == '\n' && -- 2.31.1

1 0

Extra transition type is generated by zic with -r specified
by Almaz Mingaleev Oct. 26, 2021

Oct. 26, 2021

I’ve tried to generate a TZif file with transitions up to 1 Jan 2100 using zic with -r and “-b fat”. However, an extra transition type is generated for many (all?) time zones. That type’s UTC offset is zero and it is used only for the last transition in the 64-bit section. What I did: mkdir /tmp/zic cd /tmp/zic git clone https://github.com/eggert/tz.git . make -C . zic make -C . NDATA= rearguard.zi mkdir data ./zic -b fat -r /@4102444800 -d ./data rearguard.zi Below is an investigation for Australia/Lord_Howe (I don’t think choice matters here). I couldn’t find a way to force zdump to print transitions for a given TZif file. Instead, please see human-readable dumps from the TZif from our internal tools immediately below and raw byte information at the bottom if you’d prefer to work with that. These are local time transition types for Australia/Lord_Howe: Types gmtOffset (seconds),isDst,ttisgmt,ttisstd,[gmtOffset ISO],[DST?] 38180,0,,,PT10H36M20S,STD 0,0,,,PT0S,STD <- this is odd 36000,0,,,PT10H,STD 41400,1,,,PT11H30M,DST 37800,0,,,PT10H30M,STD 39600,1,,,PT11H,DST Transitions: transition,type,[UTC time],[Type offset],[Type isDST] … 4063275000,5,2098-10-04T15:30:00Z,PT11H,DST 4078998000,4,2099-04-04T15:00:00Z,PT10H30M,STD 4094724600,5,2099-10-03T15:30:00Z,PT11H,DST 4102444800,1,2100-01-01T00:00:00Z,PT0S,STD <- this is odd So, after the upper bound specified in -r, the transitions say that GMT is used. As I’d expect, the 32-bit transitions are not affected when the upper bound in -r is after 2038. However, with -r /@1634833073 the 32-bit section also has 6 transition types and the last transition sets offset to 0. Is that a bug or is there a reason for such behaviour? Thanks, Almaz Byte manipulations: typecnt is 5 in 32-bit section: xxd -seek 36(4+1+15+4*4) -len 4 data/Australia/Lord_Howe 64-bit section starts at offset 674. timecnt is 0xF0(=240) in 64-bit section: xxd -seek 706(674 + 20 + 3 * 4) -len 4 data/Australia/Lord_Howe typecnt is 6 in 64-bit section: xxd -seek 710(706 + 4) -len 4 data/Australia/Lord_Howe So, 64-bit header has one extra transition type. Let’s check how it is used and what that transition is: 2638 = 674 + 44 + 240 * 8 xxd -seek 2638 -len 240 -c 1 data/Australia/Lord_Howe prints transition types: 00000b38: 05 . 00000b39: 04 . 00000b3a: 05 . 00000b3b: 04 . 00000b3c: 05 . 00000b3d: 01 . Transition type is changing from 4 to 5, but the last one is 1. xxd -seek 2878 -len 36 -c 6 data/Australia/Lord_Howe prints local time type records: 00000b3e: 0000 9524 0004 ...$.. 00000b44: 0000 0000 0000 ...... <- the last transition type 00000b4a: 0000 8ca0 0008 ...... 00000b50: 0000 a1b8 010d ...... 00000b56: 0000 93a8 0013 ...... 00000b5c: 0000 9ab0 0119 ...... Which means that 1st type’s offset is 0 and that the last rule for Lord Howe is actually GMT.

2 4

[PROPOSED] Improve Palestine predictions for 2025 and later
by Paul Eggert Oct. 25, 2021

Oct. 25, 2021

* NEWS: Mention this. * asia (Palestine): Guess Fri>=23, not lastFri, for fallback transitions in the future. Fri>=23 is more consistent with past practice than lastFri. The first differing prediction is a fallback on 2025-10-24, not 2025-10-31. --- NEWS | 10 ++++++++++ asia | 2 +- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index a7aa269..d83e01c 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,15 @@ News for the tz database +Unreleased, experimental changes + + Changes to future timestamps + + Predict Palestine fallbacks to be the first Friday on or after + October 23, not October's last Friday, to be more consistent with + past practice. The first differing prediction is a fallback on + 2025-10-24, not 2025-10-31. + + Release 2021e - 2021-10-21 18:41:00 -0700 Changes to future timestamps diff --git a/asia b/asia index dd228e5..6d6b1de 100644 --- a/asia +++ b/asia @@ -3445,7 +3445,7 @@ Rule Palestine 2019 only - Mar 29 0:00 1:00 S Rule Palestine 2019 only - Oct Sat>=24 0:00 0 - Rule Palestine 2020 max - Mar Sat>=24 0:00 1:00 S Rule Palestine 2020 only - Oct 24 1:00 0 - -Rule Palestine 2021 max - Oct lastFri 1:00 0 - +Rule Palestine 2021 max - Oct Fri>=23 1:00 0 - # Zone NAME STDOFF RULES FORMAT [UNTIL] Zone Asia/Gaza 2:17:52 - LMT 1900 Oct -- 2.31.1

3 3

Wrong name of timezone
by Igor Melnyk Oct. 25, 2021

Oct. 25, 2021

Hello! There is *Europe**/Kiev* timezone related to Ukraine. But Ukraine has the Ukrainian language and *Kiev* is in russian language. The correct name of the capital city of Ukraine is *Kyiv.* It must be changed. I know that it's not easy to do that but you must have some way to do that. For example, rename *Europe/Kiev* to *Europe/Kyiv* and make *Europe/Kiev* to be a temporary alias or link to *Europe/Kyiv.* What do you think about it? Best regards, Igor Melnyk.

1 0

Re: [tz] Palestine winter time
by Paul Eggert Oct. 22, 2021

Oct. 22, 2021

On 10/21/21 01:03, heba.hamad(a)mtit.gov.ps wrote: > Could you please confirm that Palestine winter time has been adopted in IANA time zone database Yes, tzdb release 2021e was published today with the updated Palestine winter time. The announcement is archived here: https://mm.icann.org/pipermail/tz-announce/2021-October/000069.html

2 2

[tz-announce] 2021e release of tz code and data available
by Paul Eggert via tz-announce Oct. 22, 2021

Oct. 22, 2021

The 2021e release of the tz code and data is available. This release reflects the following changes: Changes to future timestamps Palestine will fall back 10-29 (not 10-30) at 01:00. (Thanks to P Chan and Heba Hemad.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2021e.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2021e.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2021e.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit b102002e5300d94c369796d5b70bae22b5af720d dated 2021-10-21 18:41:00 -0700 and tagged '2021e' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 87b0335129ea41c5f42f687f548712e5da892baa8494cecf5d34851beceecf6ae52f22104696ed187713cf9e502570eb2041e277dfd3c043c11d0253bfde685a tzcode2021e.tar.gz c1e8d04e049157ed5d4af0868855bbd75517e3d7e1db9c41d5283ff260109de46b6fac6be94828201d093e163d868044ac2a9db2bf0aeab800e264d0c73a9119 tzdata2021e.tar.gz 8abd662f07a91eed5b77d03eaa3e9ef59ce08b4e3fc14f9857095c3d4f2039e8ac216fc985b0cf87a823eacad064197c8ecb76ba531a9fc700014d7f0057aba8 tzdb-2021e.tar.lz Here are the GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmFyF3cACgkQ7ZfpDmKq fjQKRw//c5HpFCN0vcPUIC/OQKTF/SXFOANCpHWypc/vgTVXFAsVu0zIKWdBuXXI 0zQDpbTcTJ2FfI5Z1JGNzeKa2G4Wy71lwwPu2mGDt0WCCAqh/l15XvgVEAM96YLG WZRK+WLKIVWgZ67NA2xWAt9VLgtA643Cgym1DCpsr9jTDAhGSYq8D0XC5OQHtfw2 oyzv4InTW+0EI14FQcQ3VqImLwGSefeYPfMBRjrAspqrTLez78vW914IWNKcgEoC pKCkq9+14u0L+G5j5E+f27gbRtZ4hZnIn5uNgItomJmGObW6khn0Huf+G6U1BAal 2zLSAYMubr1kq/6dP62QUivi1W2S3YRZDh20YsKxn214HW5qK5LdQKYruBGKOFou 7oAe91W3UW0vSJuboXj0Dbdc3p8Oay97eJ/kRDVKJZ95/UOQtwrkQi2wCbm19eC8 kvHdejbIrOvdl+ZpvkHIggQGSOchyXUASeqnX/9zirOAX0N05insC/ybJLAwepFm FqpvcfwjrJKCotAjFEEex1uIT5kgQwIumvtxLef3bGQgYtF1yfWMD0NSJAR1iAU2 BzXuikOLPNbHWpC41ODgRxBVaQnMpliC0WGJ/HiVT78ukEkx0MpcxyfnxjEDD7fz F3GlJlj/bw5rvsPrFzbSjYyzXfrn0u1y8/vgehUmtSj1K7MmB6I= =CliF -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmFyF3cACgkQ7ZfpDmKq fjSLPw/9EDTMMp0ySiPkYgXICy+hYq78xDOpF5IU34tcvmL2j3OZiM49X//CQzNF 7kLoEkYenpjJZ9QU8V0w+26UJF3js/R3a9gLU3ybPZ7+o+NOanQK68z5EvggWGfm 0yVCGbPhsKNoP/2Xtpv3gLiT6WoBvJF6k16mRQtiE7ngLJ3OUpaWaQAZ73F+sMTY I5F++cAdTvOTHw6M4ORmvp8OMg2df1KVXf2MINQZkx3OVxw+y6zaMwcKUJHz81eY KCDO6DJyoj48/WNDxfIiYVk2YoOVm9I3HiqgmrojmniJFLCq/PkWGqU61gmNCSRv 5vLjb9qnfWQG8E3E44pdH8aqZt7z7kYdcL89y5UnDBlJMmoh/cPigjfBmAot7Erw 5Mj8pp/a7tcvHKIoGZscIzjRnffYDHTD6rNwStVvTfKyGE7O6Fa63yUnndCudqdu 6nZCQNkELrn9ber4ieJR6d46LOVFvqlMhCzhknZRUBkbtU4ltwBze8RvrGGhdyJ3 s9YQtGpY1uEcNF4JWzqkE9sXtPnevFERUT1hZdQpJ2NM0mrVKAfdLhryvJyi+t30 fbMbyqmYRhPuyk7OUPbduTIXc4IIpSzAaeQRFwZqDGSOuOj+8JSk6EX9Kwel7ahp 2PIzzyffxL7m2kG9+iAKckRHz0nyvoYGHQl1gsah9qUVx2Q/JIo= =kEHz -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmFyF3cACgkQ7ZfpDmKq fjSLPw/9EDTMMp0ySiPkYgXICy+hYq78xDOpF5IU34tcvmL2j3OZiM49X//CQzNF 7kLoEkYenpjJZ9QU8V0w+26UJF3js/R3a9gLU3ybPZ7+o+NOanQK68z5EvggWGfm 0yVCGbPhsKNoP/2Xtpv3gLiT6WoBvJF6k16mRQtiE7ngLJ3OUpaWaQAZ73F+sMTY I5F++cAdTvOTHw6M4ORmvp8OMg2df1KVXf2MINQZkx3OVxw+y6zaMwcKUJHz81eY KCDO6DJyoj48/WNDxfIiYVk2YoOVm9I3HiqgmrojmniJFLCq/PkWGqU61gmNCSRv 5vLjb9qnfWQG8E3E44pdH8aqZt7z7kYdcL89y5UnDBlJMmoh/cPigjfBmAot7Erw 5Mj8pp/a7tcvHKIoGZscIzjRnffYDHTD6rNwStVvTfKyGE7O6Fa63yUnndCudqdu 6nZCQNkELrn9ber4ieJR6d46LOVFvqlMhCzhknZRUBkbtU4ltwBze8RvrGGhdyJ3 s9YQtGpY1uEcNF4JWzqkE9sXtPnevFERUT1hZdQpJ2NM0mrVKAfdLhryvJyi+t30 fbMbyqmYRhPuyk7OUPbduTIXc4IIpSzAaeQRFwZqDGSOuOj+8JSk6EX9Kwel7ahp 2PIzzyffxL7m2kG9+iAKckRHz0nyvoYGHQl1gsah9qUVx2Q/JIo= =kEHz -----END PGP SIGNATURE----- PS. If your tzdata parser does not yet support negative DST offsets or times past 24:00, or if it insists on a 'pacificnew' file that is no longer present, this release's data entries can be turned into a rearguard-format tarball that should work even with these older parsers. This is intended to be a temporary transition aid for these parsers. To generate a rearguard-format tarball, obtain the full distribution as described above, and run the command 'make rearguard_tarballs' on a development host. Or you can run 'make rearguard.zi' to generate a single file that can be fed directly to a parser that works like 'zic'.

1 0

Re: [tz] Palestine winter time
by Paul Eggert Oct. 21, 2021

Oct. 21, 2021

On 10/20/21 01:47, heba.hamad(a)mtit.gov.ps wrote: > winter time will begin in Palestine from Friday 10-29 ,01:00 AM by 60 minutes backwards. Thank you for letting us know. Attached is a proposed change to tzdb, installed into its development version <https://github.com/eggert/tz>. We plan to have a new tzdb release soon. This change implements this year's transition, and also guesses that winter time will begin on October's last Friday at 01:00 in 2022 and later years, to be consistent with 2021. If this guess is wrong, please let us know as far in advance as possible, because rule changes trickle out only slowly to cell phones and computers.

2 1

The origin of time zone regions
by Arthur David Olson Oct. 21, 2021

Oct. 21, 2021

A middling-length story with a small point. In the seventies and eighties, I helped develop two-dimensional PAGE* image analysis software. Black and white images had a thousand or so spots; the positions of the spots and their size provided information on the characteristics and abundances of proteins in samples. Step one was to get the positions and sizes of spots in a single image. Step two was to compare two images, pairing up the spots. Some spots would only appear in one image and have no pairs; in other cases, two (or more) spots would appear in one image where only one appeared in the other; one spot would be paired with multiple spots. The final step was to consider groups of images. For this purpose, there were groups of spots where (to quote an article on the matter) “each spot in a group is paired with some other spot in the group and no spot in any group is paired with any spot in any other group.” In the mid-eighties, work started on the time zone database. And time zone regions ended up being defined as being places where all the clocks agreed. The small point: the nature of time zone regions has less to do with chronometry or geopolitics than it does with gel analysis. @dashdashado _ * https://www.sciencedirect.com/topics/neuroscience/two-dimensional-gel-elect…

1 0

Re: [tz] Pre-1970 data
by Stijn “Adhemar” Vandamme Oct. 20, 2021

Oct. 20, 2021

The “should timezones be merged when they contain identical offsets from 1970 onwards” discussion has been going on for quite a while on the tz mailing list. Still, contributions that I find insightful are still being made. Stephen Colebourne recently made this observation: > The key observation is that the segregation between these two groups > > of IDs *did not exist* until around 2014. It was only in 2018 that the > > ISO country rule was removed. > This change was reflected in the documentation <theory.html> as recently as 20/21 February 2019 < https://github.com/eggert/tz/commit/5f48dee82bc111b21f3610893e3b788e37396bce > < https://github.com/eggert/tz/commit/6176aefe79e83ddb8f255849b85c149f34d46aba > And Stephen made this spot-on point of analysis: > FWIW, it is clear to me that there is an aspect of imposing a > > US-centric timezone system on other parts of the world. The recent > > tzdb approach of focussing entirely on timezone regions makes perfect > > sense for the US, where region boundaries do not follow state lines, > > and ordinary members of the public need to be aware of whether they > > are in US/Mountain or US/Central. This simply isn't the timezone model > > in many other parts of the world. In places like Europe and Asia, the > > timezone is driven primarily by the country you live in - an ordinary > > member of the public in Iceland is never going to associate with some > > abstract timezone region stretching down the Atlantic that is not > > named, not legally defined and is little more than a random outcome > > based on tzdb's choice of 1970. Even in somewhere like Norway, an > > ordinary member of the public will understand that although they > > follow CET, their timezone is actually driven by their Government in > > Oslo. The brilliance of the original rule - "ID as needed for > > post-1970 data, with at least one per ISO country" - was that it > > seamlessly handled *both* models of timezone in one unified set of > > IDs. Removal of the ISO country part has completely destabilised that > > balance. > If I may throw in my two-penny, it would pertain to the documentation of this policy. Presently, <theory.html> does mention - that timezones are zones whose clocks all agree about timestamps that occur after the 1970 POSIX Epoch; - that 1970 is indeed a somewhat-arbitrary cutoff, but that moving it earlier even by a decade or two would impose significant challenges, due to the wide variety of local practices before computer timekeeping became prevalent; - that pre-1970 clock transitions are recorded for location-based timezones, but that the database is not designed for and does not suffice for applications requiring accurate handling of all past times everywhere; - that the previous “at-least-one-timezone-per-country-with-officially-designated-ISO-3166-1-two-letter-country-code” rule is dropped for this imposed too high a maintenance burden; and - that some information outside the scope of the database (implied: pre-1970) is collected in a file backzone that is distributed along with the database proper, but that this file is less reliable and does not necessarily follow database guidelines. What astonishes me in this issue is that high-quality information is being removed from the database proper into backzone, without this being mentioned in the documentation <theory.html>. Granted, <theory.html> does not explicitly state an “at-least-attempt-to-get-monotonically-closer-to-the-truth-with-increasing-versions” policy, but one would think that’s implied in maintaining a (versioned) database, unless explicitly stated otherwise. The other way around (moving information from backzone to the database proper, e.g. when historical information is double-checked and confirmed to be in accordance with database guidelines) is totally acceptable without mentioning in the documentation <theory.html>. Indeed, even though I know that correcting pre-1970 data is not the priority of this project, I’ve seen some great sluthing of historical time zone offsets presented on the tz mailing list in the past, and I kinda assumed that the results of such research found its way to the database proper (or backzone when doubts remained). In my opinion, removing high-quality information — thereby having correct offsets changed into incorrect offsets in information systems that rely on the tz database and keep it up-to-date on the default settings (which disregard backzone) — should cease, and should preferably be undone where such damage has already occured. Seeing how much problems pursuing “fairness” under the new rules causes, perhaps it’s worth reinstating the previous “at-least-one-timezone-per-country-with-officially-designated-ISO-3166-1-two-letter-country-code” rule, either officially or unofficially. (And for what it’s worth, this comes from someone who generally tries to avoid relying on country lists such as ISO 3166-1, due to strong political belief in the desirability of independence or at least increased self-governance for several countries/regions currently lacking an officially-designated ISO 3166-1 two-letter country code, including Flanders, Wallonia, Scotland, Catalonia, Basque Country, Canary Islands, Tibet, and others.) But alternatively, if this project persists in its “removing-high-quality-information and merging-for-merging’s-sake” policy, then at the very least this should be mentioned clearly, unambiguously and conspicuously highlighted (bold, bigger font size, bright but fully saturated background colour, following an animated warning icon, the lot) in the documentation <theory.html>: PREVIOUSLY OR CURRENTLY CORRECT PRE-1970 OFFSET INFORMATION IS > INTENTIONALLY BEING CHANGED AND/OR MAY INTENTIONALLY BE CHANGED IN LATER > VERSIONS OF THE tz DATABASE INTO INCORRECT OFFSET INFORMATION for the > braindead reason of merging timezones for merging’s sake. > USERS MUST NOT RELY ON UNDISPUTEDLY AND UNCONTESTEDLY CORRECT AND VERIFIED > OFFSET INFORMATION REMAINING CORRECT in the database proper, except for > timezones that have post-1970 particularities which prevent them from being > merged with foreign timezones. (And even then — who knows what the > coordinator-maintainer will come up with next…) > Information systems that rely on tz for offset information, including for > pre-1970 datetimes-with-timezone-identifier, ought to pass this warning on > to their users. > — Adhemar

1 0

Palestine winter time
by heba.hamad＠mtit.gov.ps Oct. 20, 2021

Oct. 20, 2021

Dear Sir, I’m Heba Hamad .I have been appointed as a focal point by the Ministry of telecommunication and information technology (state of Palestine) to communicate with you. We would like to inform you that winter time will begin in Palestine from Friday 10-29 ,01:00 AM by 60 minutes backwards. Kindly find the attachment below that includes the decision of the Palestinian cabinet. With Respects, Sent from Mail for Windows

4 4

Palestine winter time
by P Chan Oct. 18, 2021

Oct. 18, 2021

http://wafa.ps/Pages/Details/34701 https://www.facebook.com/wafagency/posts/4457787417632704 Palestine winter time will start from midnight 2021-10-29 (Thursday-Friday).

4 4

[tz-announce] 2021d release of tz code and data available
by Paul Eggert via tz-announce Oct. 15, 2021

Oct. 15, 2021

The 2021d release of the tz code and data is available. This release reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Fiji suspends DST for the 2021/2022 season. 'zic -r' marks unspecified timestamps with "-00". Changes to future timestamps Fiji will suspend observance of DST for the 2021/2022 season. Assume for now that it will return next year. (Thanks to Jashneel Kumar and P Chan.) Changes to code 'zic -r' now uses "-00" time zone abbreviations for intervals with UT offsets that are unspecified due to -r truncation. This implements a change in draft Internet RFC 8536bis. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2021d.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2021d.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2021d.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 4de3d7f2499328c97e652242a36fed9523741d12 dated 2021-10-15 13:48:18 -0700 and tagged '2021d' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: dbd7e3df02a11676600aa7efa14592feb2ac9ab5807b0d395e0c29ff1ed4a31580120287df9fe0c65a78162157dcd31d9fbe90a2a93bfd891d59ae3668a3adda tzcode2021d.tar.gz e25e85679256cfa57072cc8902aad1ca1df5ddc4a06844ca38bd57c8b5ad386e38303654dc85525f4fb470a924db4deb3576827a14d3ff87f4a1c679414b95c9 tzdata2021d.tar.gz 6ccb3ed6ebf35643cb49d503f18b7c66957de098f41870fd14ac37489b0931abd6d3e7bf5c2797e69f56f44b31ff9f9068ffa40f5aa29260ecda9d0aac878103 tzdb-2021d.tar.lz Here are the GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmFp6ekACgkQ7ZfpDmKq fjQtmBAApD1Am4P0gbEECXOABxrnE258QrPRqPhupj45gW0kMD5BehW+yO2oIzOU zDmgLbWyG5CmbD2lSt2fq1mZKhfqYD2J4QJlwwiPGHriNKZZCVIQniXZVRFUzQz/ oObtIzNm5mgR6OUhWDcbzYZsa10eJ7HTMrDOGViZ7T1DyLj5yobSXqkC/Q/ZlEvM Vpnl9nDieey2GgXvobfpR+Bby6NB26Pojjab9Mbw9jyRtcvnf6GmdBn6v4aoDwKc ZUqcb9qjv7NXnN5o9nCUSK7/ad+RoVZJAVDe84Quj1Vn8ydfZ0/1+i6bF3mM6Bpi I3riuPKkv7AHW2iRgZPnnqH7U+X32gb55/+WleokkasZj7e8i1QjJW7L0b91YOHN USz1McquYNsh/n9IDph4Zw1tBpbmLYAy3HQPaR6OzO8fc9paw5nsoics/5fQ5WoZ 2T2EavJfa045XKxwzd57w9YthQgW27Ep6UMpVCEGjYCBfVt8MfmiB787apGJdeJj NeVaKfSfpE4PTWvrtfTXPCIVIbIhlA5UUXyhEBXrMJw/FVxf8rAHGi/zvmrgl48X iY/xMG4yWpUYwZqWG0NBeGE0tvj8Yj2NagWj/UnGXcte3MvgmjkFSnKhj+UZrcA+ 1ehgE8pGicWEl0xl7uW6uwJ1IgWBMHYIkxpslJdTru+nnfbBIaA= =Bvd6 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmFp6ekACgkQ7ZfpDmKq fjTbSA/9HBEpib2dXzZg06u4WuVwFEbzu1AUblHm7I9PAzoxtTvJJqH0dMCrHDlj wldeHGclbBxLq8wF33Ajh7bvgISDhmjQCm/ux7nS0ctRnPkV4Pj2j6lsfk/gYVIB agFefLTTrdHaIrPxZ9TK7c63X+6HMfFDnE+nOrJXimls/gW/Xu/VeMDtngrCIoB3 JTSbPePbaSlA+NMn+RRhfb6jlw/Slbm7n5Zpf+VSZs2HN4+bNpHuFLbl5oMbPOrQ C+va/yKJXrNYroGOfIlz/ZnM24ZGDterLh9BBLe+zy3Ni+dhuH0x406C8zkZXSDu U1BZvHK3f84beSF0H1SbkGyjkfVSIol1o2p69mMdcyZzewng3n+MLB8lNxyMkmyk f8cTKviE0V+xoEe/yV8+0+uDhli+oLMudqNGy8eCRNgrnRkCsP513LMX73bagohQ xjtBd+cp2VSzhV4vXsJJE7mIwzofnZaGqdR/jyHND+4gx80TQo8Ftc29wRGbwCCI WU37r17EmcOPg+emOciIf8nYCPnIvKGBBZ0UcCEuvaZXXYhyg+2c82z7A+bIPZaS 6wQZhqptoWB07tJOMxcgCCV7I1fT8+GLlLLlJQXladooOa06mVzsFk8VlUX4PRl3 bIQGNgqRtoE/RnhbxgD0A4ToYUqdMvYzcoCGIGpg/4zmyFZWcaY= =NgZm -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmFp6esACgkQ7ZfpDmKq fjSsWg/+NCtwn4E06FCtkR08EV0R8uG4xI6HyQc8JsB5DiFkt+evge2Bu+De03y5 nUJ1eaWbg27MLMfdYI7q5tET9G5RRcFUSZx5Zpj+Bv++KHEz7QSB5ZajE2n2qi93 AkXtFEQn8n0sCKbxdpikiUtKyZbIhcBZkzpAVU3sDdphoLUJFI2YPUCwNL5sPnzH 9pI9/iXCvu1mDW0Mg+mdBO6BuMVmTZneSJ+qtWVRvDPBvWJu8vDr16YiNaTYXkX6 atnvTDmjc3RP5DAjFzItBjsZWcLfrWWQ9WezYXWGDmJS+ijxSH0eYAUfXdHESMMd ggNwlsYZumla1p8yGmHP7YkUynds2hZYV8ySCZhfaCjq/AYANs2hzYLIY5reQ6mJ XxRoGOECc2uCmIVwFjYAALghW0GnDAy6M/l+qgzSxAr92Y0GdlFSdv8yWvIBYPyg /gFKrS+IkLHPJEF5vcpxCpCJC2XR2lJLAzoAgLUc14kD5enmVUjJzia8CpKahq2S argJwtnUl+pZT5QLfOSC46jG2o+RnhSarPSNb21cs+eNnPMA31aXDIRrGDCJ6UXf nRAU1t7eq4bbb/cvEGgJ9ZCfoQpBhYT4QO8as4JXnzkHrB7PuUiqw2sOXixF6H46 MSKRQq/uWI6XiAbXpUDFh67EeH/U1YkR8mx67Uii6pcGLvK2ptM= =Brw7 -----END PGP SIGNATURE----- PS. If your tzdata parser does not yet support negative DST offsets or times past 24:00, or if it insists on a 'pacificnew' file that is no longer present, this release's data entries can be turned into a rearguard-format tarball that should work even with these older parsers. This is intended to be a temporary transition aid for these parsers. To generate a rearguard-format tarball, obtain the full distribution as described above, and run the command 'make rearguard_tarballs' on a development host. Or you can run 'make rearguard.zi' to generate a single file that can be fed directly to a parser that works like 'zic'.

1 0

[PROPOSED 1/3] Document that -00 means local time is unspecified
by Paul Eggert Oct. 15, 2021

Oct. 15, 2021

* tzfile.5, zic.8: Document longstanding practice in time zone abbreviations. This better matches draft RFC 8536bis. --- tzfile.5 | 4 +++- zic.8 | 3 +++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/tzfile.5 b/tzfile.5 index 74564cb..e2f11b4 100644 --- a/tzfile.5 +++ b/tzfile.5 @@ -118,7 +118,9 @@ and serves as an index into the array of time zone abbreviation bytes that follow the .B ttinfo -structure(s) in the file. +entries in the file; if the designated string is "\*-00", the +.B ttinfo +entry is a placeholder indicating that local time is unspecified. The .B tt_utoff value is never equal to \-2**31, to let 32-bit clients negate it without diff --git a/zic.8 b/zic.8 index 3727922..89fc827 100644 --- a/zic.8 +++ b/zic.8 @@ -559,6 +559,9 @@ alphanumeric ASCII characters, .q "+" and .q "\*-". +By convention, the time zone abbreviation +.q "\*-00" +is a placeholder that means local time is unspecified. .TP .B UNTIL The time at which the UT offset or the rule(s) change for a location. -- 2.30.2

1 2

Kiev >> Kyiv
by Pavlo Komendant Oct. 12, 2021

Oct. 12, 2021

Hello, Could you please amend the Ukraine capital in the time zone? Kyiv is the correct spelling of the Ukraine capital https://en.wikipedia.org/wiki/Kyiv Thank you! -- Pavlo

3 2

Daylight Saving in Fiji Islands
by Jashneel Kumar Oct. 11, 2021

Oct. 11, 2021

Dear Support, Please note that there will be no daylight saving this year. Appreciate if the same can be reflected in your system to ensure that the time does not change. Looking forward to the confirmation. Regards, [New_VF_Icon_RGB_RED] Jashneel Kumar Manager Data Networks & Services Jashneel.Kumar(a)vodafone.com.fj<mailto:Jashneel.Kumar@vodafone.com.fj> Vodafone Fiji PTE Limited, 168 Princes Rd, Tamavua, Suva, Fiji Islands www.vodafone.com.fj<http://www.vodafone.com.fj/> Together we can [Vodafone] ________________________________ The content of this email including any attachments is confidential and may contain information that is proprietary and privileged. If you are not the intended recipient be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. If you have received this email in error please notify E-mail Administrator on info(a)vodafone.com.fj Please also destroy and delete this message from your system. Vodafone Fiji PTE Limited does not guarantee that this message is free from computer virus or any other defect. The reader accepts full responsibility for taking defensive and counteractive action needed to rectify the computer virus or other defects caused. Vodafone Fiji PTE Limited : Private Mail Bag, Suva, Fiji | Telephone : +679 3312000 | E-Mail : info(a)vodafone.com.fj Please consider your environmental responsibility before printing this e-mail [https://www.vodafone.com.fj//images/default-source/logo/logo-2x.png] Vodafone Fiji PTE Ltd <https://www.vodafone.com.fj/>

5 6

Typo in zic(8) man page
by Jonathan Wakely Oct. 8, 2021

Oct. 8, 2021

The description of a RULES field in a zone line says: "giving of the amount of time to be added" The first "of" looks like a typo.

2 1