Comment 3 for bug 1566491

On 05.04.2016 [22:34:01 -0000], Maciej Puzio wrote:
> Thank you for a quick response. Yes, I can find "ERROR: php5 module
> already enabled, not enabling PHP 7.0" in /var/log/apt/term.log. Not
> sure if this is relevant, but before I ran "a2enmod php7.0", directory
> /etc/apache2/mods-enabled contained a link php7.0.load, but did not
> contain php7.0.conf.

I believe that is all tied together. php7.0 and php5 conflict with one
another in apache's configuration. So probably the php7.0 configuration
stopped at that point. Not 100%, though, and I will verify that things
aren't broken once the archive has been cleaned up.

> On my machines php5 was installed as a dependency of phpldapadmin. The
> issue came to light as a result of a mundane update:

Right, but you're running a not-yet-released Ubuntu :) So you are just
getting caught up in the middle of this massive migration from php5 ->
php7.0. End-users that release to 16.04 final won't see php5 at all (it
will not be available), so phpldapadmin will pull in libapache2-mod-php
which should properly configure the php7.0 version. This happens, e.g.,
in a fresh xenial install (one that did not previously have php5
installed).