This question already has an answer here:
Can't install symfony/maker-bundle
(1 answer)
Closed 2 years ago.
I tried to install EasyAdmin bundle in my Symfony 5 app:
composer require easycorp/easyadmin-bundle
And got an error:
Using version ^3.1 for easycorp/easyadmin-bundle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Restricting packages listed in "symfony/symfony" to "5.0.*"
Your requirements could not be resolved to an installable set of packages.
Problem 1
- ocramius/proxy-manager 2.9.1 requires composer-runtime-api ^2.0.0 -> no matching package found.
- Installation request for ocramius/proxy-manager (locked at 2.9.1) -> satisfiable by ocramius/proxy-manager[2.9.1].
Additional info:
php -v
# PHP 7.4.12 (cli)
composer -V
# Composer version 1.10.15 2020-10-13 15:59:09
Updating Composer to 2.x version fixed this issue. Follow installation instructions on the Composer site: https://getcomposer.org/download/
Related
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
According laravel manual https://laravel.com/docs/8.x/redis for install predis, need run: composer require predis/predis. When that command is running (for laravel 8) - appear next Error:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- facade/ignition is locked to version 2.4.2 and an update of this package was not requested.
- facade/ignition 2.4.2 requires php ^7.2.5 -> your php version (8.0.0) does not satisfy that requirement.
Problem 2
- facade/ignition-contracts 1.0.1 requires php ^7.1 -> your php version (8.0.0) does not satisfy that requirement.
- nunomaduro/collision v4.3.0 requires facade/ignition-contracts ^1.0 -> satisfiable by facade/ignition-contracts[1.0.1].
- nunomaduro/collision is locked to version v4.3.0 and an update of this package was not requested.
In my composer.json: "php": "^7.2.5|^8.0",
What here is wrong))?
You need to update facade/ignition and nunomaduro/collision first to support PHP 8 in your project.
Running the following commands should update them accordingly.
composer require --dev facade/ignition nunomaduro/collision
composer require predis/predis
i run comand: composer require --dev facade/ignition nunomaduro/collision and have got new Error: Your requirements could not be resolved to an installable set of packages.
Problem 1
- facade/ignition[2.10.0, ..., 2.10.2] require facade/ignition-contracts ^1.0.2 -> found facade/ignition-contracts[1.0.2] but the package is fixed to 1.0.1 (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 facade/ignition ^2.10 -> satisfiable by facade/ignition[2.10.0, 2.10.1, 2.10.2].
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.
I have new laravel 8 project (blog) && use new Vagrant Homestead (with all updates) && i use laravel 8 manual)) may be laravel developers is a little busy and is a little tired to give full instruction in manual). I think may be for Laravel8 Homestead allready is not suitable and need Docker and Sail... But project work (with the exception of predis) Now i use phpredis. May be will try use docker... As for Vagrant&&Homestead - https://laravel.com/docs/8.x/homestead#introduction i don't understand what is problem to use that technology .... god with they)...
I am following along with this tutorial for installing Magento 2.3 on Ubuntu. I am able to get up to the point where I'm supposed to use composer to create a Magento 2 project using this command:
composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.3.0 .
After inputting this command, I get the following output:
Creating a "magento/project-community-edition=2.3.0" project at "./"
Installing magento/project-community-edition (2.3.0)
- Installing magento/project-community-edition (2.3.0): Extracting archive
Created project in /var/www/html/.
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 magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0].
- magento/product-community-edition 2.3.0 requires magento/composer ~1.4.0 -> satisfiable by magento/composer[1.4.0] from composer repo (https://repo.packagist.org) but magento/composer[1.0.2, ..., 1.6.0] from composer repo (https://repo.magento.com) has higher repository priority. The packages with higher priority do not match your constraint and are therefore not installable. See https://getcomposer.org/repoprio for details and assistance.
I have been following the tutorial exactly, however there error does not appear in the tutorial. Does anyone know how to fix this error?
You may find in m2 docs that 2.3.0 doesn't support composer 2
https://devdocs.magento.com/guides/v2.4/install-gde/system-requirements.html
So use
composer self-update --1
I faced with the same issue.
After changing version of the composer:
composer self-update 1.4.0
the problem was solved.
I have 2 different Windows 2016 Servers running Drupal 8 and Drush 9 is installed on both but I have a Drush verison mismatch that I'm trying to fix.
I have this global composer.json file on both servers:
{
"require": {
"drush/drush": "9.*"
}
}
On my Test server, drush --version shows version 9.5.2.
On my Live server, drush --version shows version 9.7.0.
If I run composer global update drush/drush on my Test server, it doesn't update Drush and returns, "nothing to install or update".
I tried this:
composer global require drush/drush:9.7.0
and got this error:
Changed current directory to C:/Users/username/AppData/Roaming/Composer
./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
- Can only install one of: consolidation/site-alias[3.0.0, 1.1.11].
- Can only install one of: consolidation/site-alias[3.0.0, 1.1.11].
- Can only install one of: consolidation/site-alias[3.0.0, 1.1.11].
- drush/drush 9.7.0 requires consolidation/site-alias ^3.0.0#stable -> satisfiable by consolidation/site-alias[3.0.0].
- Installation request for drush/drush 9.7.0 -> satisfiable by drush/drush[9.7.0].
- Installation request for consolidation/site-alias (locked at 1.1.11) -> satisfiable by consolidation/site-alias[1.1.11].
Installation failed, reverting ./composer.json to its original content.
Comparing the line, "name": "consolidation/site-alias", in composer.lock in both environments, I see that Test has 1.1.11 and Live has 3.0.0.
I installed drupal/recommended-project and thought I followed the same steps on both so I'm not sure how they got out of sync. Any ideas?
What is the recommended fix?
I ran composer require drush/drush and now both are on version 10.2.x.
I tried to download google api using composer to a legacy code but, the following error appeared:
composer require google/apiclient:^2.0
./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 google/apiclient 2.0 -> satisfiable by google/apiclient[v2.0.0].
- google/apiclient v2.0.0 requires google/auth 0.8 -> satisfiable by google/auth[v0.8].
- Conclusion: don't install guzzlehttp/psr7 1.4.2
- google/auth v0.8 requires guzzlehttp/psr7 1.2.* -> satisfiable by guzzlehttp/psr7[1.2.0, 1.2.1, 1.2.2, 1.2.3].
- Can only install one of: guzzlehttp/psr7[1.2.0, 1.4.2].
- Can only install one of: guzzlehttp/psr7[1.2.1, 1.4.2].
- Can only install one of: guzzlehttp/psr7[1.2.2, 1.4.2].
- Can only install one of: guzzlehttp/psr7[1.2.3, 1.4.2].
- Installation request for guzzlehttp/psr7 (locked at 1.4.2) -> satisfiable by guzzlehttp/psr7[1.4.2].
Installation failed, reverting ./composer.json to its original content.
What should I do?
Try removing vendor/google and then run composer install again, this worked for me.
Can only install one of: guzzlehttp/psr7[1.2.3, 1.4.2].
Your dependencies led to confusion of two different major versions of the package, but only one can be installed.
The locked at 1.4.2 message means this package has been already installed as per your composer.lock file, and you're trying to install different version not compatible with your existing criteria.
$ composer show -a google/auth | grep psr7
guzzlehttp/psr7 ~1.2
You can check which existing package depends on the locked version by checking the dependency tree:
composer show -t
In some cases, removing composer.lock may help.
Otherwise, to see why (from where) the package is referenced, run:
composer why guzzlehttp/psr7 -t
See also: How to resolve a "Can only install one of:" conflict?
I finally found a solution for me, it works just removing composer.lock!!