Hello, I just ran into an odd issue where we updated an Almalinux 9 server (with EPEL enabled) and it picked up tzdata 2026e. In this particular case a change that was put into 2026c caused a php web application to have some weird date issues because of timezone changes in tzdata that weren't included in libicu. When I tested libicu, it says its using 2023c. If I go and download new files from https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew/2026e/44/le
And put them somewhere like /usr/share/icu-tzdata/2026e and set the env var ICU_TIMEZONE_FILES_DIR to point to that directory then it fixes the issue. I realize that this isn't RedHat support, but I figured people here would potentially know why libicu is using such old timezone files and doesn't seem to be updated. Is the way I'm dealing with it the expected way to update it? Should I grab the fedora version and rebuild for Almalinux 9 or something? Seems odd this would lag behind. Anyone know why it lags so much and doesn't get updated? I imagine it has to do with the other parts of the library, but I seem to remember there being a libicu-data or something like that at some point. Any pointers would be appreciated but if this is wildly out of scope for the list, no worries. Sincerely, -- Nathanael -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
