- tz - lists.iana.org

Issue in tz America/Santiago
by Alberto Jose Rivera Rojas April 4, 2019

April 4, 2019

Before install the time change patch tzdata2019a the date command delivers the next output Thu Apr 4 11:07:36 CLST 2019 After installing the time change patch tzdata2019a the date command delivers the next output Thu Apr 4 11:07:36 -03 2019 we modified the lines 1278 changing -3 for CLST and -4 CLT. attachment Zone America/Santiago -4:42:46 - LMT 1890 -4:42:46 - SMT 1910 Jan 10 # Santiago Mean Time -5:00 - CLT 1916 Jul 1 # Chile Time -4:42:46 - SMT 1918 Sep 10 -4:00 - CLT 1919 Jul 1 -4:42:46 - SMT 1927 Sep 1 -5:00 Chile CL%sT 1932 Sep 1 -4:00 - CLT 1942 Jun 1 -5:00 - CLT 1942 Aug 1 -4:00 - CLT 1946 Jul 15 -4:00 1:00 CLST 1946 Sep 1 # central Chile -4:00 - CLT 1947 Apr 1 -5:00 - CLT 1947 May 21 23:00 -4:00 Chile CL%sT -- Atte. Alberto Rivera. +56944771319

2 1

GPS Week Number Rollover Apr 6/7
by Brian Inglis April 2, 2019

April 2, 2019

Expect some amount of time related disruption around April 7 00:00 GPS as the GPS 1K week cycle rolls over and GPS receivers that have not been patched or updated to use new CNAV and MNAV messages, or compensate for not doing so, provide incorrect time, position, and navigation solutions. Garmin, for example, rolled out updated firmware for some of their receivers, including the 18x popular on NTP servers, just over a week ago. Previous rollovers have shown symptoms of clocks being out by multiples of 256 weeks, some resetting to the GPS epoch at 1980 Jan 06 Sun 00:00:00+0000, showing misleading position and navigation solutions, depending on what inputs are used to solve the 4D simultaneous equations. Airlines, ships, and well maintained commercial trucks shouldn't crash, but the rest of us should check any devices using GPS! If my script is correct, the rollover occurs at the indicated instant on the time scales below: 2019 Apr 06 Sat 23:59:42+0000 JD 2458580.499792 MJD 58579.999792 ToD 86382 NTP 3763583982 Unix 1554595182 GPS We 2048 Cy 2 Wn 0 Wa 0 ToW 0 DoW 0 ToD 0 TAI-UTC 37 TAI-GPS 19 GPS-UTC 18 [*NOT* an April Fools post, unfortunately!] -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised.

2 2

DST in Palestine will start one week later
by Even Scharning March 29, 2019

March 29, 2019

DST in Palestine will start on 30 March this year, not 23 March as the time zone database predicted. Some references (in Arabic): http://pnn.ps/news/401130 http://palweather.ps/ar/node/50136.html https://ramallah.news/post/123610/%D9%85%D9%88%D8%B9%D8%AF-%D8%A7%D9%84%D8%… Even Scharning https://time.is

9 14

Will there be a 2019b update soon?
by Patsy Franklin March 27, 2019

March 27, 2019

Hi, Since there is now an experimental patch for the 2019a update, will there be a 2019b released soon? What would be the anticipated time frame for the update? Thanks, Patsy

3 2

Europe/Dublin daylight saving time format confusion
by Guruswamy Basavaiah March 27, 2019

March 27, 2019

Hello, Generated timezone files using the below command on release 2018e. zic -L /dev/null -d output_dir -y "sh yearistype.sh" europe zdump show daylight saving flag (isdst=1) is wrongly set for Europe/Dublin. Daylight saving time should start from March 31 and end on October 27. But here it shows reverse. zdump -v /home/basavaia/output_dir/Europe/Dublin | grep 2019 /home/basavaia/output_dir/Europe/Dublin Sun Mar 31 00:59:59 2019 UT = Sun Mar 31 00:59:59 2019 GMT isdst=1 gmtoff=0 /home/basavaia/output_dir/Europe/Dublin Sun Mar 31 01:00:00 2019 UT = Sun Mar 31 02:00:00 2019 IST isdst=0 gmtoff=3600 /home/basavaia/output_dir/Europe/Dublin Sun Oct 27 00:59:59 2019 UT = Sun Oct 27 01:59:59 2019 IST isdst=0 gmtoff=3600 /home/basavaia/output_dir/Europe/Dublin Sun Oct 27 01:00:00 2019 UT = Sun Oct 27 01:00:00 2019 GMT isdst=1 gmtoff=0 Above Behavior is same in 2019a also. If I check the same on 2018a, it gives proper output. zdump -v /home/basavaia/2018a/Europe/Dublin | grep 2019 /home/basavaia/2018a/Europe/Dublin Sun Mar 31 00:59:59 2019 UT = Sun Mar 31 00:59:59 2019 GMT isdst=0 gmtoff=0 /home/basavaia/2018a/Europe/Dublin Sun Mar 31 01:00:00 2019 UT = Sun Mar 31 02:00:00 2019 IST isdst=1 gmtoff=3600 /home/basavaia/2018a/Europe/Dublin Sun Oct 27 00:59:59 2019 UT = Sun Oct 27 01:59:59 2019 IST isdst=1 gmtoff=3600 /home/basavaia/2018a/Europe/Dublin Sun Oct 27 01:00:00 2019 UT = Sun Oct 27 01:00:00 2019 GMT isdst=0 gmtoff=0 Is my understanding correct? And this behavior is introduced in commit 127b4af7219e6df9253b34e390797c5527b8cc66 I am not in this mailing list, please include my email id while responding. -- Guruswamy Basavaiah

