I've already applied the patch MDVA-532.
When I run composer update magento/magento-composer-installer
I got this error:
Your requirements could not be resolved to an installable set of
packages.Problem 1
– The requested package magento/product-community-edition == 2.0.6.0 could not be found.Problem 2
– Installation request for braintree/braintree_php == 2.39.0.0 -> satisfiable by braintree/braintree_php[2.39.0].
– magento/product-community-edition 2.1.0 requires braintree/braintree_php 3.7.0 -> satisfiable by
braintree/braintree_php[3.7.0].
– magento/product-community-edition 2.1.0 requires braintree/braintree_php 3.7.0 -> satisfiable by
braintree/braintree_php[3.7.0].
– Conclusion: don't install braintree/braintree_php 3.7.0
– Installation request for magento/product-community-edition 2.1.0 -> satisfiable by magento/product-community-edition[2.1.0].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://getcomposer.org/doc/04-schema.md#minimum-stability for more
details.Read https://getcomposer.org/doc/articles/troubleshooting.md for
further common problems.
When I run composer update
I got this error:
Your requirements could not be resolved to an installable set of
packages.Problem 1
– Installation request for magento/data-migration-tool ~2.0.0 -> satisfiable by magento/data-migration-tool[2.0.5, 2.0.0, 2.0.2,
2.0.7].
– Conclusion: don't install magento/framework 100.1.0
– magento/product-community-edition 2.1.0 requires magento/framework 100.1.0 -> satisfiable by
magento/framework[100.1.0].
– magento/product-community-edition 2.1.0 requires magento/framework 100.1.0 -> satisfiable by
magento/framework[100.1.0].
– Conclusion: don't install magento/framework 100.1.0
– Installation request for magento/product-community-edition 2.1.0 -> satisfiable by magento/product-community-edition[2.1.0].
Best Answer
I've bumped into the same issue. Any attempt to upgrade to version 2.1 bumped into various messages like "Conclusion: don't install magento/module-widget" or "Can only install one of". Closer inspection of all packages defined in my
composer.json
showed that it was calling for various modules of version100.0.*
while actually the upgrade messages mentioned that version100.1.x
was needed.I changed all instances of
100.0.*
to100.*
and this allowed me to upgrade.Note that I assume that this versioning scheme follows the semantic versioning standards, meaning that this allows me to upgrade to newer minor versions without breaking backwards compatibility. Also note that I've run this on various development sites, where I'm just developing Magento 2 extensions. I don't have any Magento 2 project, so don't care much about the core. It might be that my
composer.json
hacks are not meant for production.