Citeren Bjoern Voigt :

Bjoern Voigt wrote:

...

Since last TW snapshot 20200301**my apache2/php7-fpm setup does not work anymore. I found a solution. During "zypper dup" mod_php7 was automatically activated by postinstall script of apache2-mod_php7. The solution:

# a2dismod php7 # systemctl restart apache2

or

# zypper rm apache2-mod_php7

You may want to add # zypper al apache2-mod_php7 This will prevent accidentally installing and enabling it again. I've seen similar breakage in the past too, where the 'event' MPM failed to start because mod_php was enabled in a %post script.

Greetings, Björn

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Citeren Bjoern Voigt :

Arjen de Korte wrote:

...

You may want to add

# zypper al apache2-mod_php7

This will prevent accidentally installing and enabling it again. I've seen similar breakage in the past too, where the 'event' MPM failed to start because mod_php was enabled in a %post script. Thanks, but this breaks the PHP7 updates and I have to install them manually with

# zypper in --download-only apache2-mod_php7; rpm --justdb -Uvh /var/cache/zypp/packages/repo-oss/x86_64/apache2-mod_php7-7.4.3-1.1.x86_64.rpm --nodeps" (example)

My "zypper dup" command line also solves the problem:

# zypper ref; zypper dup; a2dismod php7

In my case the Nextcloud server has a dependency to mod_php7 but in fact Nextcloud works with PHP-FPM too:

# rpm -qR nextcloud | grep mod_php mod_php_any >= 7.2.0 mod_php_any < 7.5.0

The 'mod_php_any' dependency is a nasty one. Ideally the 'php7-fpm' package should also provide 'mod_php_any' and conflict with 'apache2-mod_php7' to prevent this situation from happening in the first place. I'm not sure why we don't have this already, but it probably has to do with the fact that 'php7-fpm' will not provide a working solution out of the box while 'apache2-mod_php7' does. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 3/5/20 4:34 AM, Arjen de Korte wrote:

The 'mod_php_any' dependency is a nasty one. Ideally the 'php7-fpm' package should also provide 'mod_php_any' and conflict with 'apache2-mod_php7' to prevent this situation from happening in the first place. I'm not sure why we don't have this already, but it probably has to do with the fact that 'php7-fpm' will not provide a working solution out of the box while 'apache2-mod_php7' does.

As a php user, i would prefer (and expected) that a package like nextcloud only has dependencies for the php modules it actually uses in its code; not modules that php needs to "connect" to a given web server, or any other particular use case. How to connect php to a web server is a job for the wiki, imho. People could be just writing cli scripts and not even want a web server, much less apache deps. BTW, why does nginx use the 'nginx' user and group, instead of 'wwwrun' and 'www'? Thanks, ITwrx -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, Mar 05, 2020 at 11:49:30AM +0100, Manfred Hollstein wrote:

On Wed, 04 Mar 2020, 12:58:12 +0100, Bjoern Voigt wrote: To be honest, this does not look right to me. A package should not change a working configuration under the hood by running some post-script. This sounds similar to the changes from installing the nss-mdns package... Just because I install a package does not necessarily mean I'm going to use it now. I'd create a bug report.

I tend to agree. Petr -- Have a lot of fun! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org