On Sat, 21 Jul 2018 14:32:36 -0500
"David C. Rankin" <drankinatty(a)suddenlinkmail.com> wrote:
On 07/21/2018 10:10 AM, Dave Howorth wrote:
Now according to
problem was encountered three years ago and was fixed in mythweb
two years ago apparently in v0.27. So 0.28 should be OK.
So why am I seeing the error and is there any way I can work around
This is the bane of the php-world at the moment.
Ah, thanks for the informative reply, David. I know nothing about PHP
(being a Perlite who spits at PHP :)
(I don't have myth, so I can't give specifics,
but I can frame the
issue hopeully). There are a LOT of php applications built using
php5. There have been many changes between php5 and php7. Some of the
larger php apps have not yet been fully ported to php7 which causes
no end of grief. (you can have both php5 and php7 installed, but you
have to pick 1 for apache.
The issue in this case seems to be that the original source (mythweb
v0.28) has been modified for php7 but the packman package of same has a
dependency on php5, and the standard openSUSE repositories don't
So either the packman package was built from some source and is lying
about its version, or else it has an erroneous dependency in its
packaging. I have no idea how to determine which, nor where to bug
report packman packages, nor how to monkey patch them to work if
i.e. I know very little about mythweb, very little about PHP, very
little about packman and very little about rpm packages in general.
Add to this the moving target of how php was to be
apache 2.4. apache_mod_php was deprecated with 2.2, With 2.4,
depending on the threading model you were to use, you were either
pushed to mod_mpm_event/mod_mpm_prefork or mod_proxy_fcgi. The other
pushed alternative was php-fpm with mod_proxy and mod_proxy_fcgi.
Now I haven't kept up with the latest, but if you are saying there is
a apache2-mod_php7 for apache 2.4, then it looks like we have a third
option (and somebody relented and said OK, we will support the 2.2x
Ah, now I do remember seeing something about using FCGI in preference
to other approaches for multithreading PHP, but I don't remember where
or what the context was. So maybe when I do persuade mythweb to ask for
an apache interface to php7, there's more than one way to meet that
requirement? Or maybe the whole question has moved on as you say!
So depending on how mythTV is put together, where all
the pieces come
from, etc.. it wouldn't be surprising for some incarnations to be
php5 compliant while others are php7 compliant.
Sorry this isn't a fix, but it at least provides a filter to look at
why a php app may be having problems.
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org