[php-maint] Bug#845199: dolibarr broken after upgrading from 3.5.8+dfsg1-1 to 4.0.2+dfsg4-1 and purging php5 packages

Raphael Hertzog hertzog at debian.org
Mon Nov 21 13:56:05 UTC 2016

On Mon, 21 Nov 2016, Jean-Marc wrote:
> > Please show the output of:
> > $ ls -lR /etc/apache2
> To not make the report too big and unreadable, I do not copy the output.
> But I suppose you want to know if /etc/apache2/mods-enabled contains a symlink to activate php7 module.
> I found this in /etc/apache2/mods-available:
> [...]
> -rw-r--r-- 1 root root  867 oct 15 17:11 php7.0.conf
> -rw-r--r-- 1 root root  102 oct 15 17:11 php7.0.load
> But no link related to them into /etc/apache2/mods-enabled.
> Something missing in the php7 install.
> Or something removing this in php5 purge.
> Do you know the right way to activate php7 ?

Run "a2enmod php7.0"

But this should be done automatically by the installation of

I guess that it was not done because php5 was still enabled and the two
are conflicting. But when php5 got removed, nothing enabled php7.0...

I'm putting PHP maintainers in copy. Dear PHP maintainers, is there no
mechanism that could be put in place for this? Given the new versioning
scheme, this problem is likely to become more frequent...

Feel free to reassign this bug to track a possible solution to this
problem. It might require to modify packages in jessie to make sure
that the package removal activates something (via trigger or some other
hook mechanism).

Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

More information about the pkg-php-maint mailing list