Bug 689286

Summary:	Turkey DST Update (Java, RHEL 6)
Product:	Red Hat Enterprise Linux 6	Reporter:	J.H.M. Dassen (Ray) <rdassen>
Component:	distribution	Assignee:	RHEL Program Management <pm-rhel>
Status:	CLOSED DUPLICATE	QA Contact:	Brock Organ <borgan>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.0	CC:	rbinkhor
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	689287 (view as bug list)		Environment:
Last Closed:	2011-03-21 08:53:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	689287

Description J.H.M. Dassen (Ray) 2011-03-20 20:52:30 UTC

[Reporting against "distribution" as bugzilla doesn't have tzdata-java in the component list]

Description of problem:
The Turkish government has decided to delay the switchover to DST for 2011 by one day; cf. <http://www.worldtimezone.com/dst_news/dst_news_turkey03.html>.

tzdata-java has outdated DST information for Turkey for 2011.

Version-Release number of selected component (if applicable):
tzdata-java-2011b-1.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Download and extract DSTTest.zip from <http://www-01.ibm.com/support/docview.wss?uid=swg24014974>
2. Run "env JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/ bash dumpDetails.sh Europe/Istanbul | grep 2011"
  
Actual results:
        on 03/27/2011 at 03:00 AM offset becomes GMT+03:00 (save 01:00)
        on 10/30/2011 at 04:00 AM offset becomes GMT+02:00

Expected results:
        on 03/28/2011 at 03:00 AM offset becomes GMT+03:00 (save 01:00)
        on 10/30/2011 at 04:00 AM offset becomes GMT+02:00

Comment 1 J.H.M. Dassen (Ray) 2011-03-21 08:53:06 UTC

tzdata-java, like tzdata, is built from the tzdata srpm, so there's no need for a separate report for it.

*** This bug has been marked as a duplicate of bug 684213 ***