You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
user@notebook:~/PhpStormProjects/my-project $ ddev composer require saintsystems/odata-client
Using version ^0.6.0 for saintsystems/odata-client
./composer.json has been updated
Running composer update saintsystems/odata-client
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires saintsystems/odata-client ^0.6.0 -> satisfiable by saintsystems/odata-client[0.6.0].
- saintsystems/odata-client 0.6.0 requires guzzlehttp/guzzle ^7.0 -> found guzzlehttp/guzzle[dev-master, 7.0.0-beta.1, ..., 7.4.x-dev (alias of dev-master)] but the package is fixed to 6.5.5 (lock f
ile version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
composer [require saintsystems/odata-client] failed, composer command failed: exit status 2. stderr=
The text was updated successfully, but these errors were encountered:
I just cloned the project, removed the hard dependency on Guzzle 7 and it seems to work just fine with 6.5.5?
Is this hard dependency even neccesary given that you can use the ODataClient using any class implementing the interface? Imho guzzle7 shoul be in the suggest section of the composer.json rather than being a hard dependency..
bernhardberger
changed the title
Guzzle dependency in TYPO3 (locked at guzzlehttp/guzzle 6.5.5)
guzzlehttp/guzzle ^7.0 should be "suggest" in composer.json, not a hard-dependency
May 5, 2021
@bernhardberger, I'll take a look at this. I believe you're right that this could be in the suggest section since any class implementing the interface could be used.
The text was updated successfully, but these errors were encountered: