Bug#813226: tzdata config script ignores /etc/timezone on non-interactive configuration

[Raymond Rakesh Chetty]

Copy paste error: https://stackoverflow.com/a/20693661

Don't forget the 1 at the end or you get sent to the wrong place =).

Somewhat related... maybe I have a misunderstanding of debconf... can you
reconfigure packages that belong to 'd-i'? There are a lot of preseed
questions belonging to 'd-i' (debian-installer), would it make sense (is it
possible?) to allow reconfiguration using parts of the installer
configuration/debconf answers? Not sure there is a reason to have all of
d-i clock-setup/utc, d-i time/zone & tzdata tzdata/Areas etc. But that
might be a discussion left to another day (or maybe the documentation is
out of date?).


$ sudo debconf-get-selections --installer | grep -v '#' | grep 'd-i' | grep
zone
$ sudo debconf-get-selections | grep -v '#' | grep 'd-i' | grep zone
https://www.debian.org/releases/stable/amd64/apbs04.html.en#preseed-time

On Sun, May 20, 2018 at 8:40 PM, Raymond Rakesh Chetty <
raymond.che...@berkeley.edu> wrote:

> Why isn't debconf the single source of truth for tzdata configuration? If
> you used debconf then people wouldn't rely on implementation details to
> correctly configure their systems. Abstract configuration from
> implementation (i.e. separate timezone from is the file a link?, where is
> it located?, which file needs the right information?)
>
> https://stackoverflow.com/a/2069366 would be the top vote and everybody
> would have (or soon obtain) a good (some) understanding of debconf.
>
> All people need to know is what question is going to get asked, or needs
> answering (debconf-show + some documentation). Isn't that how debian is
> supposed to work? https://wiki.debian.org/debconf
>
> The original timezone configuration would get assigned with:
>
> $ echo "tzdata tzdata/Areas select Asia" | sudo debconf-set-selections
>
> $ echo "tzdata tzdata/Zones/Asia select Tokyo" | sudo debconf-set-selection
>
> $ dpkg-reconfigure -fnoninteractive tzdata
>
> --
> Best,
> Raymond Chetty
>
> raymond.che...@berkeley.edu
>
> Confidentiality Notice: This e-mail message, including any attachments, is
> for the sole use of the intended recipient(s) and may contain confidential
> and privileged information. Any unauthorized review, use, disclosure or
> distribution is prohibited. If you are not the intended recipient, please
> contact the sender by reply e-mail and destroy all copies of the original
> message.
>



-- 
Best,
Raymond Chetty

raymond.che...@berkeley.edu

Confidentiality Notice: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.

Bug#813226: tzdata config script ignores /etc/timezone on non-interactive configuration

[Raymond Rakesh Chetty]

Why isn't debconf the single source of truth for tzdata configuration? If
you used debconf then people wouldn't rely on implementation details to
correctly configure their systems. Abstract configuration from
implementation (i.e. separate timezone from is the file a link?, where is
it located?, which file needs the right information?)

https://stackoverflow.com/a/2069366 would be the top vote and everybody
would have (or soon obtain) a good (some) understanding of debconf.

All people need to know is what question is going to get asked, or needs
answering (debconf-show + some documentation). Isn't that how debian is
supposed to work? https://wiki.debian.org/debconf

The original timezone configuration would get assigned with:

$ echo "tzdata tzdata/Areas select Asia" | sudo debconf-set-selections

$ echo "tzdata tzdata/Zones/Asia select Tokyo" | sudo debconf-set-selection

$ dpkg-reconfigure -fnoninteractive tzdata

-- 
Best,
Raymond Chetty

raymond.che...@berkeley.edu

Confidentiality Notice: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.

Bug#813226: tzdata config script ignores /etc/timezone on non-interactive configuration

[Tomáš Ebenlendr]

On Fri, 12 Feb 2016 10:01:34 +0100
Aurelien Jarno  wrote:

