[pkg-php-pear] Upcoming transitions (Symfony, PHPUnit, etc.)
Athos Ribeiro
athoscribeiro at gmail.com
Fri Jun 23 22:15:26 BST 2023
On Fri, Jun 23, 2023 at 09:59:05PM +0200, William Desportes wrote:
>As far as I understand, there was no more change than the composer bump change needed for phpMyAdmin.
>
>So I could introduce an OR to allow both versions.
>And tests pass you said.
Nice! I assumed that the restriction in the composer file was reflecting
other changes since there is a strict version requirement there.
You should be good to pull in the changes then (given you patch the
composer file to allow multiple symfony versions). IIRC, our debhelper
does not support OR statements in composer files, it will just drop the
version restriction from d/control in that case.
>What are the BC breaking changes you expected?
>
>--
>William
>
>Le 23 juin 2023 21:07:25 GMT+02:00, Athos Ribeiro <athoscribeiro at gmail.com> a écrit :
>>On Fri, Jun 23, 2023 at 04:42:43PM +0200, William Desportes wrote:
>>> Hi,
>>>
>>>> Note that this results do not acccount for package installation or DEP8
>>>> tests. Therefore, there may be extra work needed for some packages
>>>> (e.g., phpmyadmin builds passes for symfony 6, but the package depends
>>>> on symfony 5, therefore it is not installable). Still, this should not
>>>> block the transitions/migrations.
>>>
>>> Should I ship this upstream commit as a patch to help the transition or can it wait for an actual upstream update for me to ship a version ?
>>> https://github.com/phpmyadmin/phpmyadmin/commit/66c640dade16f24c7aeb7506bb5d081ab04e106a
>>
>>Since it suggests there is no backwards compatibility (it will not be
>>installable with any of symfony 5 or 6 but with either 5 or 6), it seems
>>it should wait for symfony 6 to land in unstable, otherwise, the package
>>will remain broken until the symfony transition begins.
>>
>>>
>>> --
>>> William
>>
>
>--
>William Desportes
--
Athos Ribeiro
More information about the pkg-php-pear
mailing list