[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#602563: marked as done (tzdata: Tzdata inconsistencies)

Your message dated Mon, 13 Jan 2025 23:09:06 +0000
with message-id <E1tXTYQ-00HOxe-N0@fasolo.debian.org>
and subject line Bug#602563: fixed in tzdata 2024b-6
has caused the Debian Bug report #602563,
regarding tzdata: Tzdata inconsistencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
602563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602563
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tzdata
Version: 2010o-1
Severity: minor
I understand that in the United States of America, the preferred way to set the time zone is America/Chicago, or America/Los_Angeles. That's all fine, but what about Puerto Rico? As far as as I know, Puerto Rico is still part of the United States, and San Juan is the largest city in Puerto Rico. Where is America/San_Juan? Maybe the problem is that there is a San Juan in almost every Latin American country. If we decide to go with Region/City, then we have to keep it consistent.
Also, since Puerto Rico is in the United States, and is in the Atlantic time zone, there should be a US/Atlantic time zone.
Another inconsistency. Maybe needs a separate bug report. I see America/Aruba and America/Curacao. Where is America/Bonaire?
Then there is the question of America/Detroit. I travel to the East Coast of the US. Do I pick America/Detroit or America/New_York? What's the difference and how would I know? Should I pick America/Detroit only when I am in Detroit, or when I am in Michigan, or on the East Coast?
I personally think that the whole Region/City is garbage. If I live in Houson, Texas, why do I have to pick Chicago (1000 miles away)? After all, Denver is only 880 miles away. How am I even supposed to know that Chicago is in the Central time zone and not Eastern? I like to old system where I just pick the time zone US/Central, but I am offended that the system now changes it to America/Chicago.
And speaking of America/Denver... Which Denver is it? There are eight Denvers in the United States.
I know that some of this has been discussed in the past. And I know the reply will have something to do with upstream. I feel my complaints are legitimate; although some more than others. 

Thanks,

Marc


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tzdata depends on:
ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy 

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
  tzdata/Zones/Australia:
* tzdata/Zones/US: Central
  tzdata/Zones/Asia:
* tzdata/Zones/Etc: UTC
* tzdata/Zones/SystemV: AST4
  tzdata/Zones/Arctic:
  tzdata/Zones/Pacific:
  tzdata/Zones/Antarctica:
  tzdata/Zones/Europe:
  tzdata/Zones/Africa:
* tzdata/Zones/America: Chicago
* tzdata/Areas: SystemV
  tzdata/Zones/Atlantic:
  tzdata/Zones/Indian:

--- End Message ---
--- Begin Message --- 
Source: tzdata
Source-Version: 2024b-6
Done: Aurelien Jarno <aurel32@debian.org>

We believe that the bug you reported is fixed in the latest version of
tzdata, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 602563@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <aurel32@debian.org> (supplier of updated tzdata package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 13 Jan 2025 23:41:11 +0100
Source: tzdata
Architecture: source
Version: 2024b-6
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Closes: 498171 602563 848143
Changes:
 tzdata (2024b-6) unstable; urgency=medium
 .
   * Update debconf autopkgtest following the /etc/timezone change
   * Rework README.Debian. Explain how timezone are named, the split between
     the tzdata and tzdata-legacy packages, the difference between the 'posix'
     and 'right' version and the way to configure the timezone either
     interactively and programmatically (with and without systemd).
     (Closes: #498171, #602563, #848143)
   * Add a note in NEWS about the /etc/timezone deprecation
Checksums-Sha1:
 43b66789b5a16b920e546b19b25a79db47456589 2429 tzdata_2024b-6.dsc
 ddc6294aa56cadb078b5baa2a10dc2928258b9bc 125656 tzdata_2024b-6.debian.tar.xz
 e8e9da85b479d2df909aad357580e2ab0af40df2 5462 tzdata_2024b-6_source.buildinfo
Checksums-Sha256:
 d35ce4bf22e2dd9cddf220a8c65ee8d56aef0554845bd2bf3e9b891e117a4ec7 2429 tzdata_2024b-6.dsc
 da652e7b9e2d5c2557b4eb7d3c5b2711b40a0311dcfda735a76f0e5298a46e68 125656 tzdata_2024b-6.debian.tar.xz
 ea1f027f7deb86d74da541f03bab576d33269cc447f9a388252d1bf2df0f5989 5462 tzdata_2024b-6_source.buildinfo
Files:
 7b801b85f88d779695f5dc5b5831f289 2429 localization required tzdata_2024b-6.dsc
 ef9c3d843fdc5e622e1990b51b62b17f 125656 localization required tzdata_2024b-6.debian.tar.xz
 ad9fe535f35b00ffdfa4ae4eb06e05e4 5462 localization required tzdata_2024b-6_source.buildinfo

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

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmeFmOcACgkQE4jA+Jno
M2tvDQ//YZurx1Ri0zLar8oZjhrTdS8IEIfXnODqfNNptwuqZxqReC1Nnjd2y4IJ
JW2+N9CWLuRgfrXF2CA+sILzh56NrKbsjHKNBexdFAriufAmtJy4imPdd5j6L57F
0CIxRA7lBCGKxSE90tSv5wWZ+/oHP0HTTjs5spPLUHYD8udJE7mC/eSAPnWf+Amr
mwrac2o7fWnCu2x2phrS8kKHv8P2fxchWMQoBp/hG4+pL4uz1U8n/Jd1UqVqNKWT
hBtiPbYeJA2vHHPcg4Hr8bMnWdoVEu6q2Tst9EflxEsSNR8MJaNVKLt0xS0c3XX3
QvhpWZqKH94SUDvGHEXAqNSpzgs9j/v2G4df6MIOiC6dYRoVtCXT9a0NxGfX04pV
D94DioHpNaqp+E9p/mlk/QDRIg8nOkoo4NtbSAqGT80GiD8SP1DFU8YbcWrJ0Ukm
1cLvbYRPv4a5cv8gJEo/jAfJHV53/f2q6kBmh8y69V4sPSz6YC0U4OB97ClWQMF5
cVaXOlBYe4GaRxZWbYu8CivJcRcnYXlmtK+/kA5TrVcUPp91x9PBe00BRL9iGWqM
OYpoWS75M24DvP2vhBYdQ9rtbzgxGlFLtG03JJOqkCDeJX1V+jc2W9bcW5mTQKG4
YIinYwNoKVgWlmqBu5joxyR2PPY2wf5mag9SjjrIwGDydvPRrM4=
=7rQ3
-----END PGP SIGNATURE-----

Attachment: pgpHHizq0e002.pgp
Description: PGP signature


--- End Message ---
Reply to: