On Sat, 21 Jul 2018 14:32:36 -0500 "David C. Rankin" wrote:

On 07/21/2018 10:10 AM, Dave Howorth wrote:

...

Now according to https://code.mythtv.org/trac/ticket/12588 that 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 it?

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 contain php5. 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 possible. 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 supported on 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 approach)

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@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 22 Jul 2018 04:44:14 -0500 "David C. Rankin" wrote:

On 07/21/2018 04:19 PM, Dave Howorth wrote:

...

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 contain php5.

Wow, that's a new one. I just check Leap 15 and no php5, Leap 42.3 has all the php5 you can use right in the Updates repo. I am sure somebody is building php5 for SLE as there are still back-offfice fax handling packages like Avantfax that still required php5 on my last check. My eGroupware package does too. But ironically a guy on github move the Gallery2 web-photo album that I and I think Patrick uses it as well. He was able to port Gallery2 to work with php7. If you need 5 and end up with only 7 in 15, the build isn't bad. It's just a go get several cups of coffee whilst you want for all them packages to be built.

Get the skinny on what php version you need, and then I'm sure a proper workaround can be found.

I downloaded the source RPM, and it seems clear there's simply an error in the spec file that hasn't been updated properly. I've reported it to the packman list - I don't know where to report packman bugs. I also don't know how to install an RPM with a faulty spec file (i.e. the requires are wrong)? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 02 Aug 2018 09:14:22 +0200 Per Jessen wrote:

Dave Howorth wrote:

...

I'm trying to bring up mythweb. I've discovered that it's a separate package but am somewhat confused. Most of mythtv is v0.28 from packman and there is a mythweb package that is also 0.28, but there are also 0.27 & 0.26 versions and I'm not clear why. That's minor though, the main problem is that when I try to install mythweb I see an error:

nothing provides apache2-mod_php5

But the only PHP module for apache seems to be v7: apache2-mod_php7 - PHP7 module for the Apache 2.x webserver and that is installed.

Now according to https://code.mythtv.org/trac/ticket/12588 that 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 it?

I would try installing mythweb with --force.

Thanks, Per. It was a packaging problem. packman have updated the package to fix it. But I had so much trouble getting the various parts of myth going that I eventually gave up on it. I got tvheadend working in one day and that seems to be fine. Kodi seems to work OK on my backend box, but seems a bit strange on the Fire TV. At the moment, I've just NFS-exported the recorded videos and watch them on the Fire TV. Even then, it crashed once when I selected 32x FF. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2018-08-02 13:13, Dave Howorth wrote:

I got tvheadend working in one day and that seems to be fine. Kodi seems to work OK on my backend box, but seems a bit strange on the Fire TV. At the moment, I've just NFS-exported the recorded videos and watch them on the Fire TV. Even then, it crashed once when I selected 32x FF.

Kodi can display files it gets via ssh and http - those I have tried. I think I also saw NFS and others. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)