Bug 1080526 - tzdata: Crimea will switch to Moscow time on 2014-03-30
Summary: tzdata: Crimea will switch to Moscow time on 2014-03-30
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: tzdata
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Patsy Griffin
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1080527 1080528 1080529
TreeView+ depends on / blocked
 
Reported: 2014-03-25 15:44 UTC by Patsy Griffin
Modified: 2014-03-28 18:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Crimea will transition to Moscow time on March 30, 2014. Consequence: This requires an update to the tzdata package. Fix: Update to tzdata-2014b. Result: tzdata will correctly reflect the timezone change for Crimea.
Clone Of:
: 1080527 (view as bug list)
Environment:
Last Closed: 2014-03-28 18:12:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0338 0 normal SHIPPED_LIVE tzdata enhancement update 2014-03-28 22:11:21 UTC

Description Patsy Griffin 2014-03-25 15:44:00 UTC 
Description of problem:
The 2014b release of the tz code and data is available.  It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes:

  Changes affecting near-future time stamps

    Crimea switches to Moscow time on 2014-03-30 at 02:00 local time.
    (Thanks to Alexander Krivenyshev.)  Move its zone.tab entry from UA
    to RU.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 errata-xmlrpc 2014-03-28 18:12:14 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.

http://rhn.redhat.com/errata/RHEA-2014-0338.html
Note You need to log in before you can comment on or make changes to this bug.