Bug 4214

Summary: PHP causes many timezone errors in apache error log
Product: Mageia Reporter: claire robinson <eeeemail>
Component: RPM PackagesAssignee: Thomas Spuhler <thomas>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Normal    
Version: 1   
Target Milestone: ---   
Hardware: All   
OS: Linux   
URL: https://bugs.mageia.org/show_bug.cgi?id=3895
Whiteboard:
Source RPM: php-ini php-timezonedb php-apc php not sure CVE:
Status comment:

Description claire robinson 2012-01-21 15:31:21 CET 
This bug has been created to allow an update candidate for PHP to be validated, please see bug 3895. It is important to validate the update as it currently breaks upgrade from Mandriva.

PHP produces many error messages in /var/log/httpd/error.log such as below..

[Fri Jan 20 14:28:30 2012] [error] [client 127.0.0.1] PHP Warning:  date(): It
is not safe to rely on the system's timezone settings. You are *required* to
use the date.timezone setting or the date_default_timezone_set() function. In
case you used any of those methods and you are still getting this warning, you
most likely misspelled the timezone identifier. We selected 'UTC' for
'GMT/0.0/no DST' instead in /var/www/php-apc/index.php on line 807, referer:
http://localhost/php-apc/index.php?SCOPE=A&SORT1=H&SORT2=D&COUNT=20&OB=9
[Fri Jan 20 14:28:30 2012] [error] [client 127.0.0.1] PHP Stack trace:,
referer:
http://localhost/php-apc/index.php?SCOPE=A&SORT1=H&SORT2=D&COUNT=20&OB=9
[Fri Jan 20 14:28:30 2012] [error] [client 127.0.0.1] PHP   1. {main}()
/var/www/php-apc/index.php:0, referer:
http://localhost/php-apc/index.php?SCOPE=A&SORT1=H&SORT2=D&COUNT=20&OB=9
[Fri Jan 20 14:28:30 2012] [error] [client 127.0.0.1] PHP   2. date()
/var/www/php-apc/index.php:807, referer:
http://localhost/php-apc/index.php?SCOPE=A&SORT1=H&SORT2=D&COUNT=20&OB=9
Comment 1 Thomas Spuhler 2012-03-11 00:29:47 CET 
Can we now close this bug as the update has been pushed?

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 2 claire robinson 2012-03-11 11:36:56 CET 
Has the problem been addressed Thomas?
Comment 3 Manuel Hiebel 2012-11-05 16:52:41 CET 
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 4 Manuel Hiebel 2012-12-02 14:32:11 CET 
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => WONTFIX