Bug ID 1205983
Summary apache2-mod_php8 uninstall fails if module already removed from sysconfig
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Apache
Assignee apache-bugs@suse.de
Reporter patrick.schaaf@yalwa.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Noticed today (current tumbleweed) that a "zypper remove apache2-mod_php8"
fails, on a system where I already removed "php8" from /etc/sysconfig/apache2
by other means.

error: %preun(apache2-mod_php8-8.1.13-1.1.x86_64) scriptlet failed, exit status
1
error: apache2-mod_php8-8.1.13-1.1.x86_64: erase failed
(1/1) Removing apache2-mod_php8-8.1.13-1.1.x86_64
.........................................................................[error]
Removal of (7)apache2-mod_php8-8.1.13-1.1.x86_64(@System) failed:

The %preun script should have an explicit "exit 0" in the end, or the "a2enmod
-q php8" negative (1) exit value will propagate out, resulting in that failure.

WORKAROUND (so that the package can be uninstalled), is to run "a2enmod php8"
manually once, then the zypper remove. But I feel that is a bit ugly, thus this
bug report.


You are receiving this mail because: