Perth and Hobart zoneinfo files missing

Issue #287 resolved
prl created an issue

Zoneinfo files for Perth and Hobart are missing in firmware 20140713.

Users who select Hobart or Perth as their time zone will have UTC as their timezone, because the zoneinfo code falls back to UTCif time zone information is missing.

Reproduction steps

Log into the T3 command line interface using telnet or ssh.

root@beyonwizt3:~# cat /etc/timezone.xml 
<?xml version="1.0" encoding="iso-8859-1" ?>

<timezone>
        <zone name="(GMT+08:00) Perth" zone="Australia/Perth" />
        <zone name="(GMT+09:30) Adelaide" zone="Australia/Adelaide" />
        <zone name="(GMT+09:30) Darwin" zone="Australia/Darwin" />
        <zone name="(GMT+10:00) Brisbane" zone="Australia/Brisbane" />
        <zone name="(GMT+10:00) Canberra, Melbourne, Sydney" zone="Australia/Sydney" />
        <zone name="(GMT+10:00) Hobart" zone="Australia/Hobart" />
</timezone>
root@beyonwizt3:~#

Shows that zoneinfo files for Perth and Hobart are required for time zone setup.

root@beyonwizt3:~# ls -l /usr/share/zoneinfo/Australia/
-rw-r--r--    1 root     root          2224 Jul 14 02:58 Adelaide
-rw-r--r--    1 root     root           439 Jul 14 02:58 Brisbane
-rw-r--r--    1 root     root           310 Jul 14 02:58 Darwin
-rw-r--r--    1 root     root          2209 Jul 14 02:58 Sydney
root@beyonwizt3:~#

Shows that they are missing.

Comments (4)

  1. Peter Urbanec
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from New to Confirmed.
  2. Peter Urbanec
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from Confirmed to Implemented.
  3. Peter Urbanec
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from Implemented to Testing.
  4. Peter Urbanec
    • removed issue_resolution
    • removed issue_percent
    • removed issue_close
    • removed issue_status

    The issue was updated with the following change(s):

    • The status has been updated, from Testing to Closed.
    • This issue has been closed
    • This issue's progression has been updated to 100 percent completed.
    • The resolution has been updated, from Not determined to Fixed.
  5. Log in to comment