- tz - lists.iana.org

Re: [tz] Time zone of Mongolia
by Phake Nick Sept. 1, 2023

Sept. 1, 2023

Dear Delgermaa, Specifically when it come to Mongolia, in addition to what have been mentioned by others about start time of DST, can you help confirm status of standard time that have been used across the country now and in the past? Since DST would have to depend on correct standard time information, and despite crrently tz database have tried to use different information sources to figure out what time have been used by different parts of Mongolia, some of the information are in conflicts. Is it correct that currently western part of Mongolia use UTC+7 while rest of the country use UTC+8? And is it correct that Eastern part of the country used UTC+9 in the past but switched to UTC+8 sometimes before year 2008? If this is the case do you know when this happened? Also do you know what's the background of some information from year 2005 claiming that Sükhbaatar Aimag used UTC+8.5 that year? And is there anywhere official where these information can be sourced? Best Regards, Nick. On 2023-09-01 Fri 00:14 UTC, delgermaa.g via tz <tz(a)iana.org> wrote: > Dear sir, madam > > I am contacting from Ministry of digital development and communications > from Mongolia. First let me introduce myself, My name is Delgermaa. I am > officer at Ministry of digital development and communications in Mongolia. > Our country is studying of switching to regular summer time starting from > 2024. In this regard, how many months in advance should your organization > be notified of the time zone change? > > I hope you will soon reply > > Thank you for your cooperation > > Хүндэтгэсэн, > Г.Дэлгэрмаа > ------------------------- > Цахим хөгжил, харилцаа холбооны яамны > > Цахим хөгжлийн бодлогын хэрэгжилтийг > зохицуулах газрын > Нийтийн мэдээллийн дэд бүтцийн хэлтсийн > мэргэжилтэн > Утас: 51-265112, 976-99123321 > www.mddc.gov.mn > > >

1 0

From ministry of digital development and communications
by delgermaa.g Sept. 1, 2023

Sept. 1, 2023

Dear sir, madam I am contacting from Ministry of digital development and communications from Mongolia. First let me introduce myself, My name is Delgermaa. I am officer at Ministry of digital development and communications in Mongolia. Our country is studying of switching to regular summer time starting from 2024. In this regard, how many months in advance should your organization be notified of the time zone change? I hope you will soon reply Thank you for your cooperation Хүндэтгэсэн, Г.Дэлгэрмаа ------------------------- Цахим хөгжил, харилцаа холбооны яамны Цахим хөгжлийн бодлогын хэрэгжилтийг зохицуулах газрын Нийтийн мэдээллийн дэд бүтцийн хэлтсийн мэргэжилтэн Утас: 51-265112, 976-99123321 www.mddc.gov.mn

3 2

DST Chile 2023(tzdb)
by Rodrigo Reyes Aug. 24, 2023

Aug. 24, 2023

Hello, Raising flag about DST change for Chile 2023, official date is 1st September weekend(09/03/2023). But last year the change was delayed to 2nd September weekend(09/11/2023), https://data.iana.org/time-zones/tzdb/NEWS Release 2022b - 2022-08-10 15:38:32 -0700 Briefly: Chile's DST is delayed by a week in September 2022. Iran no longer observes DST after 2022. Rename Europe/Kiev to Europe/Kyiv. New zic -R option Vanguard form now uses %z. Finish moving duplicate-since-1970 zones to 'backzone'. New build option PACKRATLIST New tailored_tarballs target, replacing rearguard_tarballs Do you know what's the way to obtain a confirmation?, and if we have a confirmation about to use the "official date" do you have some SLA to provide a new TZDB to apply this change?. Thks a lot for your answer!!!. Regards Rodrigo Reyes Technologies Manager Phone Number (+56978971585) [cid:image001.png@01D9D52B.766327A0] This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service>

4 4

System time jumps
by Arthur David Olson Aug. 17, 2023

Aug. 17, 2023

"Windows feature that resets system clocks based on random data is wreaking havoc." https://arstechnica.com/security/2023/08/windows-feature-that-resets-system… @dashdashado

2 1

Fwd: Bulletin C number 66
by Tim Parenti Aug. 14, 2023

Aug. 14, 2023

No leap second 2023-12-31, per below. See attached patch. -- Tim Parenti ---------- Forwarded message --------- From: IERS EOP Product Center <iers.eoppc(a)obspm.fr> Date: Tue, 4 Jul 2023 at 08:06 Subject: Bulletin C number 66 To: <bulc.iers(a)obspm.fr> INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE SERVICE DE LA ROTATION TERRESTRE DE L'IERS OBSERVATOIRE DE PARIS 61, Av. de l'Observatoire 75014 PARIS (France) Tel. : +33 1 40 51 23 35 e-mail : services.iers(a)obspm.fr http://hpiers.obspm.fr/eop-pc Paris, 04 July 2023 Bulletin C 66 To authorities responsible for the measurement and distribution of time INFORMATION ON UTC - TAI NO leap second will be introduced at the end of December 2023. The difference between Coordinated Universal Time UTC and the International Atomic Time TAI is : from 2017 January 1, 0h UTC, until further notice : UTC-TAI = -37 s Leap seconds can be introduced in UTC at the end of the months of December or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every six months, either to announce a time step in UTC, or to confirm that there will be no time step at the next possible date. Christian BIZOUARD Director Earth Orientation Center of IERS Observatoire de Paris, France