> On 2016-02-02 00:23, YAMADA Tsuyoshi wrote:
> > 2016-02-01 16:43 GMT+09:00 Aurelien Jarno :
> > > I don't think it is a bug. The correct way to configure the
> > > timezone has always been to change /etc/localtime symlink, ie in
> > > your case by doing "ln
> > > -sf /usr/share/zoneinfo/Asia/Tokyo /etc/localtime". This is what
> > > desktop environments do when changing the timezone and it is what
> > > systemd expects.
> > >
> > > Changing /etc/timezone worked in some cases before as we use to
> > > store /etc/localtime as a copy of the file instead of a symlink
> > > when possible, in order to allow the timezone to be correct
> > > without a /usr partition. This is not needed anymore given /usr
> > > is now mount from the initramfs when needed.
> > 
> > Hmm, I understand the correct way, but many people are using
> > incorrect way. ("echo Foo/Bar > /etc/timezone" and
> > "dpkg-reconfigure -f noninteractive tzdata")
> > 
> > Please see github:
> > https://github.com/search?q=%2Fetc%2Ftimezone+dpkg-reconfigure+noninteractive+tzdata=Code=%E2%9C%93
> > 
> > There are about 4,000 codes!
> > 
> > I think this incompatibility for those codes is not so good.
> > 
> > I propose a patch for debian/tzdata.config
> > (/var/lib/dpkg/info/tzdata.config):
> > 
> >   --- /tmp/tzdata.config.bak 2016-01-29 20:28:52.0 +
> >   +++ tzdata.config 2016-02-01 14:42:09.462282218 +
> >   @@ -326,15 +326,6 @@
> >esac
> >}
> > 
> >   -# If /etc/localtime is a link, update /etc/timezone
> >   -if [ -L /etc/localtime ] ; then
> >   -TIMEZONE="$(readlink /etc/localtime)"
> >   -TIMEZONE="${TIMEZONE#/usr/share/zoneinfo/}"
> >   -if [ -f "/usr/share/zoneinfo/$TIMEZONE" ] ; then
> >   -echo ${TIMEZONE} > /etc/timezone
> >   -fi
> >   -fi
> >   -
> ># Read /etc/timezone
> >if [ -e /etc/timezone ]; then
> >TIMEZONE="$(head -n 1 /etc/timezone)"
> >   @@ -350,6 +341,15 @@
> >fi
> >fi
> > 
> >   +# If /etc/localtime is a link, update /etc/timezone
> >   +if [ -L /etc/localtime ] ; then
> >   +TIMEZONE="$(readlink /etc/localtime)"
> >   +TIMEZONE="${TIMEZONE#/usr/share/zoneinfo/}"
> >   +if [ -f "/usr/share/zoneinfo/$TIMEZONE" ] ; then
> >   +echo ${TIMEZONE} > /etc/timezone
> >   +fi
> >   +fi
> >   +
> ># The timezone is already configured
> >if [ -e /etc/timezone ] && [ -e /etc/localtime ] ; then
> ># Don't ask the user, except if he/she explicitely asked that
> > 
> > 
> > This patch will keep compatibility like this:
> > 
> >   root@031baca8faac:~# echo Asia/Tokyo > /etc/timezone
> >   root@031baca8faac:~# readlink /etc/localtime
> >   /usr/share/zoneinfo/Etc/UTC
> >   root@031baca8faac:~# dpkg-reconfigure -f noninteractive tzdata
> > 
> >   Current default time zone: 'Asia/Tokyo'
> >   Local time is now:  Mon Feb  1 23:45:19 JST 2016.
> >   Universal Time is now:  Mon Feb  1 14:45:19 UTC 2016.
> > 
> >   root@031baca8faac:~# cat /etc/timezone
> >   Asia/Tokyo
> >   root@031baca8faac:~# readlink /etc/localtime
> >   /usr/share/zoneinfo/Asia/Tokyo
> > 
> > Could you please consider this patch?
> 
> This patch will break all software which change /etc/localtime without
> changing /etc/timezone. I don't know if it is better to break the
> compatibility with external scripts or with software we ship in
> debian.
> 
> Aurelien
> 

There is also possibility, to decide by mtime of /etc/localtime
and /etc/timezone. The newer file will be the source of truth.
Then both types of software will work, provided that dpkg-reconfigure
will be run to synchronize state of those files. This is not a clean
solution (and I would hesitate to accept it), but your opinion may be
different, so I wanted to mention this idea. Anyways, the final
solution should be documented, as I mentioned in my previous email.



