Inconsistent naming of PHP7 apache module

Status changed to 'Confirmed' because the bug affects multiple users.

Hello and thank you for filing this bug!

I'm wondering if this might actually be an upstream PHP7.0 bug. Would you be able to file a bug at https://bugs.php.net/ referring to this issue to see what their perspective is?

Thanks,
Nish

Correct me if I'm wrong but a2enmod is a Debian/Ubuntu thing not related to the upstream, this appears to be due to the new naming scheme Ubuntu has adopted. Previously PHP was php5 now Ubuntu has add php7.0, the addition of .0 is an Ubuntu thing and inconsistent to previous releases.

s/Ubuntu/Debian/, but yes, you're right!

So, I think the conflict is that apachectl looks at the actual module's name (in this case php7) while a2{en,dis}mod look at what's in /etc/apache2/mods-available (in this case php7.0). Obviously that they disagree and thus seem incompatible is not the right approach, but I'd like to get Ondřej's insight here, as we'll presumably need to fix Debian similarly.

I know the php7.0 naming is very intentional (note I believe we also had a php5.6 package in Ubuntu at one point or another). I wonder if we should be patching the upstream in the Debian/Ubuntu build to make the module internal name be php7.0 in the code as well, so they at least agree?

@rwky: would you be able to file this as an issue with Debian?

There's no bug. The upstream PHP module is named php7_module, but the package is named php7.0. You can have more php7_module providers - libapache2-mod-php7.0 | libapache2-mod-php7.1 and in future libapache2-mod-php7.2, but only one php7_module can be enable at the same time (related to internal apache2 module structures). Filling bug with Debian would be futile, as I would only close it with the same explanation as here.

Fair enough I'll update the ansible issue.