[pkg-php-pear] Upcoming transitions (Symfony, PHPUnit, etc.)

[Athos Ribeiro]

On Tue, Jun 13, 2023 at 01:47:18PM +0200, David Prévot wrote:
>Hi,

Hi David!

>Now that Bookworm has been published, it’s already time to prepare the 
>next transitions as soon as possible in the Trixie release cycle.

Thank you!

>## Symfony 6
>
>The main one IMHO will be symfony from 5 to 6. The package has 
>recently been uploaded to experimental and has been promptly handled 
>by the ftpmasters with the new (build-)dependencies. The experimental 
>pseudo-excuse page is unfortunately not very informative about the 
>amount of breakage we could expect (the debci builds fail to actually 
>install symfony 6, so the results are useless).
>
>https://qa.debian.org/excuses.php?experimental=1&package=symfony
>
>Do you have any idea to represent how reverse dependencies are going 
>to be affected? I can think of at least phpMyAdmin and Laravel that 
>are currently depending on symfony 5, but it would be nice to gather 
>information about other non-ready packages (and fill bugs…).
>
>Given how painful the transition was last time, I intend to fill a 
>transition bug to track blocking issue, but before doing so (and 
>asking the release-team for some help), I’d like to propose a plan of 
>action.

How about using either mass-rebuild
(https://salsa.debian.org/terceiro/mass-rebuild) or ratt
(https://github.com/Debian/ratt) to verify those? As long as the
dependencies are running tests during their package build time, either
of these tools would be helpful to have an idea of what we are looking
into.

If this sounds like a helpful path forward, I would be happy to run it
and post results/fill bugs once the run is complete.

>## PHPUnit 10
>
>It is available in experimental since February (less than a month 
>after its release IIRC), and the experimental pseudo-excuse page is 
>great to show the amount of work needed.
>
>https://qa.debian.org/excuses.php?experimental=1&package=phpunit
>
>The bad news is that over a hundred packages are not ready, so we 
>already know there is a huge amount of work for it. I’ve already 
>uploaded some packages ready upstream and prepared a handful of 
>patches and forwarded some of them upstream, but I won’t be able to 
>take of all of them by myself.
>
>I guess a transition bug could be used again, and we should fill 
>individual bug reports (with patch if possible), or directly fix what 
>we can (even better if the testsuite could run with both phpunit 9 and 
>10, but that will probably not be always possible). If some of the 
>packages you are maintaining are on the list, please consider taking a 
>look at them already.
>
>## Other
>
>I’d like to move php-email-validator from 3 to 4 too, and I guess 
>Robin intend to update Laravel too.
>
>Thanks in advance for sharing your thoughts or more ;).
>
>Cheers
>
>taffit

-- 
Athos Ribeiro