-- 
*Úspěch, charisma a inspirace v jednom magazínu. *
*Čtěte o nejúspěšnějších ženách Česka.*

*Objednejte si exkluzivní magazín Hospodářských novin Top ženy Česka 2016 
.*


signature.asc
Description: PGP signature

Bug#813226: tzdata config script ignores /etc/timezone on non-interactive configuration

[Tomas Ebenlendr]

On Mon, 1 Feb 2016 08:43:32 +0100
Aurelien Jarno  wrote:

> ...
> I don't think it is a bug. The correct way to configure the timezone has
> always been to change /etc/localtime symlink, ie in your case by doing
> "ln -sf /usr/share/zoneinfo/Asia/Tokyo /etc/localtime". This is what
> desktop environments do when changing the timezone and it is what
> systemd expects.

But after dpkg-reconfigure tzdata, content of this symlink was written
into /etc/timezone and the symlink was turned into real file.
Subsequent runs of dpkg-reconfigure have seen /etc/localtime real file,
thus behaving as if /etc/timezone is the source of authority here,
and /etc/localtime symlink is some obsure state which needs to be
transformed into /etc/timezone authority and /etc/localtime real file,
driven by /etc/timezone.

New package completely changes source of authority to /etc/localtime,
as tzdata.postinst script makes /etc/localtime into symlink, and
subsequent run of tzdata.config rewrites contents of /etc/timezone
based on the value of the symlink.

This change in behaviour should be documented, at least somewhere
in /usr/share/doc/tzdata/...

P.S.: Ansible (or other orchestration tool), usually checks file not
only by its contents, but also by its type. Thus there must be now two
paths (old tzdata and new tzdata) when checking /etc/localtime.
Checking /etc/timezone is not sufficient after the change. I spent 4
hours by debugging our ansible environment because of poor
documentation of this change and poor documentation of relation
between /etc/timezone and /etc/localtime in older versions of tzdata.

> Changing /etc/timezone worked in some cases before as we use to store
> /etc/localtime as a copy of the file instead of a symlink when possible,
> in order to allow the timezone to be correct without a /usr partition.
> This is not needed anymore given /usr is now mount from the initramfs
> when needed.
> 
> Aurelien
> 



-- 
 Tomáš 'ebík' Ebenlendr
 Economia a.s.
 PF 2017.15021197996


-- 
*Úspěch, charisma a inspirace v jednom magazínu. *
*Čtěte o nejúspěšnějších ženách Česka.*

*Objednejte si exkluzivní magazín Hospodářských novin Top ženy Česka 2016 
.*


pgpt1e99w1Zx2.pgp
Description: OpenPGP digital signature

Bug#813226: tzdata config script ignores /etc/timezone on non-interactive configuration

[Aurelien Jarno]

