returns the same result: scriptlet failed, exit status 1, erase failed.
Q1: Where is the scriptlet saved on disk? My hope is that following the steps it is attempting to use to remove that package can be issued by hand and whatever error it’s encountering can be worked around.
Q2: If the package can, eventually, be removed by hand, what other steps would need to be taken to make sure the RPM database is left in the correct state where that package is no longer assumed to be on the system?
I’d like to get several virtual web services – that have been down due to this problem for nearly a week – back up and online.
Thanks. I found the manpage description of “–noscripts” (“A2”) first and was able to remove the mod_php7-related package. That didn’t allow Apache2 to start, though. There was still a complaint that I needed to recompile the apache2-mod_php7. So, I tarred up the /etc/apache2 tree, removed apache2 (yeah, thanks YaST, I know it breaks LAMP), re-installed Apache2, and restored the config files from the tar archive. Virtual servers started right up.
I wish I’d seen “–scripts” (i.e., “A1”) first as I’ve never looked at the scriptlets before. Now I’m curious as to what they do during the “rpm -e” process.