Bug 739668

Summary: Now Belarus use UTC+3
Product: Red Hat Enterprise Linux 5 Reporter: Yuri Timofeev <tim4dev>
Component: tzdataAssignee: Petr Machata <pmachata>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.8CC: azelinka, dbayly, kvolny, mnewsome, mpoole, rdassen, zzhou
Target Milestone: rc   
Target Release: 5.8   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 740000 (view as bug list) Environment:
Last Closed: 2011-10-26 17:51:01 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: 740000, 740001, 740014    

Description Yuri Timofeev 2011-09-19 18:46:30 UTC 
Description of problem:

http://www.worldtimezone.com/dst_news/dst_news_belarus02.html

Belarus has abolished seasonal clock change. It was announced by State Committee for Standardization on September 16, 2011. This decision was made by the Council of Ministers (decree #1229) on September 15, 2011. Belarus will use its current Standart time zone (UTC+2) plus one hour.

Comments from WorldTimeZone.com:
(Belarus plan to use current "summer time" year around- without any seasonal clock change- UTC+3 - same as Russia going to use "permanent summer time").
Comment 1 Petr Machata 2011-09-20 17:33:35 UTC 
Patch is being prepared upstream.  Ukraine seems to have joined the party and has canceled the DST, too.
Comment 2 Petr Machata 2011-09-20 17:33:50 UTC 
(http://news.mail.ru/politics/6861560/)
Comment 3 Petr Machata 2011-09-21 09:31:42 UTC 
A bug report was opened to track the Ukrainian change:
https://bugzilla.redhat.com/show_bug.cgi?id=739916
Comment 7 errata-xmlrpc 2011-10-26 17:51:01 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-2011-1410.html