- tz - lists.iana.org

Doubt about releases/updates
by Pablo Sánchez Dec. 1, 2016

Dec. 1, 2016

Greetings, everyone! I have a doubt about the TZ database release or updates, and maybe you can help me to solve it. So, is the database update BEFORE or AFTER a new DST has started? The reason why I need to know it is because we are having issues about calculating some ETAs and presenting the information on reports, because PHP internal database doesn't get updates automatically. So we decided to use an extension that uses IANA's Timezone Database (updated approximatelly 23 times an year). So, we need to know if those updates are released before the daylight saving time starts or if you release it before it starts. Since there are usually political decisions that delays or rushes the DST beginning, I believe those updates comes prior to the actual fact, with a data on wich day begin, so I should not worry on using the extension that updates itself with 24 hours delay, right? So, do you update it before DST comes, or after? -- *Pablo Santiago Sánchez* ZCE ZEND006757 phackwer(a)gmail.com (61) 9843-0883 http://www.sansis.com.br *"Pluralitas non est ponenda sine necessitate"*

6 7

Re: [tz] DST cancelled for Asia/Baku since 17 March 2016
by Ariel Dor Nov. 30, 2016

Nov. 30, 2016

Ahh. Nm. Found it under thread "Azerbaijan canceled daylight saving time" >From March. BR Ariel From: Ariel Dor Sent: Wednesday, November 30, 2016 16:30 To: 'tz(a)iana.org' Subject: DST cancelled for Asia/Baku since 17 March 2016 Hi, I couldn't find a reference for this change from 17/Mar/2016 to be implemented in any tzdata revision. I did see that there was a minor correction for Asia/Baku in 2016e DB (for 1992), but not for the change from 2016 and on. Source https://www.timeanddate.com/news/time/no-dst-azerbaijan.html BR, Ariel

1 0

DST cancelled for Asia/Baku since 17 March 2016
by Ariel Dor Nov. 30, 2016

Nov. 30, 2016

Hi, I couldn't find a reference for this change from 17/Mar/2016 to be implemented in any tzdata revision. I did see that there was a minor correction for Asia/Baku in 2016e DB (for 1992), but not for the change from 2016 and on. Source https://www.timeanddate.com/news/time/no-dst-azerbaijan.html BR, Ariel

1 0

Happy 30th anniversary!
by Arthur David Olson Nov. 29, 2016

Nov. 29, 2016

------------------------------ > ...*Tue Nov 25 00:58:12 UTC 1986* > ... > Now that we've moved from 4.1BSD to 4.3BSD here at elsie, > I've set things up so that mail sent to > seismo!elsie!tz > will go to folks who've expressed an interest in time zone matters. http://mm.icann.org/pipermail/tz/1986-November/008946.html (Note that it was really the 24th local time.) @dashdashado

5 4

[tz-announce] 2016j release of tz code and data available
by Paul Eggert Nov. 24, 2016

Nov. 24, 2016

