However, purging apache2 would not remove /etc/apache2, since /etc/apache2/mods-available belongs to several packages, including libapache2-mod-php8.1, which owns
/etc/apache2/mods-available/php8.1.{conf,load}.
Is there any chance you did intentionally remove /etc/apache2 after purging the package (e.g., by running `rm -rf /etc/apache2`? This would break the (re)installation patch for libapache2-mod-php8.1. In this case, you can fix the issue by purging libapache2-mod-php8.1 and re-installing it.
I am setting this bug as incomplete until we hear back from you, since at this point, I am not able to assess if this is a bug, or a configuration issue. Once you provide more information, if you still believe this is a bug, please, move the status of the issue back to new. In this case, please, also provide a reproducer for your issue.
Hello Erickson,
It seems that you manually modified the following files
/etc/apache2/ mods-available/ php8.1. conf mods-available/ php8.1. load
/etc/apache2/
then removed php*, and purged apache2.
However, purging apache2 would not remove /etc/apache2, since /etc/apache2/ mods-available belongs to several packages, including libapache2- mod-php8. 1, which owns mods-available/ php8.1. {conf,load} .
/etc/apache2/
Is there any chance you did intentionally remove /etc/apache2 after purging the package (e.g., by running `rm -rf /etc/apache2`? This would break the (re)installation patch for libapache2- mod-php8. 1. In this case, you can fix the issue by purging libapache2- mod-php8. 1 and re-installing it.
I am setting this bug as incomplete until we hear back from you, since at this point, I am not able to assess if this is a bug, or a configuration issue. Once you provide more information, if you still believe this is a bug, please, move the status of the issue back to new. In this case, please, also provide a reproducer for your issue.
Thanks!