Bug#1051973: tzdata: no warning about moving US/* to tzdata-legacy

2023-10-03 Thread Steev Klimaszewski
Hello! This also affects Postgresql Updates as the timezone is written to the configuration file, so for example Debian testing recently upgraded from postgresql-15 to postgresql-16 and if you attempt to follow the instructions in /usr/share/doc/postgresql-common/README.Debian.gz you end up gettin

Bug#1051973: tzdata: no warning about moving US/* to tzdata-legacy

2023-09-15 Thread Mike Kupfer
Mike Kupfer wrote: > I'm okay with the change itself, but it really should get more > visibility. That is, on upgrade the user should get some sort of > heads-up that they are getting an incompatible change and may need to > take corrective action. To clarify, what I have in mind is a news entry

Bug#1051973: tzdata: no warning about moving US/* to tzdata-legacy

2023-09-14 Thread Mike Kupfer
Package: tzdata Version: 2023c-10 Severity: important X-Debbugs-Cc: kup...@rawbw.com Dear Maintainer, After using synaptic or apt to upgrade tzdata from 2023c-7 to 2023c-10, I would get the wrong time in my desktop environments and on a virtual terminal (no X). I would get UTC, rather than my lo