mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
2.5 -> 2.6 dropped symfony/console v2. Breaks symfony 2.8 install/update on PHP 7.3 #6182
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @uvimoran on GitHub (Feb 19, 2019).
Bug Report
Summary
doctrine/orm v2.6breaks the installation of symfony 2.8 projects on PHP 7.3 (or updating existing ones) due to the removal of"symfony/console": "~2.5"in composer.jsonThis restriction results in doctrine/orm being stuck at v2.5.14 in symfony 2.8 projects, which until php 7.2 worked fine, but fails with this error if composer update is executed under PHP 7.3:
Which is caused by
doctrine/orm v2.5PHP 7.3 compatibility issues mentioned here.Current behavior
Symfony 2.8 projects cannot be installed or updated on PHP 7.3 as they are stuck with an incompatible version of
doctrine/ormdue to composer dependency restrictions.How to reproduce
php composer.phar create-project symfony/framework-standard-edition my_project_name "2.8.*"symfony/orm v2.5.14being incompatible with PHP 7.3Expected behavior
If it is possible for symfony 2.8 projects to get
doctrine/ormupdated to v2.6 without compatibility issues, fixing this would allow symfony 2.8 projects to be installed or updated in PHP 7.3 environments.@SenseException commented on GitHub (Feb 19, 2019):
Symfony 2.8 is on "Security fixes only" and will be dropped end of this year. It also wasn't updated for PHP 7.3. I isn't reasonable for Doctrine to depend on an old and unsupported console version.
I suggest to update your Symfony project to one of the recent versions.