psr/http-message Current Version Issue
CavitU opened this issue · comments
Hi,
Laravel 9 and above, when I try to install the akeneo/api-php-client package, I get the following error:
The reason is that I have version 2.0 of the psr/http-message package. Also when I use --with-all-dependencies (-W) it causes other incompatibilities.
Can you update the version of the psr/http-message package in composer.json to 2.0?
Problem 1
- akeneo/api-php-client[v1.0.0, ..., v1.0.1, v2.0.0, ..., v2.0.1, v3.0.0, v4.0.0, ..., v4.0.2, v5.0.0, v6.0.0, ..., v6.0.1, v7.0, ..., v7.0.1, v8.0.0, v9.0.0, ..., v9.1.2, v10.0.0, v11.0.0, ..., v11.3.0] require psr/http-message ^1.0 -> found psr/http-message[1.0, 1.0.1, 1.1] but the package is fixed to 2.0 (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 akeneo/api-php-client * -> satisfiable by akeneo/api-php-client[v1.0.0, v1.0.1, v2.0.0, v2.0.1, v3.0.0, v4.0.0, v4.0.1, v4.0.2, v5.0.0, v6.0.0, v6.0.1, v7.0, v7.0.1, v8.0.0, v9.0.0, ..., v9.1.2, v10.0.0, v11.0.0, v11.1.0, v11.2.0, v11.3.0].
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 akeneo/api-php-client:*" to figure out if any version is installable, or "composer require akeneo/api-php-client:^2.1" if you know which you need.
Thank you.
+1
+1
Is this a dead project? No one from Akeneo has commented anything on tickets for a while now.
This adds missing composer rules #281
No news about this issue? I'm stuck and cannot use it on Laravel 10. Why there are no activity on this repo since 8 months?
https://api.akeneo.com/php-client/introduction.html
Their documentation says that PHP client support is only "best effort". Seems that best effort is actually quite close to none.
We ended up patching their composer.json and publishing it in our private satis repository. All the tests went through with composer.json changes and we are running the api client in production with that #281