Bug 1377715 - Turkey stays on DST since 2016
Summary: Turkey stays on DST since 2016
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: tzdata
Version: 4.9
Hardware: Unspecified
OS: All
unspecified
medium
Target Milestone: rc
: ---
Assignee: Patsy Griffin
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 1377695
Blocks: 1377707 1377711
TreeView+ depends on / blocked
 
Reported: 2016-09-20 12:38 UTC by Zdenek Pytela
Modified: 2019-12-16 06:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1377695
Environment:
Last Closed: 2016-09-30 21:45:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2642991 0 None None None 2016-09-20 12:38:08 UTC
Red Hat Product Errata RHEA-2016:1982 0 normal SHIPPED_LIVE tzdata enhancement update 2016-10-01 01:44:29 UTC

Description Zdenek Pytela 2016-09-20 12:38:09 UTC
+++ This bug was initially created as a clone of Bug #1377695 +++

Description of problem:
Based on Turkish Council of Ministers decision, Turkey will stay permanently on DST, i. e. UTC+3. The decision was made on Sep 7th, 2016.

Version-Release number of selected component (if applicable):
tzdata-2016f

How reproducible:
always

Steps to Reproduce:
1. zdump -v Asia/Istanbul|grep 2016

Actual results:
Time changes back 1 hour with the end of DST

Expected results:
Time is not changing back as of 2016

Additional info:
https://www.timeanddate.com/news/time/turkey-scraps-dst-2016.html

Comment 11 errata-xmlrpc 2016-09-30 21:45:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-1982.html


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