←back to thread

Debian 13, Postgres, and the US/* time zones

(rachelbythebay.com)
283 points move-on-by | 1 comments | 12 Sep 25 02:33 UTC | HN request time: 0.212s | source
Show context
ggm ◴[12 Sep 25 02:48 UTC] No.45218201[source]▶
Is there a problem with ISO3166 denoted information in general or is there a specific US issue here? I would think ISO code denoted tzdata was a public good in some sense.
replies(3): >>45218844 #>>45219199 #>>45219576 #
masklinn ◴[12 Sep 25 06:27 UTC] No.45219199[source]▶
All the legacy time zones were moved out of the default zoneinfo install. It’s not a us-specific issue but the legacy US/ timezones remain in widespread use, and they stop working on Debian 13 ootb (possibly Ubuntu noble as well?).
replies(2): >>45219462 #>>45219568 #
pixelesque ◴[12 Sep 25 07:23 UTC] No.45219568[source]▶
Does anyone know why they are still in widespread use?

Config defaults somewhere still using them? Man page examples? Tutorials using them? Or just force of habit?

replies(5): >>45219671 #>>45220170 #>>45220261 #>>45220493 #>>45220793 #
1. zahlman ◴[12 Sep 25 09:01 UTC] No.45220170[source]▶
> Does anyone know why they are still in widespread use?

Because of a lack of things compelling people to change them until it causes a breakage. And then when it does cause a breakage, most people would rather move heaven and earth to complain, research workarounds, etc. rather than just change it. (Institutional structures can also make "just" changing it far harder than that should be.)