Bug 1044305 - Jordan DST change
Summary: Jordan DST change
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tzdata
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Patsy Griffin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 04:34 UTC by Patsy Griffin
Modified: 2015-10-05 19:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-05 19:49:00 UTC
Type: Bug


Attachments (Terms of Use)

Description Patsy Griffin 2013-12-18 04:34:24 UTC
Additional info:
+++ This bug was initially created as a clone of Bug #1043502 +++

Description of problem:

Jordan has reversed its decision to drop DST changes and is going back to previous rules as well as going to winter time on December 20th.

Per http://www.timeanddate.com/news/time/jordan-reverses-dst-decision.html
and
http://mm.icann.org/pipermail/tz/2013-December/020517.html

Please include commits:
ed8f3bd6d28689369c7632bf758b0d11ff77f343
b0cde690c66b6c91404f738059f940df3fc1e4a8
from https://github.com/eggert/tz
in the tzdata package as soon as possible (hopefully before 20th December).

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

tzdata-2013g-1.el5

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Jan Kurik on 2013-12-16 08:57:47 EST ---

Granting pm_ack+ on behalf of PM.

Comment 1 Dominik 'Rathann' Mierzejewski 2013-12-20 09:17:57 UTC
tzdata 2013i has just been released by upstream, so no need to patch anymore.

Comment 2 Jaroslav Reznik 2015-03-03 17:11:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22


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