Bug#1114729: apache2 delivers .php files uninterpreted in clear during apt dist-upgrade

David Prévot <[email protected]> Mon, 19 Jan 2026 15:57:46 +0100
Newsgroups gmane.linux.debian.devel.apache
Message-ID <aW5GarbhnTTxEyyw__13537.1263882675$1768834765$gmane$org@brocoli.tilapin.org>
Hi,

Le Sat, Dec 13, 2025 at 08:54:04AM +0100, Sebastiaan Couwenberg a écrit :
> On Fri, 26 Sep 2025 09:03:19 +0200 Moritz Schlarb <[email protected]> wrote:
> > please tell us how exactly are you running the PHP interpreter in your apache
> > (mod_php or PHP-FPM or...)?
> 
> I've noticed the same with upgrades of systems at $DAYJOB where libapache2-mod-php8.4 did not get enabled automatically after the upgrade of libapache2-mod-php.
> 
> The upgrade procedure for those systems added steps to explicitly enable it:
> 
>  a2enmod php8.4
>  service apache2 restart

Thanks for the feedback. The initial bug report also seem to imply that
the issue happens “During the run of apt dist-upgrade”, i.e., during a
major upgrade. Maybe this issue should rather be documented in the
release notes actually, and it may not be specific to PHP either.

Regards,

taffit
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAmluRmcACgkQBYwc+UT2
vTxCHQf/dqD1O/ymQjS0ye+OAmV1kRk2W1u0a3LxBxTG58urBTOd5zJa3jXCQSHz
L0sjX5+L7fY+t+EX2Sto5QsHZAUJ1oxjYOH1gsTSdP1Jci2VB5CZDLxTgyr9uwaz
h2jdVnS1uT3ZuexfJKDB+shJjaYyN1pWcTn8aWNFNypuM7CTPhMNXjjOoQhTLvyS
QCSZxMftX8TuYm5fRzpHprDWx3rZcY1GjIpgHnwcRtF6LtQcejftriTfLdNH+c3s
ugwrLLvc03brnku0sFzd4IgisRTAyuZ6kVJ0xkw2Z9iQ9GxqSt6tnowMjx950Wep
T631LUcgdmizzxtbqzSvQK2W+Np8KQ==
=34FI
-----END PGP SIGNATURE-----