I'm trying to install the package erusso7/redsys-rest but it shows this error:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Can only install one of: guzzlehttp/guzzle[7.4.3, 6.5.x-dev].
- Can only install one of: guzzlehttp/guzzle[6.5.x-dev, 7.4.3].
- Can only install one of: guzzlehttp/guzzle[6.5.x-dev, 7.4.3].
- erusso7/redsys-rest 0.1.2 requires guzzlehttp/guzzle ^6.0 -> satisfiable by guzzlehttp/guzzle[6.5.x-dev].
- Installation request for erusso7/redsys-rest ^0.1.2 -> satisfiable by erusso7/redsys-rest[0.1.2].
- Installation request for guzzlehttp/guzzle (locked at 7.4.3, required as ^7.0.1) -> satisfiable by guzzlehttp/guzzle[7.4.3].
Installation failed, reverting ./composer.json to its original content.
I've tried all the solutions in the other questions related to this topic but nothing seems to work.
I'm using Laravel/Backpack and I think it uses guzzle too and that may be causing the issues with the versions, any help please? I can give more info about my composer files if needed. Thank you.
I Want to install laravel app and I user composer like this to install packages
composer install
And I get this error
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for doctrine/dbal 3.3.5 -> satisfiable by doctrine/dbal[3.3.5].
- doctrine/dbal 3.3.5 requires composer-runtime-api ^2 -> no matching package found.
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
- It's a private package and you forgot to add a custom repository to find it
Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
I search any solution on the web without succes.
I'm on ubuntu server 20.04
Thank you
you have to upgrade the composer to version ^2.
run this command before "composer install"
=> composer self-update --2
I am trying to install google/apiclient:^2.0 in my project and it gives me errors as below,
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires laravel/framework 5.8.*, found laravel/framework[v5.8.0, ..., 5.8.x-dev] but the package is fixed to v7.30.4 (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.
Problem 2
- Root composer.json requires google/apiclient 2.0 -> satisfiable by google/apiclient[v2.0.0].
- google/apiclient v2.0.0 requires monolog/monolog ^1.17 -> found monolog/monolog[1.17.0, ..., 1.x-dev] but the package is fixed to 2.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.
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.
Please help me out with the same.
Thanks & Regards
I have problems installing FOS/ckeditor-bundle after succesfully removing egeloen/ckeditor-bundle.
(I did it the way suggested in: https://github.com/FriendsOfSymfony/FOSCKEditorBundle/blob/HEAD//docs/migration.rst )
The output is:
composer require friendsofsymfony/ckeditor-bundle
Using version ^2.1 for friendsofsymfony/ckeditor-bundle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- friendsofsymfony/ckeditor-bundle 2.1.0 conflicts with sebastian/exporter[1.2.2].
- friendsofsymfony/ckeditor-bundle 2.1.0 conflicts with sebastian/exporter[1.2.2].
- friendsofsymfony/ckeditor-bundle 2.1.0 conflicts with sebastian/exporter[1.2.2].
- Installation request for friendsofsymfony/ckeditor-bundle ^2.1 -> satisfiable by friendsofsymfony/ckeditor-bundle[2.1.0].
- Installation request for sebastian/exporter == 1.2.2.0 -> satisfiable by sebastian/exporter[1.2.2].
Installation failed, reverting ./composer.json to its original content.
I also tried with:
composer require friendsofsymfony/ckeditor-bundle:1.2.0
But I get the same error. Is there a special version for symfony 3.4?
Some of your other dependencies probably require sebastian/exporter < 2.0 which friendsofsymfony/ckeditor-bundle does not support.
You can get the list of packages that require sebastian/exporter with
composer why sebastian/exporter
which then you can use to upgrade (so they require newer sebastian/exporter) or remove packages to enable installation of your bundle.
My Composer has just told me that a certain package foo/bar is abandoned.
However, it's not listed in my composer.json, so therefore some other package has that as a dependency.
How can I get Composer to show me this?
For example, it might tell me that my root composer.json requires a/b, which requires c/d which in turn requires the offending foo/bar.
composer show --tree
Lists your dependencies as a tree. If you pass a package name it will show the dependency tree for that package.
See documentation for more: https://getcomposer.org/doc/03-cli.md#show
When you have the package name of a deep dependent, and you want to know to what root dependent it belongs, use composer depends.
$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 0 installs, 0 updates, 0 removals
Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead.
Writing lock file
Generating autoload files
$ composer depends guzzle/guzzle
aws/aws-sdk-php 2.8.31 requires guzzle/guzzle (~3.7)
Your comment on another answer suggested you were trying to untangle a dependency problem. Here's an example using depends to do that:
$ composer require phan/phan
Using version ^1.1 for phan/phan
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for composer/xdebug-handler (locked at 1.1.0) -> satisfiable by composer/xdebug-handler[1.1.0].
- phan/phan 1.1.0 requires composer/xdebug-handler ^1.3 -> satisfiable by composer/xdebug-handler[1.3.0].
- phan/phan 1.1.1 requires composer/xdebug-handler ^1.3 -> satisfiable by composer/xdebug-handler[1.3.0].
- phan/phan 1.1.2 requires composer/xdebug-handler ^1.3 -> satisfiable by composer/xdebug-handler[1.3.0].
- phan/phan 1.1.3 requires composer/xdebug-handler ^1.3 -> satisfiable by composer/xdebug-handler[1.3.0].
- phan/phan 1.1.4 requires composer/xdebug-handler ^1.3 -> satisfiable by composer/xdebug-handler[1.3.0].
- Conclusion: don't install composer/xdebug-handler 1.3.0
- Installation request for phan/phan ^1.1 -> satisfiable by phan/phan[1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4].
Installation failed, reverting ./composer.json to its original content.
$ composer depends composer/xdebug-handler
friendsofphp/php-cs-fixer v2.12.1 requires composer/xdebug-handler (^1.0)
So, I wanted phan/phan, but that failed because of a version problem on composer/xdebug-handler, which is not a package I've ever asked for explicitly.
Then I ask what packages "depend" on composer/xdebug-handler and discover that friendsofphp/php-cs-fixer needs it (and I know about that package, it's a root dependent).
Then I note that phan/phan wants composer/xdebug-handler:^1.3 and (from the depends) that friendsofphp/php-cs-fixer allows me to have version 1.3. So now I just do an update:
$ composer update composer/xdebug-handler
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 0 installs, 1 update, 0 removals
- Updating composer/xdebug-handler (1.1.0 => 1.3.0): Loading from cache
Writing lock file
Generating autoload files
$ composer require phan/phan
Using version ^1.1 for phan/phan
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 5 installs, 0 updates, 0 removals
- Installing sabre/event (5.0.3): Loading from cache
- Installing microsoft/tolerant-php-parser (v0.0.15): Loading from cache
- Installing netresearch/jsonmapper (v1.4.0): Loading from cache
- Installing felixfbecker/advanced-json-rpc (v3.0.3): Loading from cache
- Installing phan/phan (1.1.4): Loading from cache
phan/phan suggests installing ext-ast (Needed for parsing ASTs (unless --use-fallback-parser is used). php-ast ^0.1.5|^1.0.0 is needed.)
Writing lock file
Generating autoload files
Use composer depends with the --tree option.
Example: say I want to see a tree structure of what packages depend on the doctrine/data-fixtures package up to the _root_ package.
composer depends --tree doctrine/data-fixtures
Output:
doctrine/data-fixtures 1.4.0 Data Fixtures for all Doctrine Object Managers
└──doctrine/doctrine-fixtures-bundle 3.3.0 (requires doctrine/data-fixtures ^1.3)
└──__root__ (requires (for development) doctrine/doctrine-fixtures-bundle ^3.3)
The question has already been answered, but Composer offers, in my opinion, a more eloquent way, which hasn't been mentioned before: depends command alias why.
composer why aims to answer the "Why is this package installed?" question, instead of "Which packages depend on this package?", which I find much easier to remember.
Being an alias, the why command behaves the same as depends and both aforementioned options still apply:
--recursive (-r): Recursively resolves up to the root package;
--tree (-t): Prints the results as a nested tree, implies -r.
I don't know of a nice way to solve this but I ran into the same problem. A package I've never heard of was warning that it was abandoned. My solution was to search the composer.lock file for the abandoned package name. It will appear in require or require-dev for the package that depends on it.
In my case it was several levels, package A depended on package B that depended on abandoned package C. Once I identified what package A was then composer show --tree package/a showed the abandoned package in the tree output