Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 484300

Summary: Please stop providing patches to PHP that don't work
Product: Red Hat Enterprise Linux 5 Reporter: Noel Forbes <noelforbes>
Component: phpAssignee: Joe Orton <jorton>
Status: CLOSED INSUFFICIENT_DATA QA Contact: BaseOS QE <qe-baseos-auto>
Severity: medium Docs Contact:
Priority: low    
Version: 5.5CC: bblaskov, mmahut
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-02-06 09:27:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
"Actual results" screenshot none

Description Noel Forbes 2009-02-05 22:37:59 UTC 
Description of problem:

Red Hat engineers insist on adding patches to PHP that completely break the way scripts behave. They do this even when the PHP development team tells them that this is a bad idea.


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

*


How reproducible:

Always.


Steps to Reproduce:

1. Become an egotistical software developer.
2. Try to patch some software, and have your patch rejected upstream.
3. Patch whatever software projects you can with your patch anyway, despite the fact that upstream says it doesn't work.
4. ???
5. Profit!

  
Actual results:

PHP stops working. A domokun kills several kittens.


Expected results:

PHP works.


Additional info:

WHY ARE YOU ALL SUCH CUNTS, YOU RUINED REDHAT 8, YOU RUINED REDHAT 9, WHY CAN'T YOU BE AS GOOD AS VALHALLA, BECAUSE THAT WAS THE ONLY GOOD RELEASE, AND ALSO IF YOU TRY TO UPGRADE GLIBC ON VALHALLA RPM STOPS WORKING I THINK THIS IS PROBABLY A BUG TOO
Comment 1 Joe Orton 2009-02-06 09:27:51 UTC 
Thanks for the eloquent feedback.

I presume you are referring to the patch to use the system timezone database, which is the subject of recent blog posts?

The more controversial part of this patch (the artificial System/Localtime timezone id) has never been shipped in a supported RHEL or Fedora release.

If you experience any problems with the changes to use the system timezone database in the RHEL php packages, please feel free to report them.
Comment 2 Karel Volný 2009-02-06 09:48:04 UTC 
Created attachment 331104 [details]
"Actual results" screenshot