Most active commenters

    ←back to thread

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

    (rachelbythebay.com)
    283 points move-on-by | 11 comments | 12 Sep 25 02:33 UTC | HN request time: 1.239s | source | bottom
    1. JdeBP ◴[12 Sep 25 08:19 UTC] No.45219936[source]▶
    This does not trace things back far enough. The root is where IANA has long since segregated out a set of timezone file names into a "backward" collection:

    * https://data.iana.org/time-zones/tzdb/backward

    If one traces references, one finds this connected bug on Launchpad. Amusingly to anyone who has ever seen these sweeping timezone database changes over the years, Launchpad marked it as "This bug affects 1 person.".

    * https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/200807...

    The rules for the "backward" file are here:

    * https://data.iana.org/time-zones/theory.html#naming

    All of the US/* timezone names, such as US/Pacific here, have been backwards compatibility measures in place for the whole of the 21st century and some of the late 20th. The Olson database in the 1980s (mod.sources v08i085, comp.sources.unix v14i030) used these names. But the naming scheme changed somewhen in the 1990s to a continent/city and ocean/city form and backwards compatibility with the old names has been preserved ever since by the "backward" file.

    * https://groups.google.com/g/comp.unix.solaris/c/ON_MPZxVdv0/...

    Debian has moved into a non-depended-upon package a backwards compatibility measure that is as old as Debian itself.

    replies(2): >>45219985 #>>45220289 #
    2. AnssiH ◴[12 Sep 25 08:28 UTC] No.45219985[source]▶
    > Launchpad marked it as "This bug affects 1 person.".

    That just means no one has clicked "affects me too" button yet (after logging in).

    3. ForHackernews ◴[12 Sep 25 09:21 UTC] No.45220289[source]▶
    It's good Debian is making this change now to be prepared when the legacy United States are downed at the end of 2052.
    replies(2): >>45221524 #>>45223094 #
    4. tempodox ◴[12 Sep 25 12:45 UTC] No.45221524[source]▶
    I can’t tell whether you’re joking. Seems like a distinct possibility now.
    replies(1): >>45222197 #
    5. maybewhenthesun ◴[12 Sep 25 13:54 UTC] No.45222197{3}[source]▶
    2052? I hope the last 2 digits aren't swapped...
    replies(1): >>45224059 #
    6. phantom784 ◴[12 Sep 25 15:21 UTC] No.45223094[source]▶
    That is the logic for using city-based timezone names rather than countries. Country borders change but cities tend to be more stable.
    replies(3): >>45224300 #>>45224805 #>>45225616 #
    7. boredumb ◴[12 Sep 25 16:48 UTC] No.45224059{4}[source]▶
    keep that energy when you and your family are starving in the dark with no running water.
    8. dripton ◴[12 Sep 25 17:11 UTC] No.45224300{3}[source]▶
    Istanbul's not Constantinople.
    replies(1): >>45224678 #
    9. dsr_ ◴[12 Sep 25 17:49 UTC] No.45224678{4}[source]▶
    You mean Byzantium? Nova Roma?

    https://en.wikipedia.org/wiki/Names_of_Istanbul

    10. charcircuit ◴[12 Sep 25 18:03 UTC] No.45224805{3}[source]▶
    The laws of the country can affect what timezone is used.
    11. fph ◴[12 Sep 25 19:17 UTC] No.45225616{3}[source]▶
    Someone must have complained about `China/Hong Kong` to cause this change.