2 1

Re: [tz] [tz-announce] 2019a release of tz code and data available
by Paul Eggert March 26, 2019

March 26, 2019

On 3/26/19 6:02 AM, Michael H Deckers wrote: > > In the file NEWS, I read > > Release 20198 - 2019-03-25 22:01:33 -0700 > > instead of > > Release 2019a - 2019-03-25 22:01:33 -0700 > > Maybe a file transfer error? No, it's a typo. Sorry about that. I fixed it as per attached. Thanks for reporting it.

1 0

European Parliament votes to drop DST by 2021, leaving it to member states
by Tim Parenti March 26, 2019

March 26, 2019

The European Parliament has just voted 410-192 in favor of dropping its DST requirement in the EU by 2021. The vote is not the last word on the issue but will form the basis of discussions with EU countries to produce a final law. Under the proposal, each member state would decide amongst three options: - to continue with twice-a-year clock changes, - to stick permanently to summer time, or - to stick permanently to winter time. All member states would need to inform the European Commission of their choice ahead of the proposed switch, by April 2020. They would then coordinate with the bloc's executive so that their decisions do not disrupt the functioning of the single market. The European Commission proposed in September ending the practice after an EU-wide opinion survey showed a large majority in favor of doing so. The survey generated 4.6 million responses, with 84% of respondents wanting to end seasonal clock changes. Critics say the survey was dominated by Germans, who made up 70% of the respondents. https://www.dw.com/en/eu-parliament-votes-to-end-daylight-savings/a-48064185 https://www.rte.ie/news/europe/2019/0326/1038689-eu-daylight-savings/ -- Tim Parenti

5 8

Re: [tz] Proposed changes for Argentina, Jan Mayen, worldtimeengine.com, etc.
by REMI ACIEN March 26, 2019

March 26, 2019

Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10 For Atlantic /Jan Mayen , UTC-1 . It’ s yes .

2 1

[tz-announce] 2019a release of tz code and data available
by Paul Eggert March 26, 2019

March 26, 2019

