I have been trying to install DoctrineMongoDBBundle with Symfony2. I followed this reference http://symfony.com/doc/current/bundles/DoctrineMongoDBBundle/index.html
Unfortunately I am getting the following error and could not find a solution.
I have already added the php extension for MongoDB. Could you please give an idea about this ?
doctrine/mongodb 1.0.3 requires ext-mongo >=1.2.12,<1.5-dev -> the request
ed PHP extension mongo has the wrong version (1.2.11) installed.
doctrine/mongodb 1.0.2 requires ext-mongo >=1.2.12,<1.4-dev -> the request
ed PHP extension mongo has the wrong version (1.2.11) installed.
doctrine/mongodb 1.0.1 requires ext-mongo >=1.2.12,<1.4-dev -> the request
ed PHP extension mongo has the wrong version (1.2.11) installed.
doctrine/mongodb 1.0.0 requires ext-mongo >=1.2.12,<1.4-dev -> the request
ed PHP extension mongo has the wrong version (1.2.11) installed.
doctrine/mongodb-odm 1.0.0-BETA5 requires doctrine/mongodb 1.0.0-BETA1 ->
no matching package found.
You have to update your PHP MongoDB extension as it is currently version 1.2.11 and you need a version greater than or equal to 1.2.12.
ext-mongo in the error message refers to your PHP extension.
That's exactly what the error message says ... doctrine/mongodb needs a greater version of the mongoDB extension and therefore composer can't find a compatible package.
Related
I'm running Airflow 1.10.6 on Google Cloud Composer with Python 3. To initiate a dataflow job from the composer environment I need to have the PyPi package google-cloud-datastore. When I try to add this package through either the interface or cloud shell, the build fails. It raises the following error:
UPDATE operation on this environment failed 1 hour ago with the following error message:
Failed to install PyPI packages.
If I check the logs of Google Build for the Kubernetes Engine I see the following error:
I 2020-03-04T14:36:23.939075607Z [0mgoogle-cloud-datastore 1.11.0 has requirement google-cloud-core<2.0dev,>=1.0.3, but you have google-cloud-core 0.29.1.
I 2020-03-04T14:36:23.939669242Z google-cloud-datastore 1.11.0 has requirement google-api-core[grpc]<2.0.0dev,>=1.14.0, but you have google-api-core 1.8.1.
So google-cloud-datastore requires google-cloud-core>=1.0.3. I tried to explicitly set google-cloud-core to 1.0.3, but then I get the following error:
I 2020-03-05T08:13:18.539300693Z [0mgoogle-cloud-logging 1.9.1 has requirement google-cloud-core<0.30dev,>=0.29.0, but you have google-cloud-core 1.0.3.
I 2020-03-05T08:13:18.539878367Z google-cloud-bigtable 0.32.0 has requirement google-cloud-core<0.30dev,>=0.29.0, but you have google-cloud-core 1.0.3.
I 2020-03-05T08:13:18.540308937Z google-cloud-bigquery 1.8.1 has requirement google-cloud-core<0.30dev,>=0.29.0, but you have google-cloud-core 1.0.3.
So the ranges of versions required for the packages are not overlapping. Does anyone know if this can be fixed? Please let me know.
There is a compatibility issue with google-cloud-datastore in the main container of Composer, and that the latest version of this package could not be installed. The Composer product team has confirmed the issue and is working on it.
Attempting to install an older version of google-cloud-datastore may be a workaround before the root cause is fixed. I have tried with 1.7.4 version and got positive result:
I hope it helps.
In case you (or someone else reading this) needs to use the latest version of google-cloud-datastore (==1.11.0), I was able to install it in my environment (composer-1.9.1-airflow-1.10.6) by adding recent versions of the following libraries to the dependencies too:
googleapis-common-protos==1.6.0
google-cloud-spanner==1.14.0
google-cloud-bigtable==1.2.1
google-cloud-logging==1.14.0
google-cloud-bigquery==1.22
I get following error on composer install for ebay bundle. dependency has old version of jms and I'm using new version. what can I do on this?
How can I ignore dependency?
- webconsul/ebay-api-bundle dev-master requires jms/serializer-bundle ~0.13 -> no matching package found.
my composer.json:
"jms/serializer-bundle": "^1.1",
...
"webconsul/ebay-api-bundle": "dev-master"
There is a reason why jms/serializer-bundle had a major release. They are simply incompatible. You can't ignore the version, because the code won't work anymore.
Either contribute the update to webconsul/ebay-api-bundle or create a working fork if it's not maintained anymore.
You cannot ignore version restriction required by a dependency that you are trying to install.
The classic way in this case is to look for a more recent version of the requested package (here webconsul/ebay-api-bundle).
But, you are using dev-master and it should be the most recent dev version.
You can just wait for a new version or adapt your jms/serializer-bundle version according to the webconsul/ebay-api-bundle requirement.
EDIT By using dev-master or #dev you will have a non stable release.
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 am on OS X 10.9, using MAMP. I have mcrypt installed and it is enabled when I look at php -i. I am running the composer via php through composer.phar. Getting:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- laravel/framework v5.0.5 requires ext-mcrypt * -> the requested PHP extension mcrypt is missing from your system.
- laravel/framework v5.0.4 requires ext-mcrypt * -> the requested PHP extension mcrypt is missing from your system.
- laravel/framework v5.0.3 requires ext-mcrypt * -> the requested PHP extension mcrypt is missing from your system.
- laravel/framework v5.0.2 requires ext-mcrypt * -> the requested PHP extension mcrypt is missing from your system.
- laravel/framework v5.0.1 requires ext-mcrypt * -> the requested PHP extension mcrypt is missing from your system.
- laravel/framework v5.0.0 requires ext-mcrypt * -> the requested PHP extension mcrypt is missing from your system.
- Installation request for laravel/framework 5.0.* -> satisfiable by laravel/framework[v5.0.0, v5.0.1, v5.0.2, v5.0.3, v5.0.4, v5.0.5].
Sorry for the late.. but if you still have the problem, it's certainly because of your php version ..
Composer use the system version and mcrypt module may not be installed for that version. So check the version that your system using and do what you can to choose the "correct" php.
For example change your PATH env variable ;p
Best regards,
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.