1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • Re: tzdata-legacy [was: Re: systemd and timezone]

    From Nate Bargmann@21:1/5 to Max Nikulin on Sat Jan 6 10:20:01 2024
    * On 2024 06 Jan 01:00 -0600, Max Nikulin wrote:
    US/Eastern & Co has been moved to tzdata-legacy as well. Currently used identifiers are based on cities: America/New_York.

    Ugghhh!

    I guess I'll be going to the legacy package then until
    $WHOEVER_IS_IN_CHARGE issues a decree that it too shall be eliminated.
    I really don't get the fascination with some city hundreds of miles
    distant defining the time zone. Why Chicago for US/Central? There are
    any number of cities in US/Central that could be referenced, but no,
    pick the most notorious one--rolls eyes.

    I could even accept America/Central without complaint. Yeah, US is a
    directory and Central is a symlink to ../America/Chicago that could be
    manually added to a system if need be.

    Ambles off shaking fist at a cloud...

    - Nate

    --
    "The optimist proclaims that we live in the best of all
    possible worlds. The pessimist fears this is true."
    Web: https://www.n0nb.us
    Projects: https://github.com/N0NB
    GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819


    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCZZkWEQAKCRD7LFEw1VqI GbGuAJ9+79mzBrGdoF0JPD6an4am0e/wDwCfb29XkFpXUzYtxOMQnJmbrtQNwgw=
    =9YsB
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From gene heskett@21:1/5 to Nate Bargmann on Sat Jan 6 13:10:01 2024
    On 1/6/24 04:15, Nate Bargmann wrote:
    * On 2024 06 Jan 01:00 -0600, Max Nikulin wrote:
    US/Eastern & Co has been moved to tzdata-legacy as well. Currently used
    identifiers are based on cities: America/New_York.

    Ugghhh!

    I guess I'll be going to the legacy package then until
    $WHOEVER_IS_IN_CHARGE issues a decree that it too shall be eliminated.
    I really don't get the fascination with some city hundreds of miles
    distant defining the time zone. Why Chicago for US/Central? There are
    any number of cities in US/Central that could be referenced, but no,
    pick the most notorious one--rolls eyes.

    I could even accept America/Central without complaint. Yeah, US is a directory and Central is a symlink to ../America/Chicago that could be manually added to a system if need be.

    Ambles off shaking fist at a cloud...
    You got company on that trail.

    - Nate


    Cheers, Gene Heskett.
    --
    "There are four boxes to be used in defense of liberty:
    soap, ballot, jury, and ammo. Please use in that order."
    -Ed Howdershelt (Author, 1940)
    If we desire respect for the law, we must first make the law respectable.
    - Louis D. Brandeis

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Greg Wooledge@21:1/5 to Nate Bargmann on Sat Jan 6 16:10:01 2024
    On Sat, Jan 06, 2024 at 02:57:53AM -0600, Nate Bargmann wrote:
    I really don't get the fascination with some city hundreds of miles
    distant defining the time zone. Why Chicago for US/Central? There are
    any number of cities in US/Central that could be referenced, but no,
    pick the most notorious one--rolls eyes.

    <https://data.iana.org/time-zones/theory.html> is the only page I've
    ever found that EXPLAINS things properly. I strongly recommend it.

    Among other things, it says:

    * Use the most populous among locations in a region, e.g., prefer
    Asia/Shanghai to Asia/Beijing. Among locations with similar populations,
    pick the best-known location, e.g., prefer Europe/Rome to Europe/Milan.

    So, it's based on population and fame.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Wright@21:1/5 to Nate Bargmann on Sun Jan 7 18:30:01 2024
    On Sat 06 Jan 2024 at 02:57:53 (-0600), Nate Bargmann wrote:
    * On 2024 06 Jan 01:00 -0600, Max Nikulin wrote:
    US/Eastern & Co has been moved to tzdata-legacy as well. Currently used identifiers are based on cities: America/New_York.

    Ugghhh!

    I guess I'll be going to the legacy package then until
    $WHOEVER_IS_IN_CHARGE issues a decree that it too shall be eliminated.
    I really don't get the fascination with some city hundreds of miles
    distant defining the time zone.

    Until fairly recently there wasn't a $WHOEVER_IS_IN_CHARGE to issue
    the decree as Congress now does. A lot of the rules were made locally.

    Why Chicago for US/Central? There are
    any number of cities in US/Central that could be referenced, but no,
    pick the most notorious one--rolls eyes.

    I don't know what your problem is with Chicago: it's merely the
    largest city in the area covered by the timezone.

    I could even accept America/Central without complaint. Yeah, US is a directory and Central is a symlink to ../America/Chicago that could be manually added to a system if need be.

    States still have the right to decide whether to observe DST, just
    so long as any clock changes occur at the same time as everybody
    else. So it's conceivable that Texas could, for example, decide
    changing clocks is a waste of effort, and stay on one or the other
    all year. In which case, it's a simple matter to cater for that
    with the addition of an America/Houston timezone.

    Impossible to do that with America/Central; I think it's long overdue
    to recognise these old names as a legacy of earlier attempts to
    specify time zones. Historically, some of them (like Eastern) don't
    work anyway. Also it's doubly unfortunate, for non-Americans, that
    there's a region of the world called Central America.

    Ambles off shaking fist at a cloud...

    Cheers,
    David.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)