I get this error with composer require sonata-project/propel-admin-bundle dev-master:
Problem 1
- Installation request for sonata-project/propel-admin-bundle dev-master -> satisfiable by sonata-project/propel-admin-bundle[dev-master].
- sonata-project/propel-admin-bundle dev-master requires sonata-project/admin-bundle ~2.3 -> satisfiable by sonata-project/admin-bundle[2.3.0, 2.3.1, 2.3.10, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6, 2.3.7, 2.3.8, 2.3.9, 2.x-dev] but these conflict with your requirements or minimum-stability.
Is there any possible way to get sonata to work on symfony 3.2? Is it possible to ignore composer requirement errors somehow and then fix compatibility errors myself?
SonataPropelAdminBundle is not compatible with Symfony 3.x. As you can see in the error it requires SonataAdminBundle ~2.3 and only versions > 3.x of SonataAdminBundle are compatible with Symfony 3.x
Related
$ composer require sonata-project/admin-bundle
Using version ^3.87 for sonata-project/admin-bundle
./composer.json has been updated
Running composer update sonata-project/admin-bundle
Loading composer repositories with package information
Restricting packages listed in "symfony/symfony" to "5.2.*"
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- sonata-project/admin-bundle[3.87.0, ..., 3.x-dev] require symfony/console ^4.4 -> found symfony/console[v4.4.0-BETA1, ..., 4.4.x-dev] but it conflicts with your root composer.json require (5.2.*).
- Root composer.json requires sonata-project/admin-bundle ^3.87 -> satisfiable by sonata-project/admin-bundle[3.87.0, 3.x-dev].
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.
My suggestion is to use EasyAdmin bundle which is compatible with Symfony 5.3. It has only one bug which is related to viewing images thumbnail in easyadmin panel. For now the only solution is to use TextareaField instead of ImageField in DasboardCrudController.
According to an issue from their tracker and packagist.org, the most recent version of that package (which is 3.87.0) is not fully compatible with Symfony 5. You either need to wait until this is resolved, or downgrade Symfony in your application to v4.4
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.
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.
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
I'm learning Symfony with a french tutorial.
I need then to install doctrine-fixtures-bundle, but here is the result of my composer.phar update : http://pastebin.com/55k3zKUQ (kind of big to shows it on stackoverflow)
It seems that the latest version of doctrine-fixtures-bundle doesn't support Symfony 2.3.6.
Am I right? How could I install doctrince fixture bundle on my symfony project?
Here's my composer.json : http://pastebin.com/CpccRyid
You problem isn't the doctrine fixtures bundle, another package (jms/di-extra-bundle) is complaining about the versions.
You should always skip a lot stuff from the composer error, the first thing you should read is:
jms/di-extra-bundle 1.1.0 requires symfony/framework-bundle 2.1.*
Here you see that the jms/di-extra-bundle version 1.1.0 package symfony/framework-bundle version 2.1.* required (in other words, it requires symfony 2.1). You have installed symfony 2.3.x.
Then you read further:
jms/di-extra-bundle 1.1.1 requires symfony/finder 2.1.*
So if we take version 1.1.1, it doesn't require symfony/framework-bundle 2.1, but symfony/finder 2.1.*. The result is the same: We should install symfony 2.1 and not 2.3.
Then you go to the package page to see if there is a version which supports symfony 2.3. And yes, for the latest stable version (1.4.0) the list of dependencies looks like:
jms/aop-bundle: >=1.0.0,<1.2-dev
jms/metadata: 1.*
symfony/framework-bundle: ~2.1
symfony/process: ~2.1
symfony/finder: ~2.1
~2.1 means at least 2.1.0. It will match each 2.* version, so 2.3 is supported to. So, you just need to replace 1.1.* in your composer.json for the jms/di-extra-bundle to 1.4.* and then update the packages with the update command.