Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 452682

Summary: [RHEL 2.1] Brazil time zone changes
Product: Red Hat Enterprise Linux 2.1 Reporter: Petr Machata <pmachata>
Component: tzdataAssignee: Petr Machata <pmachata>
Status: CLOSED ERRATA QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 2.1CC: jplans, mnewsome
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-03 11:05:41 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: 452679    
Bug Blocks:    

Description Petr Machata 2008-06-24 13:52:05 UTC
+++ This bug was initially created as a clone of Bug #452679 +++

This is just to inform you that by law number 11.662 of April 24, 2008
(published in the "Diário Oficial da União"
in Brazil there are changes in the timezones, effective today (00:00am at June
24, 2008) as follows:

a) The timezone UTC+5 is estinguished, with all the Acre state and the part of
the Amazonas state that had this timezone now being put to the timezone UTC+4
b) The whole Pará state now is put at timezone UTC+3, instead of just part of
it, as was before.

(Hence only Acre, part of Amazonas, and part of Para are impacted.)

We don't cover this.  Upstream doesn't cover this neither.  I'll work on patch,
ASYNC erratum will be needed.

Comment 4 errata-xmlrpc 2008-09-03 11:05:41 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.