Bug 3548 - PHP timezone database needs update
Summary: PHP timezone database needs update
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Spuhler
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks: 3600
  Show dependency tree / graph
 
Reported: 2011-11-30 23:10 CET by Dimitri Jakov
Modified: 2011-12-04 02:16 CET (History)
1 user (show)

See Also:
Source RPM: php-timezonedb-2011.5-1.mga1
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Dimitri Jakov 2011-11-30 23:10:33 CET 
Description of problem:

PHP uses its own timezone database in a form of PHP extension (essentially, a .so file). Current version (2011.5) does not reflect actual DST information for Russia and some other countries where DST has been nullified. Suggest updating the package to a recent version (2011.14 as of now).

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

2011.5-1.mga1

How reproducible:

always

Steps to Reproduce:
1. <?php echo date(DATE_RFC850); ?>
2. if you are in an affected country, output will differ 1 hour from system clock
3.
Comment 1 Manuel Hiebel 2011-12-01 17:22:11 CET 
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

Keywords: (none) => Triaged
Assignee: bugsquad => thomas

Comment 2 Thomas Spuhler 2011-12-02 05:20:36 CET 
Fixed, upgraded to version 2011.14

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 3 Dave Hodgins 2011-12-03 22:20:11 CET 
Shouldn't this also be updated in Mageia 1?

CC: (none) => davidwhodgins
Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 4 Thomas Spuhler 2011-12-04 01:23:33 CET 
Would you mind to find file a bug under mga1?
Dave Hodgins 2011-12-04 02:15:00 CET

Blocks: (none) => 3600

Comment 5 Dave Hodgins 2011-12-04 02:16:21 CET 
Bug 3600 cloned from this bug for Mageia 1.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.