Hi Stephanie,

On Apr 11, 2019, at 3:25 PM, Gardner, Stephanie (Enel X) <stephanie.gardner@enel.com> wrote: I’ve just joined this mailing list and I don’t fully understand how this works, but I’m writing because have a dilemma. My understanding is that Chile Continental time changed back to standard time on April 6. See https://www.horaoficial.cl/aviso/informacion.html <https://www.horaoficial.cl/aviso/informacion.html> which states: “Dispone fecha cambio huso horario para el 6 de abril de 2019, de acuerdo a lo siguiente: a. Chile Continental (desde Región de Arica y Parinacota hasta Aysén), a las 24:00 hora local, pasará a huso horario UTC-4, y deberá atrasar los relojes en una hora.” However, this is not reflected in the 2019-03-25 release. I therefore have an application which is using the incorrect UTC offset as a result. What is the process for getting that change into the database?

That change was added in the TZ 2018f version released 6 months ago and is currently active. https://github.com/eggert/tz/blob/2018f/NEWS#L19-L23 <https://github.com/eggert/tz/blob/2018f/NEWS#L19-L23> You may check if your system has a good TZDB with something like this: $ zdump -v /usr/share/zoneinfo/America/Santiago | grep 2019 /usr/share/zoneinfo/America/Santiago Sun Apr 7 02:59:59 2019 UTC = Sat Apr 6 23:59:59 2019 -03 isdst=1 /usr/share/zoneinfo/America/Santiago Sun Apr 7 03:00:00 2019 UTC = Sat Apr 6 23:00:00 2019 -04 isdst=0 /usr/share/zoneinfo/America/Santiago Sun Sep 8 03:59:59 2019 UTC = Sat Sep 7 23:59:59 2019 -04 isdst=0 /usr/share/zoneinfo/America/Santiago Sun Sep 8 04:00:00 2019 UTC = Sun Sep 8 01:00:00 2019 -03 isdst=1 Aldrin.