-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation request of project package could only satisfy by itself #9949
Comments
Can you try to "composer self-update --2" and try again with composer 2? It may fix it or at least hopefully give you a clearer error message. |
With composer 2, the solver finds a solution. |
My
After the update. Composer showed me, that I also need to update the following packages. So please don't surprise that I modified the original command. The new command is:
This is the output:
I'm again surprised that there is a conflict with the root composer package itself. See for this the following issue: |
I am guessing it's to do with one of your replace or conflict rules.. But I can't know for sure. Please update to latest composer, 2.0.7 is over six months old, we have done lots more improvements since. Maybe 2.1.2 reports it correctly. |
@Seldaek thank you. After the upgrade to the current composer version, I got much more details. There was a conflict with the replacement of |
Ok great :) |
My
composer.json
:Output of
composer diagnose
:When I run this command:
I get the following output:
And I expected this to happen:
I don't know why I couldn't install the package
sylius/sylius
. I expect, that it should work. However, the project package himself its conflict with his self. That's startled me, because I don't get it. Why itsbmh/backend
having a conflict by itself? And why it has an installation request? It's the root composer package. In my point of view it's the problem whysylius/sylius
couldn't be installed by composer.Hopefully this is the right place for help. I think it's a composer issue and not an problem with sylius.
The text was updated successfully, but these errors were encountered: