Summary: | =www-apps/mythweb-0.26.0 incompatible with PHP 5.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jim Faulkner <dogshu> |
Component: | [OLD] Server | Assignee: | MythTV Maintainers <mythtv+disabled> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | dogshu, gregg.casillo, web-apps |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jim Faulkner
2013-04-07 21:55:53 UTC
I ran into something similar: http://www.mythtv.org/pipermail/mythtv-users/2013-January/346189.html A few things: 1. If you just rename the ebuild you aren't bumping anything. You need to populate the BACKPORTS variable in the build, and point the SRC_URI to a tarball containing the corresponding patches, which you have to obtain from git. 2. Upstream hasn't touched anything related to this in ages, so bumping will likely do you little good. Just look at their git log (I might still push out a bump just for its own sake). The patch is likely what is doing all the work. The changes I listed also work, but I'm not sure that either is a proper fix. I need to research this a bit more before I put anything into portage. It almost seems like some kind of php bug (you get errors unless you set the errors to maximum verbosity, and then you don't get errors). I just ran into this after an upgrade from php-5.3 to 5.4. I added the two php_value lines Richard prescribed in the mythtv-users mailing list to my mythweb apache config file, and it fixed the problem. What's strange is that these values appear to be set in the php.ini file for php-5.4. Is there a reason why they have to be set in my apache config file for mythweb? Looking forward to a better fix for this. (In reply to Gregg Casillo from comment #2) > Is there a > reason why they have to be set in my apache config file for mythweb? There is certainly a reason. There probably shouldn't be a reason. This seems likely to be a PHP bug, but I have no idea. It is a heisenbug at the very least. This ebuild is no longer in the tree. Unfortunately mythweb support is a bit sporadic here and upstream. |