Bug 1380738 - retroactive changes in zone abbreviations
Summary: retroactive changes in zone abbreviations
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tzdata
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Patsy Griffin
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-30 12:45 UTC by Karel Volný
Modified: 2017-02-28 21:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-28 21:53:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Karel Volný 2016-09-30 12:45:27 UTC
Description of problem:
Upstream makes retroactive changes in zone abbreviations, despite it was promised that the new scheme will be applied only to new zones and zone transfers.

Due to rebasing tzdata, this affects *existing* installations, but I believe this is the kind of change that should NOT be done in .z stream, such changes in behaviour should be done only between major RHEL versions.

Version-Release number of selected component (if applicable):
2016g (and maybe older)

How reproducible:
always

Steps to Reproduce:
1. TZ=Asia/Vladivostok date -d "2003-08-03 22:43:22 UTC"

Actual results:
Mon Aug  4 09:43:22 +11 2003

Expected results:
Mon Aug  4 09:43:22 VLAST 2003

Additional info:
In this particular example, the change is very unfortunate - as it was already pointed on the upstream mailinglist (where the new system received significant backlash but was forced by "who codes decides" anyways), Russia uses numbered zones, so ordinary user (not following upstream development) has about zero chance to understand that "+11" does NOT mean "Moscow + 11" in this case.


Note You need to log in before you can comment on or make changes to this bug.