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
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.
Created attachment 331104 [details] "Actual results" screenshot