Bugzilla – Bug 105934
ampache requires mod_php
Last modified: 2005-08-25 23:19:33 UTC
The package "ampache" requires "mod_php", but there is no package providing it.
% rpm -q --provides apache2-mod_php4 mod_php libphp4.so apache2-mod_php4 = 4.3.11-0.1 Where do/did you see the problem?
Then probably the problem is, that apache2-mod_php4 is missing from the installer: roxen# find . | grep -i php | grep -i apache ./inst-source/CD1/suse/i586/apache2-mod_php5-5.0.4-7.i586.rpm ./inst-source/CD1/suse/x86_64/apache2-mod_php5-5.0.4-7.x86_64.rpm ./inst-source-java/suse/i586/mod_php4-apache2-4.4.0-3.i586.rpm ./inst-source-java/suse/x86_64/mod_php4-apache2-4.4.0-3.x86_64.rpm And this might be the answer for bug #105938 as well.
it's on DVD1 zgrep apache2-mod_php4 /dist/install/SUSE-10.0-DVD-Beta2/CD1/ARCHIVES.gz ./DVD1/suse/i586/mod_php4-apache2-4.4.0-3.i586.rpm: [...] Andreas, is this a bug?
Problem: mod_php4-apache2 isn't on the OSS version. Rudi?
And apache2-mod_php4 isn't there as well.
*** Bug 105929 has been marked as a duplicate of this bug. ***
pay/apache2-mod_php4 pay/mod_php4-core pay/mod_php4-servlet mod_php4 is not OSS, that's why. Some modules are not. and ampache is not on the oss version because it depends on php4 ... aj: ok to close ?
*** Bug 105938 has been marked as a duplicate of this bug. ***
whenever there is a consideration to drop php4, ampache should not matter. It should work with php5 just as well.
Sure, but php5 doesn't have all the features of php4 yet. So keeping it for SUSE Linux 10.0 is a must in my point of view. Anyway, that's not the topic of this bug ;)
Let's include both.
ok: ampache is on DVD9 and ftp-oss php4 is on CD, DVD and ftp-oss php5 is on DVD and ftp-oss
Still a problem in beta3. #### YaST2 conflicts list - generated 2005-08-25 23:30:31 #### mod_php not available Required by: ampache requires mod_php Conflict Resolution: ( ) Remove the Referring Package Do Not Install ampache ( ) Ignore Conflict and Risk System Inconsistencies #### YaST2 conflicts list END ###
I did add comment #15 and close the bug today, clearly after beta3 ... this has been fixed in the config today and will be fixed in beta4.