The 2016j 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: Saratov, Russia moves from +03 to +04 on 2016-12-04. Changes to future time stamps Saratov, Russia switches from +03 to +04 on 2016-12-04 at 02:00. This hives off a new zone Europe/Saratov from Europe/Volgograd. (Thanks to Yuri Konotopov and Stepan Golosunov.) Changes to past time stamps The new zone Asia/Atyrau for Atyraū Region, Kazakhstan, is like Asia/Aqtau except it switched from +04/+05 to +05/+06 in spring 1999, not fall 1994. (Thanks to Stepan Golosunov.) Changes to past time zone abbreviations Asia/Gaza and Asia/Hebron now use "EEST", not "EET", to denote summer time before 1948. The old use of "EET" was a typo. Changes to code zic no longer mishandles file systems that lack hard links, fixing bugs introduced in 2016g. (Problems reported by Tom Lane.) Also, when the destination already contains symbolic links, zic should now work better on systems where the 'link' system call does not follow symbolic links. Changes to documentation and commentary tz-link.htm now documents the relationship between release version numbers and development-repository commit tags. (Suggested by Paul Koning.) The 'Theory' file now documents UT. iso3166.tab now accents "Curaçao", and commentary now mentions the names "Cabo Verde" and "Czechia". (Thanks to Jiří Boháč.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016j.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016j.tar.gz ftp://ftp.iana.org/tz/releases/tzdb-2016j.tar.lz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2016j.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2016j.tar.gz http://www.iana.org/time-zones/repository/releases/tzdb-2016j.tar.lz As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz http://www.iana.org/time-zones/repository/tzdb-latest.tar.lz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzdb-latest.tar.lz 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 eeff212d0f2b94a8c08d7ce2e1ff2278c027936b dated 2016-11-22 23:17:13 -0800 and tagged '2016j' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: cac19dded22ff80cd784641ac239358c28cce535ac1eb60b52b7e51c6e9e5fe5f795ea0252daf32c949dddb9c5b24d7e4456d7869aa2725d49c5af58b564822a tzcode2016j.tar.gz ce0b9958b764479fac7df6b5ba0933fc4c6d815ebccc2537c75c4be105691cd58054704eebfb50ca755d7d48504480d4925ce8836eb499ae4798e3d5503d7e0e tzdata2016j.tar.gz d6ea53bb23ebc1a41ae5ccfa198aec50b8c3836ee8e2dbe8ac0dd77b410884055df87fe9ca926aa8683c6593d2f08ce18b552cf5996d484b2a526c97c67f8419 tzdb-2016j.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYNUONAAoJEO2X6Q5iqn40TiAQAIepGbE9Wt41kBEuehf8LMfh 5qH25z0XDnETV88qofo+Eo8C1eFpueohL6xcHO3L1eCKSt+DJ/kphdvLJaFr+l6Q Kj6HisrJZxQcs8A98M29oydwZ9s9Zsu0igZQlmkhFgh9/NOnsuByoMwZpB0yGGaU zHd2O6hJEQt5IPimEmm7n7awwjzoUctNAjKQISHXApZqpSH14/cYKltwBeR4Up4r F8NmFIbrfstnETUSPPAJsvHntD+98gR7EfwoFYeCmmorDgD65Q5DxqpYuzt67upI Xd3rxD6UUmOmzJwmJ4sO/cEQuxim+kRrnGFOONlavtt1j7FUFRzL762bNpC94byj pMqJNUNy37L+uqucFEORLeqlLvfQA0GVHxcT508aACbht0QMmw5+qcY6rmjEKVqq AA7ZpxX1GhQyk4r7xUth4sMvJjG9ZHa7esv4Uq6lTAVx+IQu1M/kXD3VHfyV0Pb1 LJxz6btSA2PEJmHsFlZtxdp/sinvT2BItN5bBN0JU7lcINalKTBud61dCaa/bt5P 6lHeA6c8R023rHl6ZyHhL6MVME/7DhBKZO+ltbW42Oaul077joyHi8KbuWC4OB4Y 5WqkOI9slIqqwG7DN85uxkgKp4S0puxDDQbmfK4ndkJOSgWhb5ihdvATrvF/CBHZ JKSipGEJ35Sh56Z8qnT1 =L0s/ -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYNUONAAoJEO2X6Q5iqn407TUP/Aib3PFeaTwL3/LnUliah908 GCckZElj1wCc5YwBSfJp3LuYq3OEBQez+EQgUU6TkbEmYhL0mw8le+JU7idI8k3G Qxsy2qKLpUfaLMyXxEsdwWMVIbazK5psEoX2HQna+/DG6oEsDYJ2L9TF4Vf7QVbk rmlqcezdKejOdKmiWz4ksD5VpfzL99ncLmSF+jTof/wuQheSJoGvTyhklVWdNxfj FMANsVXKhKFdajxr71pkehBqQOOGjyQyf4FcIaWDcDbnhKuew/z2JCXUOcymNGU2 bRp5fXawJTV8S7Q865npe5zBjf0exklRUhWp39W+LMwisKjO9sWOrIbgzQPkaqEG VCQq+TA8kDDH1fs4KB7v90DJjoZGLeFDSrfAsaEaFCQV6lwuDAFwFgaZ/tHgSdaC w6NnvD9kFM/1xKAi08kOHhDwyrcD8l12j17BKRS6JSEWo7h3dT7y74Mv6BIAfzLL TgiOperwW8076aVHYXM/7yc4i5pjqDGemJVp0iiZPQhm9zWR6IO3evIZ2zoi2xUw uSBF+p640JgZtVCKCYP3/wFmxdmnk+CcWX+k9LVcwErkXEn+YyREeD6uGsMlAyuB JSb0ea7FhMiazRjXTQLM4wjbBXVVfjfCyVNBB+vF3VBxw1bzxhP/zdhd6kujelH4 I3I4D5bwHXBuxh4ILLjg =05b3 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJYNUONAAoJEO2X6Q5iqn40cWgQAJaQfb8jBiTlYU59s5s/Thh/ OO+pfNAJum2naV4WtCK/gsM/GayFrT3hlPo/ju9/haz05tz1Ejnlj7qxYe1t+HXp xFrm202OhTwn8aGrrITtvrdlQW/dgYyH6otx5wQ9xFe9MR+J9/CViaL7riY1thcg q9z4VbesRG3RSzsqq4NrnmXK2TY+YyV+kg0qf4Nb3O9k4lD5US+ArTZTxz5KGu42 QhllZrTKWN5fe10ME5v8WOsefrkJRhxqrqTbAS5iaNvuCVT40XWjMt8JstLJmdaq PnSGO0s7WoHRxqSpU9yiHA+YviGqPpp+W+CYap53AfzNAXsAT/4x9cqPlbvYgIwt ki6qzFEvK0qfUqTadDbykFBtvri7e8KsZj+zjyd75bdt+MVe4dpkGHhFLoUz6rD6 9trj+sUwLPZFhFAriBes0FduZ8iMi1c08kTzzePSuIkKlaZbhrKs6Focxo1DohB2 8ocCh8uUgkumwfBbcRuQ8HYZJsQLBLgFXYWz9612hNPGjX5EO7Jyyyux9qkEHLF+ upD08YpROhDsZ6XH4OYnAct1O3WL4xO5Vj/EJnyf1bhYglbjZkT4gDth3RnTqGlI tlQU9I7Yf4ZOi9Vv1Nr+TmlYEHZ6rH6u/sLR5MX9O2vRuY2KNh3uqOFxLqL2dOfq 3jbRBjzbPl/oUfEoaTC/ =3EO0 -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Switching to DST in Australia could save Koalas
by Eliot Lear Nov. 23, 2016

Nov. 23, 2016

The problem isn't the Koalas telling time, but humans being on the road at certain times... http://www.latimes.com/science/sciencenow/la-sci-sn-daylight-savings-koalas…

1 0

[PATCH] * NEWS: Add "Briefly:" section.
by Paul Eggert Nov. 23, 2016

Nov. 23, 2016

--- NEWS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/NEWS b/NEWS index 1682709..e018862 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,8 @@ News for the tz database Unreleased, experimental changes + Briefly: Saratov, Russia moves from +03 to +04 on 2016-12-04. + Changes to future time stamps Saratov, Russia switches from +03 to +04 on 2016-12-04 at 02:00. -- 2.7.4

1 0

Re: [tz] Regarding Turkey DST change
by Brian Inglis Nov. 23, 2016

Nov. 23, 2016

On 2016-11-22 13:24, Meno Hochschild wrote: > Am 22.11.2016 um 19:06 schrieb Brian Inglis: >> On 2016-11-22 10:27, Paul Eggert wrote: >>> On 11/22/2016 03:18 AM, Peddi, Radhika (Radhika) wrote: >>>> I am using tzdata along with joda. >>> If the 'date' command works but Joda does not, it must be a Joda >>> problem and not a tzdata problem, so I suggest looking for Joda >>> support. http://www.joda.org/joda-time/ >> Joda runs on Java which has tzupdater problems, so the OP should >> read recent threads and the Oracle page on the Java tzupdater to >> update Java time zones and see correct time, update your JDK/JRE >> to a current release, or submit a TAR to Oracle support. >> Also the OP should note on the Joda page that the Joda API has >> been incorporated into the Java SE 8 java.time class and Joda >> time now deprecates using itself. > Two corrections: > a) Joda Time has nothing to do with tzupdater tool distributed by > Oracle but manages its own independent tz data repository which is > based on analysis of tzdb-sources. > b) The Joda API has NOT been incorporated into Java SE 8 but only > inspired it. Both APIs are really different. > If something with Joda tz-interpretation might be wrong then someone > could check it via Jon Skeets tz-validation-project. But I rather > suspect that there was an outdated Joda-version. The newest version > 2.9.6 is declared to support tzdb-version 2016i. Two problems: - one language product with two sources of time information - no wonder the OP is confused why their time is wrong: perhaps you could post how the OP can correct their Joda time, walk them thru difficulties that may be encountered in http://www.joda.org/joda-time/tz_update.html; - Joda time says the project is finished, and advises migration to Java SE 8 java.time, so it may not be reasonable to expect prompt future releases or tz updates. Like Adobe products, Java has become such a source of security holes and vulnerabilities requiring frequent updates, blocked by various products, that it's safer to uninstall them, eliminate the annoyances and vulnerabilities, and do without what they provide, or use alternatives that don't suffer the same issues. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

1 0

[Russia] Saratov region is moving to UTC+4 at [preliminary] Nov 27, 2016
by Yuri Konotopov Nov. 22, 2016

Nov. 22, 2016

Hello. Today Russian Duma has approved in 1st read (of 3) Law project №1058438-6 that will move Saratov region to UTC+4. Project card: http://asozd2.duma.gov.ru/main.nsf/%28SpravkaNew%29?OpenAgent&RN=1058438-6&… Preliminary date of change is November 27, 2016. As I think new timezone "Europe/Saratov" should be created in tzdata. I will inform you as soon as President will approve Law project. -- Best regards, Yuri Konotopov

4 16

Re: [tz] Regarding Turkey DST change
by Paul Eggert Nov. 22, 2016

Nov. 22, 2016

On 11/22/2016 03:18 AM, Peddi, Radhika (Radhika) wrote: > I am using tzdata along with joda. If the 'date' command works but Joda does not, it must be a Joda problem and not a tzdata problem, so I suggest looking for Joda support. http://www.joda.org/joda-time/

2 1