1 0

What is the "Factory" Zone used for?
by Justin Grant Aug. 10, 2023

Aug. 10, 2023

There's a Zone called "Factory". What is its purpose, and how is it used? Thanks! Justin Grant (I work with ECMA TC39 to make time zones work well in JavaScript)

3 2

[PROPOSED] Document Paraguay’s recently-passed Law No. 7115
by Paul Eggert July 28, 2023

July 28, 2023

This law doesn’t change TZDB’s data; it merely codifies into law recent common practice as implemented by presidential decrees. * southamerica: Add comments re Law No. 7115. --- southamerica | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/southamerica b/southamerica index e55c5f08..9430b185 100644 --- a/southamerica +++ b/southamerica @@ -1697,6 +1697,12 @@ Rule Para 2010 2012 - Apr Sun>=8 0:00 0 - # From Carlos Raúl Perasso (2014-02-28): # Decree 1264 can be found at: # http://www.presidencia.gov.py/archivos/documentos/DECRETO1264_ey9r8zai.pdf +# +# From Paul Eggert (2023-07-26): +# Transition dates are now set by Law No. 7115, not by presidential decree. +# https://www.abc.com.py/politica/2023/07/12/promulgacion-el-cambio-de-hora-s… +# Although Google indexed this government URL, it did not work for me: +# https://www.bacn.gov.py/leyes-paraguayas/11831/ley-n-7115-establece-el-hora… Rule Para 2013 max - Mar Sun>=22 0:00 0 - # Zone NAME STDOFF RULES FORMAT [UNTIL] -- 2.39.2

3 4

[PATCH] Improve touches when making tarballs
by Paul Eggert July 27, 2023

July 27, 2023

* Makefile (SET_TIMESTAMP_N, set-timestamps.out) (tzdata$(VERSION)-rearguard.tar.gz, tzdata$(VERSION)-tailored.tar.gz): Do not use ‘touch -c’, as POSIX says it exits with status 0 even when it fails. Instead, check in the shell that a file exists before touching it. Chatter with “+ touch ...” before touching, to aid debugging of failures. --- Makefile | 23 +++++++++++++++-------- 1 file changed, 15 insertions(+), 8 deletions(-) diff --git a/Makefile b/Makefile index d891f837..68c644d8 100644 --- a/Makefile +++ b/Makefile @@ -958,12 +958,18 @@ $(MANTXTS): workman.sh # plus N if GNU ls and touch are available. SET_TIMESTAMP_N = sh -c '\ n=$$0 dest=$$1; shift; \ - touch -cmr `ls -t "$$@" | sed 1q` "$$dest" && \ + <"$$dest" && \ if test $$n != 0 && \ - lsout=`ls -n --time-style="+%s" "$$dest" 2>/dev/null`; then \ + lsout=`ls -nt --time-style="+%s" "$$@" 2>/dev/null`; then \ set x $$lsout && \ - touch -cmd @`expr $$7 + $$n` "$$dest"; \ - else :; fi' + timestamp=`expr $$7 + $$n` && \ + echo "+ touch -md @$$timestamp $$dest" && \ + touch -md @$$timestamp "$$dest"; \ + else \ + newest=`ls -t "$$@" | sed 1q` && \ + echo "+ touch -mr $$newest $$dest" && \ + touch -mr "$$newest" "$$dest"; \ + fi' # If DEST depends on A B C ... in this Makefile, callers should use # $(SET_TIMESTAMP_DEP) DEST A B C ..., for the benefit of any # downstream 'make' that considers equal timestamps to be out of date. @@ -992,7 +998,8 @@ set-timestamps.out: $(EIGHT_YARDS) --format='tformat:%cd' \ --date='format:%Y-%m-%dT%H:%M:%SZ' \ $$file` && \ - touch -cmd $$time $$file; \ + echo "+ touch -md $$time $$file" && \ + touch -md $$time $$file; \ else \ echo >&2 "$$file: warning: does not match repository"; \ fi || exit; \ @@ -1148,7 +1155,7 @@ tzdata$(VERSION)-rearguard.tar.gz: rearguard.zi set-timestamps.out sed '1s/$$/-rearguard/' <version >$@.dir/version : The dummy pacificnew pacifies TZUpdater 2.3.1 and earlier. $(CREATE_EMPTY) $@.dir/pacificnew - touch -cmr version $@.dir/version + touch -mr version $@.dir/version LC_ALL=C && export LC_ALL && \ (cd $@.dir && \ tar $(TARFLAGS) -cf - \ @@ -1172,7 +1179,7 @@ tzdata$(VERSION)-tailored.tar.gz: set-timestamps.out `test $(DATAFORM) = vanguard || echo pacificnew` (grep '^#' tzdata.zi && echo && cat $(DATAFORM).zi) \ >$@.dir/etcetera - touch -cmr tzdata.zi $@.dir/etcetera + touch -mr tzdata.zi $@.dir/etcetera sed -n \ -e '/^# *version *$.*$/h' \ -e '/^# *ddeps */H' \ @@ -1183,7 +1190,7 @@ tzdata$(VERSION)-tailored.tar.gz: set-timestamps.out -e 's/ /-/g' \ -e 'p' \ <tzdata.zi >$@.dir/version - touch -cmr version $@.dir/version + touch -mr version $@.dir/version links= && \ for file in $(TZDATA_DIST); do \ test -f $@.dir/$$file || links="$$links $$file"; \ -- 2.39.2

