Mexico UTC changed

Hi everyone:

A request, if is possible.

In mexico changed the UTC, no more summer time.
Sorry this page is only availabe in spanish.

Is possible to update your servers?

more /etc/ntp/ntpInclude.conf
server prefer

At this momment local time central Mexico is 11:50 am, but acording to is 12:50 pm.

Mon Apr 3 12:52:24 PM CDT 2023

Best Regards.

1 Like

This is likely to be occurring based on the tzdata file which has all the timezone information.

In CU173 the tzdata version is 2022e
In CU174 Testing the tzdata version is 2022g
A patch has been submitted to be merged into the next branch which will probably become CU175. That version is 2023b

Looking through the changes for those versions and others in between the only reference to Mexico is in version 2022g in CU174 Testing.
The changelog says:

 In the Mexican state of Chihuahua, the border strip near the US
 will change to agree with nearby US locations on 2022-11-30.
 The strip's western part, represented by Ciudad Juárez, switches
 from -06 all year to -07/-06 with US DST rules, like El Paso, TX.
 The eastern part, represented by Ojinaga, will observe US DST next
 year, like Presidio, TX.  (Thanks to Heitor David Pinto.)
 A new Zone America/Ciudad_Juarez splits from America/Ojinaga.

I am not sure if this reference is in line with what you have mentioned or not.

Looking in the IANA Time Zone Database discussion mail archives I found the following.

I wanted to inquire about the update to the rules for Mexico as they have
announced they will not be following daylight saving’s time as of this year.

Will this be reflected on the tz database?

Yes, most of these changes were made in version 2022f with follow-ups in 2022g, which was released on 29 November 2022. Note that tz zone IDs may have changed for some regions from prior versions. See the ‘NEWS’ file for more details.

So this means that the changes you mention will be included in CU174 when it is released.


Thanks for the explanation.
Is there a way to update only the tzdata on my IPFire version 2.27 (x86_64) - Core-Update 171 ?
I defined my IPFire server as a time server for my equipments, and since it is not updated the timezone, the time advanced by one hour.
In my IPFire server is marked this option:
Provide time to local network

Best Regards.

On Core Update 171 the tzdata file is even older. It is 2022a

The tzdata source does not need to be compiled in the normal autotools approach so it is possible to update the tzdata on your machine. However you will need to carry out a sequence of steps carefully and then copy the resultant files onto your ipfire machine and place them into the correct locations with the correct ownerships and permissions.

I will look at putting together the steps and actions needed and provide that but I will also need to test it myself on a vm testbed to make sure I have everything correct. So it is unlikely to be available before Wednesday or Thursday as I have to fit it into my activities.


Don’t worry, it’s not something urgent.
Take your time.
Thank you so much

I had a go at trying to define the steps needed to custom build the tzdata package set and install it.

It took longer than expected to define it and test it out to makie sure it does what is expected. It ends up comprising several steps and has risks with it as you have to overwrite system files in IPFire when implementing it.

As Core Update 174 has now been released my recommendation is to upgrade to that version as it has the updated Mexico time zone info and the update will be done automatically.


I understand, I will schedule the system update, thank you very much.