Package: tzdata Version: 2018i-0+deb9u1 Followup-For: Bug #704089 Dear Maintainer, This is still a problem 4 years later, and I unexpectedly found myself spending time to track it down when doing configuration management. Can we please get the above patch applied *before* the Buster soft-freeze on 2019-02-12 (just over a month away)? It seems the only work-around for now (aside from patching tzdata.config before executing dpkg-reconfigure in non-interactive mode) is to delete /etc/timezone first. As discussed in #516755, that has the effect of causing a race condition that can lead to things like log files showing wrong timestamps. Not great. Thanks, Adam -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (400, 'proposed-updates'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en:ja (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tzdata depends on: ii debconf [debconf-2.0] 1.5.61 tzdata recommends no packages. tzdata suggests no packages. -- debconf-show failed
Attachment:
signature.asc
Description: PGP signature