[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]

Hi,

On Tue, 06 Dec 2016, Ondřej Surý wrote:
> the problem in any automatic solution is in the fact there are two kind
> of PHP users:
> 
> 1. php got pulled as dependency and is used in default config (e.g. end
> users)
> 2. php was installed by hand and is carefully configured (e.g. web
> hostings)
> 
> Any automatic switch for group 1 would be ok, but it probably won't be
> ok for group 2.

The problem is not the lack automatic switch, the package was working fine
with PHP5. But when the user dropped PHP5 because after all he had PHP7
already, then the application stopped working.

So what I was suggesting is that something enables the latest available
PHP (i.e. 7 currently) when the currently enabled PHP (i.e. 5 in this
case) is being removed.

This should be doable with postrm code and possibly a trigger to watch
for removal of PHP5.

Cheers,
-- 
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/