psr/container 2.0 dependency not compatible
pandooux opened this issue · 7 comments
On a fresh install of laravel 9, composer install symfony/service-contracts:3.0 which require psr/container:2.0 and this last one is not compatible with php-di/php-di requirement for this package :
"Problem 1
- atymic/twitter 3.1.15 requires php-di/php-di ^6.2 -> satisfiable by php-di/php-di[6.2.0, ..., 6.3.5].
- atymic/twitter[3.1.0, ..., 3.1.14] require illuminate/support 6 - 8 -> found illuminate/support[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require. - php-di/php-di[6.2.0, ..., 6.3.5] require psr/container ^1.0 -> found psr/container[1.0.0, ..., 1.x-dev] but the package is fixed to 2.0.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires atymic/twitter ^3.1 -> satisfiable by atymic/twitter[3.1.0, ..., 3.1.15].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require atymic/twitter:*" to figure out if any version is installable, or "composer require atymic/twitter:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content."
Best way I found is to downgrade symfony/service-contract to 2.5 version and then install this package.
Btw, your automated tests are validated because it uses psr/container:1.1.2
+1
I downloaded the packages php-di/php-di and atymic/twitter locally then manually update the psr/container in php-di/php-di to version ^2.0.1. So far nothing is breaking in php-di/php-di package. By updating the version everything worked, there was no more collision with the version in laravel/framework.
+1
Is there a pull request for this yet?