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.
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'm coming to ask a question, maybe stupid, but I can't find a good explanation about it..
For this example, I'll take for example a Xamarin Forms - Portable Project and look at the Project.Droid part. Also, I'm gonna take the following packages:
Xamarin.Forms.Map 2.3.1.114
and
Xamarin.Android.Support.Vector.Drawable 23.3.0
Xamarin.Android.Support.v7.RecyclerView 23.3.0
Xamarin.Android.Support.v7.MediaRouter 23.3.0
Xamarin.Android.Support.v7.CardView 23.3.0
Xamarin.Android.Support.v7.AppCompat 23.3.0
Xamarin.Android.Support.v4 23.3.0
Xamarin.Android.Support.Design 23.3.0
Xamarin.Android.Support.Animated.Vector.Drawable 23.3.0
As you can see, the Xamarin.Forms.Map package is version 2.3.1.114 and the others, 23.3.0. However, an update is available, but when I make it, the package of 23.3.0 version update to 23.4.0.1 while Xamarin.Forms.Map is downgrading to 1.5.1.6471 ...
Why does it work like it? why everything doesn't up to the last update? What are the differents effects of this update/downgrade? Also, what's the best choice? Does it's better to update the Xamarin.Android.Support.xxx packages and downgrade the Xamarin.Forms.Map one or do the reverse?
Thank in advance for your answer/explanation :)
Some package are update and not compatible with the last version of Xamarin.form, because the updates are not at the same frequency the principal reason, are all the new versions of Xamarin.form need to be probe, and be stable and may be exist a delay between one and other.
for Example if you try to install Xamarin.Android.Support.Design
Attempting to resolve dependencies for package 'Xamarin.Android.Support.Design.23.4.0.1' with DependencyBehavior 'Lowest'
One or more unresolved package dependency constraints detected in the existing packages.config file. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'Xamarin.Android.Support.Design 23.3.0'
Unable to resolve dependencies. 'Xamarin.Android.Support.Design 23.4.0.1' is not compatible with 'Xamarin.Forms 2.3.1.114 constraint: Xamarin.Android.Support.Design (= 23.3.0)'.
'Xamarin.Android.Support.Design 23.4.0.1' is not compatible with 'Xamarin.Forms 2.3.1.114 constraint: Xamarin.Android.Support.Design (= 23.3.0)'.
Xamarin Form 2.3.1.114 say I'm compatible with the version = 23.3.0
Regards.
The nuget manager allowing you to update packages to the version compatible with target SDK version selected in the project properties. If you need to upgrade to the newer version you have to install newer version of android SDK and update it in project properties to be able to upgrade nuget packages.
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 am trying to set up the Sonata User Bundle. As per the instructions I am also trying to install Sonata Easy-Extends (according to these instructions).
Unfortunately, I can't get Easy-Extends installed via composer (on Win7):
>composer require sonata-project/easy-extends-bundle
Please provide a version constraint for the sonata-project/easy-extends-bundle requirement: dev-master
./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
- The requested package sonata-project/easy-extends-bundle could not be found in any version, there may be a typo in the package name.
Problem 2
- Installation request for symfony/framework-standard-edition 2.5.x-dev -> satisfiable by symfony/framework-standard-edition[2.5.x-dev].
- symfony/framework-standard-edition 2.5.x-dev requires sonata-project/easy-extends-bundle 2.0 -> 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.
Read <http://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
Installation failed, reverting ./composer.json to its original content.
I have tried various version constraints, including 2.0 as suggested in the instructions.
What am I missing?
TIA
Matt
Based on a discussion in the sonata-users Google group, I managed to install the bundle by manually adding the following to my composer.json:
...
"sonata-project/easy-extends-bundle": "dev-master",
...
Related thread in GG can be found here.
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.