Hello, last year, the DST automatic adjust for my recently installed system was wrong. It is a Debian 9 install. I adjusted it manually in the start and end or the period. It was not done according to what was defined by our State sometime before. Please note that it was not something done close to the change date. My friends and I looked around a bit, and we found that this change should have passed here somehow. Next year, I do not know how it will be. Who is responsible for this kind of information or update?
On 1/14/19 3:20 PM, Dedeco Balaco via tz wrote:
Who is responsible for this kind of information or update?
You're responsible for installing Debian's time zone updates and for setting your time zone correctly. Debian is responsible for getting time zone data from tzdb. We're responsible for publishing the best data we can. It's not clear from your email where the problem is in that chain, so it sounds like you may need to do some detective work to isolate the problem. You can start by looking here: https://github.com/eggert/tz/blob/master/NEWS and map its release numbers to what's installed on your system now.
On 2019-01-14 16:42, Paul Eggert wrote:
On 1/14/19 3:20 PM, Dedeco Balaco via tz wrote:
Who is responsible for this kind of information or update? You're responsible for installing Debian's time zone updates and for setting your time zone correctly. Debian is responsible for getting time zone data from tzdb. We're responsible for publishing the best data we can. It's not clear from your email where the problem is in that chain, so it sounds like you may need to do some detective work to isolate the problem. You can start by looking here: https://github.com/eggert/tz/blob/master/NEWS and map its release numbers to what's installed on your system now.
With distros, tzdata releases available depends how up to date the maintainers keep the distro, and the package maintainers keep the tzdata package; which base distro release you run e.g. 9 Stretch, 10 Buster; which repos you have available on your selected mirror(s) and defined in your /etc/apt/sources.list e.g. debian-updates, debian-proposed-updates, debian-backports, debian-security/updates; although if a newer release is available for your distro, the currently installed release should be able to be upgraded using your preferred package manager e.g. as I have a package mirrors with debian-updates repo available, and as I have added debian-updates repos to my package sources, I am up to date: $ apt list -a tzdata Listing... Done tzdata/stable-updates,stable-updates,stable-updates,now 2018i-0+deb9u1 all [installed] tzdata/stable,stable,stable 2018g-0+deb9u1 all $ sudo apt install tzdata=2018i-0+deb9u1 Reading package lists... Done Building dependency tree Reading state information... Done tzdata is already the newest version (2018i-0+deb9u1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. SImilarly on Ubuntu 16.04 Xenial: $ apt list -a tzdata Listing... Done tzdata/xenial-updates,xenial-security,now 2018i-0ubuntu0.16.04 all [installed] tzdata/xenial-updates,xenial-security 2018g-0ubuntu0.16.04 all tzdata/xenial-updates,xenial-security 2016j-0ubuntu0.16.04 all tzdata/xenial,xenial,xenial 2016d-0ubuntu0.16.04 all where the base release is much older than Debian, and more recent distro release 18.04 Bionic is only at 2018d, and 18.10 Cosmic at 2018e. Other distros may offer only older package releases e.g. Fedora whereas CentOS. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised.
On 2019-01-15 07:27, Brian Inglis wrote:
offer only older package releases e.g. Fedora whereas CentOS... ...is up to date. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised.
participants (3)
-
Brian Inglis -
Dedeco Balaco -
Paul Eggert