The 2019a release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Palestine "springs forward" on 2019-03-30 instead of 2019-03-23. Metlakatla "fell back" to rejoin Alaska Time on 2019-01-20 at 02:00. Changes to past and future timestamps Palestine will not start DST until 2019-03-30, instead of 2019-03-23 as previously predicted. Adjust our prediction by guessing that spring transitions will be between 24 and 30 March, which matches recent practice since 2016. (Thanks to Even Scharning and Tim Parenti.) Metlakatla ended its observance of Pacific standard time, rejoining Alaska Time, on 2019-01-20 at 02:00. (Thanks to Ryan Stanley and Tim Parenti.) Changes to past timestamps Israel observed DST in 1980 (08-02/09-13) and 1984 (05-05/08-25). (Thanks to Alois Treindl and Isaac Starkman.) Changes to time zone abbreviations Etc/UCT is now a backward-compatibility link to Etc/UTC, instead of being a separate zone that generates the abbreviation "UCT", which nowadays is typically a typo. (Problem reported by Isiah Meadows.) Changes to code zic now has an -r option to limit the time range of output data. For example, 'zic -r @1000000000' limits the output data to timestamps starting 1000000000 seconds after the Epoch. This helps shrink output size and can be useful for applications not needing the full timestamp history, such as TZDIST truncation; see Internet RFC 8536 section 5.1. (Inspired by a feature request from Christopher Wong, helped along by bug reports from Wong and from Tim Parenti.) Changes to documentation Mention Internet RFC 8536 (February 2019), which documents TZif. tz-link.html now cites tzdata-meta <https://tzdata-meta.timtimeonline.com/>. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2019a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2019a.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2019a.tar.lz As usual, links to the latest release files are here: 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 14c73382cf95efd5f189379427b7b37ca22b9eff dated 2019-03-25 22:01:33 -0700 and tagged '2019a' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 7cc76ce6be4a67c3e1b2222cb632d2de9dabb76899793a938f87a1d4bb20e462cabdae9e3b986aaabaa400795370510095d236dbad5aff4c192d0887f0ecedf5 tzcode2019a.tar.gz d8eb5b2b68abee08bd2b0d2134bce85b5c0aee85168e9697a607604ed5be7d1539ac60fda9b37e0c9c793ef6251978bc250563a0af59497fde775499964bb5aa tzdata2019a.tar.gz 5971d53ceb8cd9e0723d0694c2dca5a3781b9c84bdfef2eb324e9f94fb0b25da263cf59b5429bc77e12e549130aab8c8b1755c34d62bf672c184210c629328f2 tzdb-2019a.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlyZs50ACgkQ7ZfpDmKq fjRR5xAAqsWv2T1beL9TnJ2JaadySGOZiJg3M3RqW8Vm4Dd0ye8Dz8t+YtDtBX1/ 8+xGdlS7LWjwK2EQC6xWhp0EiqpiFjMU1FRGFeAlAOOv8SE0dPRfP9vIeKzCNXKp UwtSrzM5JUX6/iza9UUTlzpwHaEM/gVIfP+sLgT15RJiB84teHro/rpcfOvNRyj1 bteknySCtbPcETe9VW3qH2YgMRtNQgkt/DcJgCvY2qWLsnicWRH9Ec6NhqYLFpuv QwvqC0Odaehrytu+DNhi1wuxt90YHgGHMgIZXtG+kO8eJy2aWFP9zQJ80wVvNqat Xgl6T5AU5ZIdBEQkMnk0EhqFlKYFX/81hEWT0gsMBCzteVFhhQQPPyptUwtL5U17 MX1oVaZbiTbTCqjAjHAJbfW61Fbu9H0wzZhoRLvDqaFfOxQ1HEMh2Ioh+KlJ0nLw +l5dLNed7D/kjRE0ja7Jj+ocCl4Hf1DTQknfqtk1USGctWLZ3WfKHk6jCS0vid7g IrN6POYhZ6kg4NLF1G2pD7tTiog37Kvd/c3FHC76cqbbA5wkye+L/A73xmy0qOlv tp14wxd99ETI5loWgMb5SgRzzeEjNbTrG5AuAOX0qK4Fz3cEdK9/PYYJDSOkueJJ 0DpP9Eo3Kmhhk7E4PheygmX+Vk+Ntutu7jx8r6EFNck/erZrnJs= =kJqF -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlyZs50ACgkQ7ZfpDmKq fjTPrg/9HBD7RK0/e2NQc/IEg0BeZPOG/SsWOo78lQ23UVwqXdXqQz9LJXl9gTqM ENe8Ecknctk6fmfriAYnSydXx/MwWDbze5nmi4p7wzlogL/ctPILJvQbc/T62fDK NpGNwDlaUX/ht7cRG9VO+oun3Zc7efGHJB9UpZDDVZGtq6VT5+AZIryM12XvHfcR g0P+0pZfZu9LI4H0K/JUmNnRRXLoq6/5OsV6+hFlTzS7quVfUu+Vb+gsoUVejXld 77hNvqdAaRBwVW69hjdUL2WJXymQtP/1ZoeOVHskti0HQBFRJsDc4Fhs3Pe5MUWd PXVanz/C0sHhHbTLfHs4wVQvNg4g4OP5nl9DyF+KG2SqfuqWOzfbEs5bc8dGqFCk HLdj7Nd4eQA8x/Xl6OSukE1yzUR8Xkb9GFgTmpHlP7uq/TH2URJdd/ZXhSgPv+u6 bM9ghH9eirnVDPxWxsj0bwkZYHY6eJC8pgLPpXsxBY0ktJD/hqS1IMXOAyPRj9fO uRt7QLcsJW+wx6Q7ggsgTs7cxnq/Pk55S0lcp63mAu960+2XuBy8ffFJp4J2OwqS U6nBCtAZ6ZONKvsoQ4UpIcNfkYEiM3A4XNjn/rL2Jtb0cDA8e0j66/k1vcOc9p6u KQSXvSrhoqGTqhKy03XuQJ7LYhSgtD790sxFOXWS59cs/WcLO+M= =g5BY -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlyZs54ACgkQ7ZfpDmKq fjQOExAAj3bXlkhyxx2pTIt2sEiE687kRa3VOKYeLnSLyWfOSAKFsrEXiPHNGPJ9 Xn9PjUZa7cZ+5IiZoHYr37GbDqs0VdTrnt/SId+fxhv14DoCJsQT2yuji7aWrBnp LOIscrsvvciNk6035bWJjuLZRyDYqm8MKBSBCgKuuFOCCy/mFprW42nzM/L9QK3p vhnDrKnXlDF4pu3J6w5MThZyTbJOD4zqMIMgdfuBLlOjks5smLTVmTN0QTuZyVca Cr8T4+BTGnmMfGkgGCG1/33DZg58q/Q7l8hqKkaK6znErPFk5cCE7S/Ty32hD91o x6YUQNxEYai9nhgirr55mYc4/X4BjiqRA/Dzw+Nbum0AC1OtNijqHmy1frZRyky5 jwFaMWEIxSTKKd/FexqBUuw6KpciEtVM46VCa73VQN5/3RqaXiA7f36zi7HB3flC jdKqmse2yMGASavYRMVvY/LT8TC+DPZ2+8hbHproLmz5y7tFgXh+eSqj+SwKIw/5 SADRjIaTCQS6KUm5syUc0Nu4Oi9fEifdnOJ6WM0/yj2ix40D1dXwRSuja2Tf1sM1 DkO05GH0G3+0zjKMROMKwXM8PahXvePcRuaKROO9Nx+mBZ3MvYpaOORecQ7flJKb GINC0cwwbDiLF/k+ESruOlCZ57D6ChUABptKwiPOrmNcqDRYiOo= =6VXD -----END PGP SIGNATURE----- PS. If your tzdata parser does not yet support negative DST offsets, this particular release's data entries are also available in a rearguard-format tarball and signature that does not contain such offsets. This is intended to be a temporary transition aid for these parsers. The URLs are: https://web.cs.ucla.edu/~eggert/tz/release/2019a/tzdata2019a-rearguard.tar.… https://web.cs.ucla.edu/~eggert/tz/release/2019a/tzdata2019a-rearguard.tar.… with the following SHA-512 and GPG checksums: 1ebca45c43aaed76fcb8894a5e8321975cc74a272a9e7b83b2f4ca9d5c2c0b4a4de276bd019d95468ce7e6b88d8afdab70b17580071b8a54cdf2218c2bb8a069 tzdata2019a-rearguard.tar.gz -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlyZs50ACgkQ7ZfpDmKq fjTGig//QSof18SghwQoHqUCxUEKhblFyV7+mSzEMdF3J+eSCpt+SsoN75NaLHYm GoBlJkmYFOxnyWjbzvn9dcr9/vHXu0D5P8Bd2NvVEULRSJ/Kb+uOsXsic38Z5Uz6 hJ/9Il/7mAYF23diYLtOuuVoeuKrHhmS/9jzACu6jXMwaXXWfMpbm3NGVLgXNIPe QD93PUq/aQ87OwmysZBhXui0PR5Pakg3nWSj7jTtAKhbRFOZdN5g9OxneYvaCmmC K2s+mvXRnQiImNnTvXavAEWw3Gz3MP7972JYdmd6gm9Q+lfNf1ykbM8Z4KO+rDMk YTfQCrNpAtmGP3TqNgFtzBouQAmjoQ8+Lyh7jjGArxZEpZVle+7zSGOoB/US4otz hrHrzg/6rNmYWL5Xvg8rhgtG0fp8uZABhA0s9gV2Qz8TRnArTUoLoYWiEGpfQ7Vf uHU1947DSMebshg4BYBmLvcEr2/KH7TMholRMllTv5soM7sX3bariejI8u5dcDhk wRyiBZhLJbFd+of6kNeo5jPm9caDOWrp3vq2xryyiN1M9s3gu8BfrBcSI2tE2l6F uOMAuaeNOfuoLuAYghgkXWM1DvZo81ePQXAVW9CIsg+aT1wcCRk0TPRn+OiPjbKQ YS4ULentOrEnxdKfFC1XIJ4JQZuDjhyW2vlkboWhc1zT5a83erc= =bFDj -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Proposed Change to Maine's Time Zone *No Current Action Needed* Update
by C Yohman March 24, 2019

March 24, 2019

LD 144 http://legislature.maine.gov/legis/bills/display_ps.asp?paper=HP0126&PID=un… Ought Not to Proceed LD 885 http://legislature.maine.gov/legis/bills/display_ps.asp?paper=HP0659&PID=un… Tabled I would expect no changes to Maine's timezone in the meantime.

1 0