I want to install a bundle which has the following dependencies:
"require": {
"symfony/symfony": ">=2.4",
"simplesamlphp/simplesamlphp": "dev-master"
},
When I try to do do the composer require hslavich/simplesamlphp-bundle dev-master I get the following:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- simplesamlphp/simplesamlphp v1.13.2 requires openid/php-openid dev-master#ee669c6a9d4d95b58ecd9b6945627276807694fb as 2.2.2 -> no matching package found.
- simplesamlphp/simplesamlphp v1.13.1 requires openid/php-openid dev-master#ee669c6a9d4d95b58ecd9b6945627276807694fb as 2.2.2 -> no matching package found.
- simplesamlphp/simplesamlphp v1.13.0 requires openid/php-openid dev-master#ee669c6a9d4d95b58ecd9b6945627276807694fb as 2.2.2 -> no matching package found.
- simplesamlphp/simplesamlphp v1.12.0 requires openid/php-openid dev-master#ee669c6a9d4d95b58ecd9b6945627276807694fb as 2.2.2 -> no matching package found.
- hslavich/simplesamlphp-bundle dev-master requires simplesamlphp/simplesamlphp dev-master -> no matching package found.
- hslavich/simplesamlphp-bundle dev-master requires simplesamlphp/simplesamlphp * -> satisfiable by simplesamlphp/simplesamlphp[v1.12.0, v1.13.0, v1.13.1, v1.13.2].
- Installation request for hslavich/simplesamlphp-bundle dev-master -> satisfiable by hslavich/simplesamlphp-bundle[dev-master].
But if I first do composer require simplesamlphp/simplesamlphp dev-master and then composer require hslavich/simplesamlphp-bundle dev-master everything is ok.
How should the bundles composer.json file modified so that I would not need separate require for simplesamlphp dev-master?
hslavich/simplesamlphp-bundle v1.13 requires simplesamlphp/simplesamlphp 1.13
But simplesamlphp/simplesamlphp v1.13.2 requires openid/php-openid: dev-master#ee669c6a9d4d95b58ecd9b6945627276807694fb as 2.2.2
Add in your composer.json:
"hslavich/simplesamlphp-bundle": "1.*",
"openid/php-openid": "dev-master#ee669c6a9d4d95b58ecd9b6945627276807694fb"
The last line is required because openid/php-openid dev-master is not stable.
For your information, gmp PHP extension is required by penid/php-openid.
If you require another package, that requires another unstable (dev-master) package, you need to mention it in your composer.json:
"require": {
"hslavich/simplesamlphp-bundle": "~1.13",
"simplesamlphp/simplesamlphp": "dev-master"
}
Then run:
composer update
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 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.
while installing admin bundle through this error :
Your requirements could not be resolved to an installable set of packages.
Problem 1
- sonata-project/admin-bundle 2.3.7 requires sensio/generator-bundle ~2.3 -> no matching package found.
- sonata-project/admin-bundle 2.3.6 requires sensio/generator-bundle ~2.3 -> no matching package found.
- sonata-project/admin-bundle 2.3.5 requires sensio/generator-bundle ~2.3 -> no matching package found.
- sonata-project/admin-bundle 2.3.4 requires sensio/generator-bundle ~2.3 -> no matching package found.
- sonata-project/admin-bundle 2.3.3 requires sensio/generator-bundle ~2.3 -> no matching package found.
- sonata-project/admin-bundle 2.3.2 requires sensio/generator-bundle ~2.3 -> no matching package found.
- sonata-project/admin-bundle 2.3.1 requires sensio/generator-bundle ~2.3 -> no matching package found.
- sonata-project/admin-bundle 2.3.0 requires sensio/generator-bundle ~2.3 -> no matching package found.
- Installation request for sonata-project/admin-bundle ^2.3 -> satisfiable by sonata-project/admin-bundle[2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6, 2.3.7].
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://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.
Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
however I have installed sensio/generator-bundle
what is the problem ? and how I can fix that ?
my symfony is 3.0.1
I've recently encountered this kind of issue during an installation of sonata/admin-bundle.
You can work with the dev dependency until the issue is resolved.
Use composer require sonata-project/admin-bundle:dev-master
Maybe the installation will require an update of related packages like sonata/user-bundle, use the version required by the bundle or #dev .
Take a look of this post on github https://github.com/sonata-project/SonataAdminBundle/issues/3467 and this document about sonata project development state. https://docs.google.com/spreadsheets/d/1fSpS10nzlEj9HE-GdZ-BHcxileEzHwRIzLlNfdNtZ2k/edit#gid=0 . So if you can it's better to keep symfony 2.7 for Sonata Admin integrations, at least by the moment.
Work done by Sonata team for compatibility with Symfony3 but this work is not finish apparently.
And I don't find a 2.4 version of SonataAdminBundle in gitHub or documentation
Following situation:
app requires andig/dbcopy in dev version:
composer require andig/dbcopy:dev-master
andig/dbcopy requires symfony/consolein dev version (due to a bug in 2.5):
"require": {
"doctrine/dbal": "2.4.*",
"symfony/console": "2.6.*#dev"
},
Now, when adding andig/dbcopy to the app using composer require, composer complains about stability:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for andig/dbcopy dev-master -> satisfiable by andig/dbcopy[dev-master].
- andig/dbcopy dev-master requires symfony/console 2.6.*#dev -> 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://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.
No minimum-stability settings have been defined, the app already has a dependency on a dev-master package.
I've read https://groups.google.com/forum/#!topic/composer-dev/_g3ASeIFlrc/discussion but I'm still confused as to why composer fails to install even though
all stability settings are explicitly defined and
the app itself already has another dependency on "dev-master" which works?
Just put:
"symfony/console": "2.6.*#dev"
in your main composer.json. You must override stability requirement directly.
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.