On 2016-02-02 00:23, YAMADA Tsuyoshi wrote:
> 2016-02-01 16:43 GMT+09:00 Aurelien Jarno :
> > I don't think it is a bug. The correct way to configure the timezone has
> > always been to change /etc/localtime symlink, ie in your case by doing
> > "ln -sf /usr/share/zoneinfo/Asia/Tokyo /etc/localtime". This is what
> > desktop environments do when changing the timezone and it is what
> > systemd expects.
> >
> > Changing /etc/timezone worked in some cases before as we use to store
> > /etc/localtime as a copy of the file instead of a symlink when possible,
> > in order to allow the timezone to be correct without a /usr partition.
> > This is not needed anymore given /usr is now mount from the initramfs
> > when needed.
> 
> Hmm, I understand the correct way, but many people are using incorrect way.
> ("echo Foo/Bar > /etc/timezone" and "dpkg-reconfigure -f noninteractive 
> tzdata")
> 
> Please see github:
> https://github.com/search?q=%2Fetc%2Ftimezone+dpkg-reconfigure+noninteractive+tzdata=Code=%E2%9C%93
> 
> There are about 4,000 codes!
> 
> I think this incompatibility for those codes is not so good.
> 
> I propose a patch for debian/tzdata.config (/var/lib/dpkg/info/tzdata.config):
> 
>   --- /tmp/tzdata.config.bak 2016-01-29 20:28:52.0 +
>   +++ tzdata.config 2016-02-01 14:42:09.462282218 +
>   @@ -326,15 +326,6 @@
>esac
>}
> 
>   -# If /etc/localtime is a link, update /etc/timezone
>   -if [ -L /etc/localtime ] ; then
>   -TIMEZONE="$(readlink /etc/localtime)"
>   -TIMEZONE="${TIMEZONE#/usr/share/zoneinfo/}"
>   -if [ -f "/usr/share/zoneinfo/$TIMEZONE" ] ; then
>   -echo ${TIMEZONE} > /etc/timezone
>   -fi
>   -fi
>   -
># Read /etc/timezone
>if [ -e /etc/timezone ]; then
>TIMEZONE="$(head -n 1 /etc/timezone)"
>   @@ -350,6 +341,15 @@
>fi
>fi
> 
>   +# If /etc/localtime is a link, update /etc/timezone
>   +if [ -L /etc/localtime ] ; then
>   +TIMEZONE="$(readlink /etc/localtime)"
>   +TIMEZONE="${TIMEZONE#/usr/share/zoneinfo/}"
>   +if [ -f "/usr/share/zoneinfo/$TIMEZONE" ] ; then
>   +echo ${TIMEZONE} > /etc/timezone
>   +fi
>   +fi
>   +
># The timezone is already configured
>if [ -e /etc/timezone ] && [ -e /etc/localtime ] ; then
># Don't ask the user, except if he/she explicitely asked that
> 
> 
> This patch will keep compatibility like this:
> 
>   root@031baca8faac:~# echo Asia/Tokyo > /etc/timezone
>   root@031baca8faac:~# readlink /etc/localtime
>   /usr/share/zoneinfo/Etc/UTC
>   root@031baca8faac:~# dpkg-reconfigure -f noninteractive tzdata
> 
>   Current default time zone: 'Asia/Tokyo'
>   Local time is now:  Mon Feb  1 23:45:19 JST 2016.
>   Universal Time is now:  Mon Feb  1 14:45:19 UTC 2016.
> 
>   root@031baca8faac:~# cat /etc/timezone
>   Asia/Tokyo
>   root@031baca8faac:~# readlink /etc/localtime
>   /usr/share/zoneinfo/Asia/Tokyo
> 
> Could you please consider this patch?

This patch will break all software which change /etc/localtime without
changing /etc/timezone. I don't know if it is better to break the
compatibility with external scripts or with software we ship in debian.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#813226: tzdata config script ignores /etc/timezone on non-interactive configuration

[YAMADA Tsuyoshi]

2016-02-01 16:43 GMT+09:00 Aurelien Jarno :
> I don't think it is a bug. The correct way to configure the timezone has
> always been to change /etc/localtime symlink, ie in your case by doing
> "ln -sf /usr/share/zoneinfo/Asia/Tokyo /etc/localtime". This is what
> desktop environments do when changing the timezone and it is what
> systemd expects.
>
> Changing /etc/timezone worked in some cases before as we use to store
> /etc/localtime as a copy of the file instead of a symlink when possible,
> in order to allow the timezone to be correct without a /usr partition.
> This is not needed anymore given /usr is now mount from the initramfs
> when needed.

Hmm, I understand the correct way, but many people are using incorrect way.
("echo Foo/Bar > /etc/timezone" and "dpkg-reconfigure -f noninteractive tzdata")

Please see github:
https://github.com/search?q=%2Fetc%2Ftimezone+dpkg-reconfigure+noninteractive+tzdata=Code=%E2%9C%93

There are about 4,000 codes!

I think this incompatibility for those codes is not so good.

