On production machine which most probably using php5-fpm + event or worker Apache2 MPM, this bug forcefully reinstall libapache2-mod-php5 after (unattended = minor) PHP5 update.
The direct effect of this is reinstalling mpm_prefork !
Simply stated: unattended-upgrades breaks LAMP installation by not resolving dependencies correctly.
Could maintainer have a look on this please?
I've been hit every time php5 package is updated.
Current workaround:
```
Package: libapache2-mod-php5 libapache2-mod-php5filter
Pin: origin ""
Pin-Priority: -1
```
Note: may add php5-cgi, since the auto-installation of this package is not as disastrous.
Note: it's hard to *debug* this bug (unless setting XUUPOPT="-d" inside /etc/cron.daily/apt) and may well be left unnoticed in some case... until website traffic increases implying the prefork MPM extra-load.
Side question: why would unattended-upgrades provide its own (not-apt-based) resolution mechanism in the first place?
On production machine which most probably using php5-fpm + event or worker Apache2 MPM, this bug forcefully reinstall libapache2-mod-php5 after (unattended = minor) PHP5 update.
The direct effect of this is reinstalling mpm_prefork !
Simply stated: unattended-upgrades breaks LAMP installation by not resolving dependencies correctly.
Could maintainer have a look on this please?
I've been hit every time php5 package is updated.
Current workaround: mod-php5filter daily/apt) and may well be left unnoticed in some case... until website traffic increases implying the prefork MPM extra-load.
```
Package: libapache2-mod-php5 libapache2-
Pin: origin ""
Pin-Priority: -1
```
Note: may add php5-cgi, since the auto-installation of this package is not as disastrous.
Note: it's hard to *debug* this bug (unless setting XUUPOPT="-d" inside /etc/cron.
Side question: why would unattended-upgrades provide its own (not-apt-based) resolution mechanism in the first place?