[pkg-php-pear] Laravel status for Trixie

[David Prévot]

Hi Robin,

On 25/01/2025 09:52, David Prévot wrote:
> On 23/01/2025 22:46, Robin Gustafsson wrote:
> […]
>> I hope to have it ready soon. My work-in-progress is on Salsa [1][2], 
>> but some patching and testing remains. Finishing it will be easier now 
>> that phpunit has transitioned.
>>
>> As far as I know, the dependencies are ready in unstable but some were 
>> removed from testing:
[…]
>> * php-nesbot-carbon [5] won't migrate because the test suite 
>> (legitimately) fails on 32-bit archs. It's a known limitation of the 
>> library and was technically acceptable until recently, but seemingly 
>> not anymore. I don't know how to best handle that yet; suggestions 
>> welcome.

I went with [skipping] autopkgtests on those arches (first time I use 
this feature), we’ll see.

skipping: 
https://salsa.debian.org/php-team/pear/php-nesbot-carbon/-/commit/406cfc7a14996791de8abcb0350777cbe487a01e

I updated the package to the latest upstream release (of the 2.x branch) 
in hope the situation would be better, but I think it got worse. A new 
dependency is needed since: php-carbon-doctrine-types, uploaded, and now 
in [NEW] processing. I shipped the code with php-nesbot-carbon 
(arguably, it was already there before the update anyway), and we may 
revert this [hack] once the NEW package has been processed (we may have 
to handle the proper package [relationships] then). I’ve used the same 
kind of hack for [phpunit] about a month ago, and I don’t regret it 
since it would have delayed the PHPUnit 11 transition otherwise (or 
forced us to use an old version until the NEW package got processed). 
The FTP team usually takes care of the NEW backlog before the freeze, 
but I don’t know when or even if it will happen in time for Trixie.

NEW: https://ftp-master.debian.org/new.html (soon, ^F carbon)
hack: 
https://salsa.debian.org/php-team/pear/php-nesbot-carbon/-/commit/e9fd02a83c2bf0ace08fe4c47b526ae677836356
relationships: 
https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks
phpunit: 
https://ftp-master.debian.org/new/php-staabm-side-effects-detector_1.0.5-1.html

>> Bonus points if we package orchestra/testbench-core (>=8.23.4, <9) [6] 
>> to get the php-laravel-framework test suite running in Debian, but 
>> it's not required.

I might give it a try, but it looks big. If I don’t come back with 
something by February 7th (well, when the latest [PHPUnit] 12 may get 
out), I may probably have given up.

PHPUnit: https://github.com/sebastianbergmann/phpunit/milestone/52

Spoiler alert: if the regressions are not on the nightmare scale of the 
PHPUnit 9 -> 10 one, I’d like to give PHPUnit 12 a try for Trixie (we’ll 
see how much autopkgtests are broken once ready in experimental)…

>> [1]: https://salsa.debian.org/php-team/pear/php-laravel-framework
>> [2]: https://salsa.debian.org/php-team/pear/php-laravel-lumen-framework
[…]
>> [5]: https://qa.debian.org/excuses.php?package=php-nesbot-carbon
>> [6]: https://github.com/orchestral/testbench-core/tree/8.x
> 
> I guess some packages may be updated to newer upstream version (but 
> maybe not the latest major), feel free to provide some guidance (what 
> packages can be updated, up to which version, and eventually what major 
> version could be uploaded to experimental if that helps) if we can help 
> you handle tinier tasks.

I followed up with a forked thread: it’s not limited to Laravel.

Regards,

taffit