I propose a patch for debian/tzdata.config (/var/lib/dpkg/info/tzdata.config):

  --- /tmp/tzdata.config.bak 2016-01-29 20:28:52.0 +
  +++ tzdata.config 2016-02-01 14:42:09.462282218 +
  @@ -326,15 +326,6 @@
   esac
   }

  -# If /etc/localtime is a link, update /etc/timezone
  -if [ -L /etc/localtime ] ; then
  -TIMEZONE="$(readlink /etc/localtime)"
  -TIMEZONE="${TIMEZONE#/usr/share/zoneinfo/}"
  -if [ -f "/usr/share/zoneinfo/$TIMEZONE" ] ; then
  -echo ${TIMEZONE} > /etc/timezone
  -fi
  -fi
  -
   # Read /etc/timezone
   if [ -e /etc/timezone ]; then
   TIMEZONE="$(head -n 1 /etc/timezone)"
  @@ -350,6 +341,15 @@
   fi
   fi

  +# If /etc/localtime is a link, update /etc/timezone
  +if [ -L /etc/localtime ] ; then
  +TIMEZONE="$(readlink /etc/localtime)"
  +TIMEZONE="${TIMEZONE#/usr/share/zoneinfo/}"
  +if [ -f "/usr/share/zoneinfo/$TIMEZONE" ] ; then
  +echo ${TIMEZONE} > /etc/timezone
  +fi
  +fi
  +
   # The timezone is already configured
   if [ -e /etc/timezone ] && [ -e /etc/localtime ] ; then
   # Don't ask the user, except if he/she explicitely asked that


This patch will keep compatibility like this:

  root@031baca8faac:~# echo Asia/Tokyo > /etc/timezone
  root@031baca8faac:~# readlink /etc/localtime
  /usr/share/zoneinfo/Etc/UTC
  root@031baca8faac:~# dpkg-reconfigure -f noninteractive tzdata

  Current default time zone: 'Asia/Tokyo'
  Local time is now:  Mon Feb  1 23:45:19 JST 2016.
  Universal Time is now:  Mon Feb  1 14:45:19 UTC 2016.

  root@031baca8faac:~# cat /etc/timezone
  Asia/Tokyo
  root@031baca8faac:~# readlink /etc/localtime
  /usr/share/zoneinfo/Asia/Tokyo

Could you please consider this patch?

Bug#813226: tzdata config script ignores /etc/timezone on non-interactive configuration

[Aurelien Jarno]

On 2016-01-31 00:36, YAMADA Tsuyoshi wrote:
> Package: tzdata
> Version: 2016a-1
> Severity: minor
> 
> Dear Maintainer,
> 
> After tzdata 2016a-1, automated tzdata configuration with
> 
>   echo "Asia/Tokyo" > /etc/timezone
>   dpkg-reconfigure -fnoninteractive tzdata
> 
> does not work.
> 
> With tzdata 2015g-1, it works.
> 
>   root@a26eeeb7b8b7:~# date
>   Sat Jan 30 15:28:54 UTC 2016
>   root@a26eeeb7b8b7:~# echo Asia/Tokyo > /etc/timezone
>   root@a26eeeb7b8b7:~# dpkg-reconfigure -fnoninteractive tzdata
> 
>   Current default time zone: 'Asia/Tokyo'
>   Local time is now:  Sun Jan 31 00:29:12 JST 2016.
>   Universal Time is now:  Sat Jan 30 15:29:12 UTC 2016.
> 
>   root@a26eeeb7b8b7:~# date
>   Sun Jan 31 00:29:13 JST 2016
> 
> But with tzdata 2016a-1, it does not work well.
> 
>   root@fdc1139936e4:~# date
>   Sat Jan 30 15:30:00 UTC 2016
>   root@fdc1139936e4:~# echo Asia/Tokyo > /etc/timezone
>   root@fdc1139936e4:~# dpkg-reconfigure -fnoninteractive tzdata
> 
>   Current default time zone: 'Etc/UTC'
>   Local time is now:  Sat Jan 30 15:30:21 UTC 2016.
>   Universal Time is now:  Sat Jan 30 15:30:21 UTC 2016.
> 
>   root@fdc1139936e4:~# date
>   Sat Jan 30 15:30:23 UTC 2016
> 
> I have found a workaround, deleting /etc/localtime
> before running dpkg-reconfigure solves this problem.
> 
>   root@fdc1139936e4:~# date
>   Sat Jan 30 15:30:50 UTC 2016
>   root@fdc1139936e4:~# echo Asia/Tokyo > /etc/timezone
>   root@fdc1139936e4:~# rm /etc/localtime
>   root@fdc1139936e4:~# dpkg-reconfigure -fnoninteractive tzdata
> 
>   Current default time zone: 'Asia/Tokyo'
>   Local time is now:  Sun Jan 31 00:31:15 JST 2016.
>   Universal Time is now:  Sat Jan 30 15:31:15 UTC 2016.
> 
>   root@fdc1139936e4:~# date
>   Sun Jan 31 00:31:18 JST 2016
> 
> Is this bug of tzdata config script? Or expected behavior?