1 0

[PATCH] Port better to POSIX 'touch'
by Paul Eggert July 26, 2023

July 26, 2023

* Makefile (set-timestamps.out): Use POSIX syntax for 'touch -d' rather than relying on a GNU extension. --- Makefile | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 17e73891..d891f837 100644 --- a/Makefile +++ b/Makefile @@ -988,8 +988,11 @@ set-timestamps.out: $(EIGHT_YARDS) rm -f test.out && \ for file in $$files; do \ if git diff --quiet $$file; then \ - time=`git log -1 --format='tformat:%ct' $$file` && \ - touch -cmd @$$time $$file; \ + time=`TZ=UTC0 git log -1 \ + --format='tformat:%cd' \ + --date='format:%Y-%m-%dT%H:%M:%SZ' \ + $$file` && \ + touch -cmd $$time $$file; \ else \ echo >&2 "$$file: warning: does not match repository"; \ fi || exit; \ -- 2.39.2

2 3

Problem with some timezone data from 2023 w/ Java SimpleTimeZone
by Andreas Haumer July 19, 2023

July 19, 2023

Hi! [I hope this is the right place to report this problem. I reported it on OpenSUSE bugzilla, but was asked to report it upstrem, too. See https://bugzilla.opensuse.org/show_bug.cgi?id=1213470 for my original bugreport] A few days ago I found that with the 2023c timezone database as installed on OpenSUSE LEAP or RedHat Fedora there are two timezones which produce an IllegalArgumentException in the SimpleTimeZone Java class (from OpenJDK 17): "Asia/Gaza" and "Asia/Hebron" The following small Java programm demonstrates the problem: andreas@localhost:~> cat TimeZoneTest.java import java.util.TimeZone; public class TimeZoneTest { public static void main(String[] argv) { for (final String id : TimeZone.getAvailableIDs()) try { TimeZone.getTimeZone(id).toString(); } catch (Exception ex) { System.out.println("TimeZone " + id + " failed: " + ex); } } } Running this programm with a current Java timezone database installed gives the following output: andreas@localhost:~> java TimeZoneTest.java TimeZone Asia/Gaza failed: java.lang.IllegalArgumentException: Illegal daylight saving value: 0 TimeZone Asia/Hebron failed: java.lang.IllegalArgumentException: Illegal daylight saving value: 0 andreas@localhost:~> rpm -q timezone-java timezone-java-2023c-150000.75.23.1.noarch andreas@localhost:~> java -version openjdk version "17.0.7" 2023-04-18 OpenJDK Runtime Environment (build 17.0.7+0-suse-150400.3.24.1-x8664) OpenJDK 64-Bit Server VM (build 17.0.7+0-suse-150400.3.24.1-x8664, mixed mode, sharing) This is with OpenSUSE LEAP 15.4 and 15.5 I also see the same exceptions with Fedora 37, which also uses a separate 2023c timezone database for Java. Debian based systems (like Debian 11, Debian 12 or Ubuntu 22) run the above program without error. They use the internal tzdb which comes with OpenJDK. It looks like the timezone database contains a 0 for the dstSavings property. The constructor for the SimpleTimeZone Java class wants this calue to be > 0 and throws an IllegalArgumentException if it isn't: public SimpleTimeZone(int rawOffset, String ID, int startMonth, int startDay, int startDayOfWeek, int startTime, int startTimeMode, int endMonth, int endDay, int endDayOfWeek, int endTime, int endTimeMode, int dstSavings) { setID(ID); this.rawOffset = rawOffset; this.startMonth = startMonth; this.startDay = startDay; this.startDayOfWeek = startDayOfWeek; this.startTime = startTime; this.startTimeMode = startTimeMode; this.endMonth = endMonth; this.endDay = endDay; this.endDayOfWeek = endDayOfWeek; this.endTime = endTime; this.endTimeMode = endTimeMode; this.dstSavings = dstSavings; // this.useDaylight is set by decodeRules decodeRules(); if (dstSavings <= 0) { throw new IllegalArgumentException("Illegal daylight saving value: " + dstSavings); } } So: is this a problem with the timezone database or rather a problem with the implementation of the Java SimpleTimeZone class? Thanks! - andreas -- Andreas Haumer *x Software + Systeme | mailto:andreas@xss.co.at Karmarschgasse 51/2/20 | https://www.xss.co.at/ A-1100 Vienna, Austria | Tel: +43-1-6060114-0

3 2