Hi Ondřej, Le Tue, Dec 08, 2020 at 09:28:38AM +0100, Ondřej Surý a écrit :
> I would like to transition the PHP to version 8.0; The timing of this request makes me uneasy: php8.0 has been in Debian for less than a week, and we are a month away from the transition freeze. > it's not such a huge bump as it was with 5.6 -> 7.0 and If I remember correctly, the 7.3 -> 7.4 was not a huge bump either, yet php7.4 packages were in Debian months before the actual transition happen, and it took months for the updated php-defaults to actually migrates into testing. > most of the packages that were compatible with PHP > 7.4 are working just fine with PHP 8.0. That does not match my experience as a maintainer of about a hundred packages relying on PHP. Many upstream are currently releasing updates to fix compatibility with PHP 8.0, and many more have not yet done so. I’m actually surprised to discover this request in the BTS without any prior communication with teams involved in PHP related packaging. For example, PHPUnit 8 as currently available in unstable and testing is expected to run on PHP 8 (thanks to upstream updates less than two weeks ago), yet “Please note that the code coverage functionality is not available for PHPUnit 8.5 on PHP 8.” (from upstream changelog 8.5.12). So shipping PHPUnit 8 with PHP 8 would mean having a major fonctionnality unavailable for the whole Bullseye life cycle. PHPUnit 9 is available from experimental, yet uploading to unstable would mean having to deal with dozens of breakage (in the FTBFS form): https://release.debian.org/britney/pseudo-excuses-experimental.html#phpunit PHPUnit is just one example, but it seems unrealistic to ship version 9 with Bullseye (I really abandonned this option months ago). Other packages will break (and I suspect the number of breakage will be high). This kind of disruptive change would hopefully be better suited early in the release cycle rather than just before the beginning of the freeze. That said, it would be nice to have an updated php-default in *experimental* to help have a grasp of the possible brekages. Regards David
signature.asc
Description: PGP signature