I don't think it is a bug. The correct way to configure the timezone has
always been to change /etc/localtime symlink, ie in your case by doing
"ln -sf /usr/share/zoneinfo/Asia/Tokyo /etc/localtime". This is what
desktop environments do when changing the timezone and it is what
systemd expects.

Changing /etc/timezone worked in some cases before as we use to store
/etc/localtime as a copy of the file instead of a symlink when possible,
in order to allow the timezone to be correct without a /usr partition.
This is not needed anymore given /usr is now mount from the initramfs
when needed.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#813226: tzdata config script ignores /etc/timezone on non-interactive configuration

[YAMADA Tsuyoshi]

Package: tzdata
Version: 2016a-1
Severity: minor

Dear Maintainer,

After tzdata 2016a-1, automated tzdata configuration with

  echo "Asia/Tokyo" > /etc/timezone
  dpkg-reconfigure -fnoninteractive tzdata

does not work.

With tzdata 2015g-1, it works.

  root@a26eeeb7b8b7:~# date
  Sat Jan 30 15:28:54 UTC 2016
  root@a26eeeb7b8b7:~# echo Asia/Tokyo > /etc/timezone
  root@a26eeeb7b8b7:~# dpkg-reconfigure -fnoninteractive tzdata

  Current default time zone: 'Asia/Tokyo'
  Local time is now:  Sun Jan 31 00:29:12 JST 2016.
  Universal Time is now:  Sat Jan 30 15:29:12 UTC 2016.

  root@a26eeeb7b8b7:~# date
  Sun Jan 31 00:29:13 JST 2016

But with tzdata 2016a-1, it does not work well.

  root@fdc1139936e4:~# date
  Sat Jan 30 15:30:00 UTC 2016
  root@fdc1139936e4:~# echo Asia/Tokyo > /etc/timezone
  root@fdc1139936e4:~# dpkg-reconfigure -fnoninteractive tzdata

  Current default time zone: 'Etc/UTC'
  Local time is now:  Sat Jan 30 15:30:21 UTC 2016.
  Universal Time is now:  Sat Jan 30 15:30:21 UTC 2016.

  root@fdc1139936e4:~# date
  Sat Jan 30 15:30:23 UTC 2016

I have found a workaround, deleting /etc/localtime
before running dpkg-reconfigure solves this problem.

  root@fdc1139936e4:~# date
  Sat Jan 30 15:30:50 UTC 2016
  root@fdc1139936e4:~# echo Asia/Tokyo > /etc/timezone
  root@fdc1139936e4:~# rm /etc/localtime
  root@fdc1139936e4:~# dpkg-reconfigure -fnoninteractive tzdata

  Current default time zone: 'Asia/Tokyo'
  Local time is now:  Sun Jan 31 00:31:15 JST 2016.
  Universal Time is now:  Sat Jan 30 15:31:15 UTC 2016.

  root@fdc1139936e4:~# date
  Sun Jan 31 00:31:18 JST 2016

Is this bug of tzdata config script? Or expected behavior?

-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (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.58

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
  tzdata/Zones/SystemV:
  tzdata/Zones/Antarctica:
  tzdata/Zones/Pacific:
  tzdata/Zones/Atlantic:
* tzdata/Zones/Asia: Tokyo
* tzdata/Zones/Etc: UTC
  tzdata/Zones/US:
  tzdata/Zones/Europe:
  tzdata/Zones/Australia:
  tzdata/Zones/Africa:
* tzdata/Areas: Asia
  tzdata/Zones/Arctic: