This is the error message I'm getting when I try a composer update.
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for ****/silex-php 1.1 -> satisfiable by ****/silex-php[v1.1].
- ****/silex-php v1.1 requires symfony/framework-bundle ~2.3 -> satisfiable by symfony/framework-bundle[2.3.x-dev, 2.4.x-dev, 2.5.x-dev, 2.6.x-dev, 2.7.x-dev, 2.8.x-dev] but these conflict with your requirements or minimum-stability.
I want any symfony/framework-bundle that is a) stable and b) greater than 2.3.
This error went away by itself.
Sometimes it help to remove the whole vendor folder and try again instead of trying to debug this very specific dependency problems.
Related
I'm using following command
composer require propel/propel-bundle
and getting the following error
Problem 1
- propel/propel-bundle[1.5.0, ..., 1.5.2] require symfony/framework-bundle ^2.8.2 -> found symfony/framework-bundle[v2.8.2, ..., v2.8.52] but it conflicts with your root composer.json require (5.4.*).
- Root composer.json requires propel/propel-bundle ^1.5 -> satisfiable by propel/propel-bundle[1.5.0, 1.5.1, 1.5.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 am attempting to update from 8.9.13 to 9.0.1 (intending to migrate to 9 in general, not specifically 9.0.1)
Its on a composer site.
I'm running:
composer require drupal/core:^9.0.1 drupal/core-dev:^9.0.1 --update-with-all-dependencies
I keep running up against the following errors:
Problem 1
- drupal/loft_data_grids is locked to version 1.3.0 and an update of this package was not requested.
- drupal/loft_data_grids 1.3.0 requires drupal/core ~8.0 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but it conflicts with your root composer.json require (^9.0.1).
Problem 2
- drupal/upgrade_status is locked to version 3.4.0 and an update of this package was not requested.
- drupal/upgrade_status 3.4.0 requires drupal/core ^8.7.0 -> found drupal/core[8.7.0-alpha1, ..., 8.9.x-dev] but it conflicts with your root composer.json require (^9.0.1).
Problem 3
- drupal/backup_migrate is locked to version 5.0.0-rc2 and an update of this package was not requested.
- Conclusion: don't install symfony/process[v4.4.0-BETA1] | install symfony/process[v3.4.39] (conflict analysis result)
- Conclusion: don't install symfony/process v3.4.39 (conflict analysis result)
- Conclusion: don't install drupal/core 9.1.4 (conflict analysis result)
- Conclusion: don't install symfony/process v4.4.0-BETA2 (conflict analysis result)
- Conclusion: don't install symfony/process v4.4.0-RC1 (conflict analysis result)
- Conclusion: don't install symfony/process v4.4.0 (conflict analysis result)
.... remvoed for brevity of symfony/profess v4.4.1 - 4.4.2 - etc until 4.4.19
- Conclusion: don't install symfony/process v4.4.19 (conflict analysis result)
- drupal/recaptcha 3.0.0 requires drupal/captcha ^1.0.0-alpha1 -> satisfiable by drupal/captcha[1.1.0].
- drupal/recaptcha is locked to version 3.0.0 and an update of this package was not requested.
- drush/drush is locked to version 10.3.6 and an update of this package was not requested.
- drupal/captcha 1.1.0 requires drupal/core ^8.8 || ^9 -> satisfiable by drupal/core[9.0.1, ..., 9.2.x-dev].
- drupal/core[9.0.1, ..., 9.2.x-dev] require symfony/process ^4.4 -> satisfiable by symfony/process[v4.4.0-BETA1, ..., 4.4.x-dev].
- Conclusion: don't install symfony/process 4.4.x-dev (conflict analysis result)
Could anyone help enlighten me please?
Thanks in advance!
Carefully read the problem statements, for Problem 1:
- drupal/loft_data_grids 1.3.0 requires drupal/core ~8.0
This indicates that Loft Data Grids has a constraint to Drupal 8.x, hence the error. When you follow the link, you will also see that that project doesn't have a Drupal 9 release, so that is blocking your upgrade already. Try and apply the patches from either Drupal 9 Readiness or Automated Drupal 9 compatibility fixes.
The same applies to Problem 2 Upgrade Status, though you wouldn't need this module in Drupal 9, so consider removing this one before upgrading:
- drupal/upgrade_status 3.4.0 requires drupal/core ^8.7.0
I advice you first to fix the module constraints in general that are not yet ready for Drupal 9 before even attempting to run the Composer upgrade command to Drupal 9, as they will all halt the upgrade in similar way.
Please see Apply Drupal 9 compatibility patches with Composer and Require v8 only contrib module with v9 patch to get around Drupal 8 modules that aren't tagged yet with a Drupal 9 release, but have a patch that can be applied.
I am trying to understand how to upgrade a LTS8 installation installed with
composer create-project typo3/cms-base-distribution myProject ^8
to LTS 9.5.
When I follow the documentation and do
composer require typo3/cms-backend:^9.5 typo3/cms-core:^9.5 typo3/cms-extbase:^9.5 typo3/cms-extensionmanager:^9.5 typo3/cms-filelist:^9.5 typo3/cms-fluid:^9.5 typo3/cms-frontend:^9.5 typo3/cms-install:^9.5 typo3/cms-recordlist:^9.5 --update-with-dependencies
I get
Your requirements could not be resolved to an installable set of packages.
Problem 1
- typo3/cms-rte-ckeditor v8.7.19 requires typo3/cms-core 8.7.19 -> satisfiable by typo3/cms-core[v8.7.19] but these conflict with your requirements or minimum-stability.
- typo3/cms-rte-ckeditor v8.7.19 requires typo3/cms-core 8.7.19 -> satisfiable by typo3/cms-core[v8.7.19] but these conflict with your requirements or minimum-stability.
- typo3/cms-rte-ckeditor v8.7.19 requires typo3/cms-core 8.7.19 -> satisfiable by typo3/cms-core[v8.7.19] but these conflict with your requirements or minimum-stability.
- Installation request for typo3/cms-rte-ckeditor (locked at v8.7.19, required as ^8.7.10) -> satisfiable by typo3/cms-rte-ckeditor[v8.7.19].
Installation failed, reverting ./composer.json to its original content.
Shouldn’t my fresh installation not be all v8.7.19?
It seems there is no direct way on this major update. I finally ended up exporting the pagetree of my 8.7 installation as well as the db, created blank 9.5 installation with all extensions, imported the pagetree and imported the db. Since I only used major ext like georgringer/news and bootstrap_package I had no major prolbmes
I had this problem that whenever i wanted to download dev-master running $ composer require egeloen/google-map-bundle dev-master package I was getting error:
Problem 1
Installation request for egeloen/google-map-bundle dev-master -> satisfiable by egeloen/google-map-bundle[dev-master].
egeloen/google-map-bundle dev-master requires egeloen/google-map ^2.0#dev -> satisfiable by egeloen/google-map[2.0.x-dev] but these
conflict with your requirements or minimum-stability.
When I added minimum-stability: "dev" to composer.json file it suddenly upgraded all the packages including symfony/symfony to dev-master. I am not getting any error, but I am worried that I might have problems with some unstable packages in the future.
I made some research and found out that it is possible to set minimum-stability to single package. I tried running this:
$ composer require egeloen/google-map-bundle dev-master#dev
But unfortunatelly I am getting an error:
Problem 1
egeloen/google-map-bundle dev-master requires egeloen/google-map ^2.0#dev -> satisfiable by egeloen/google-map[2.0.x-dev].
egeloen/google-map-bundle dev-master requires egeloen/google-map ^2.0#dev -> satisfiable by egeloen/google-map[2.0.x-dev].
Removal request for egeloen/google-map == 2.0.9999999.9999999-dev
Installation request for egeloen/google-map-bundle dev-master#dev -> satisfiable by
egeloen/google-map-bundle[dev-master].
Unfortunatelly it suggests ^2.0#dev, but that version is not what I need. Any ideas where I am wrong or what I am missing?
The bundle you want to install has another dependency egeloen/google-map with a constraint of ^2.0#dev (also don't confuse this package with the bundle package). Since there is no stable 2.0 release of this dependency yet, it fails when your minimum stability is stable.
To resolve it without lowering the minimum stability for the other packages, you should explicitely list egeloen/google-map in your dependencies:
"egeloen/google-map": "^2.0#dev"
This will allow Composer to install a non-stable version of this "second-level" dependency.
I want to install resource bundle in sylius i used below command using cmd
composer require sylius/resource-bundle:0.2.*
when i ran above command i get below error
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
- sylius/taxation-bundle 0.1.x-dev requires sylius/resource-bundle 0.1.* -> satisfiable by sylius/resour
ce-bundle[v0.1.0].
- sylius/taxation-bundle 0.1.x-dev requires sylius/resource-bundle 0.1.* -> satisfiable by sylius/resour
ce-bundle[v0.1.0].
- Can only install one of: sylius/resource-bundle[v0.2.0, v0.1.0].
- Can only install one of: sylius/resource-bundle[v0.2.0, v0.1.0].
- Installation request for sylius/resource-bundle 0.2.* -> satisfiable by sylius/resource-bundle[v0.2.0]
.
- Installation request for sylius/taxation-bundle == 0.1.9999999.9999999-dev -> satisfiable by sylius/ta
xation-bundle[0.1.x-dev].
Installation failed, reverting composer.json to its original content.
Please share some knowledge..Thanks in advance.
Why you want to install this bundle? I is already there as it is dependency of all other bundles. You do not need to install it separately. And these bundles use 0.1.* version currently.