Skip to content
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

Wider Magento version support #881

Open
fooman opened this issue Jan 21, 2022 · 2 comments
Open

Wider Magento version support #881

fooman opened this issue Jan 21, 2022 · 2 comments

Comments

@fooman
Copy link
Contributor

fooman commented Jan 21, 2022

Steps to reproduce

  1. Try to install the latest version of magento/magento2-functional-testing-framework with the same feature set across multiple versions of Magento

Expected result

  1. The latest release of magento/magento2-functional-testing-framework should be installable in a wide range of Magento versions

Actual result

  1. magento/magento2-functional-testing-framework 3.8.0 only works with 2.4.4
  2. For 2.4.3-p1 you need to go down all the way to magento/magento2-functional-testing-framework: 3.5.1.

Suggested solution

When using dependencies that are used in common with magento/product-* please use wider dependency ranges. So far I have seen monolog/monolog and guzzlehttp/guzzle causing incompatibilities, but I also do not believe magento/magento2-functional-testing-framework uses particular features which would prevent dependency ranges covering monolog ^1 || ^2 as well as guzzle ^6 || ^7

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires magento/product-community-edition 2.4.3-p1 -> satisfiable by magento/product-community-edition[2.4.3-p1].
    - Conclusion: don't install monolog/monolog 1.19.0 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.20.0 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.21.0 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 2.3.2 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.22.0 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.22.1 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.23.0 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 2.3.3 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.24.0 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.25.0 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.25.1 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 2.3.4 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.25.2 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.25.3 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.25.4 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 2.3.5 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.25.5 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.26.0 (conflict analysis result)
    - Conclusion: don't install monolog/monolog 1.26.1 (conflict analysis result)
    - magento/product-community-edition 2.4.3-p1 requires magento/framework 103.0.3-p1 -> satisfiable by magento/framework[103.0.3-p1].
    - Root composer.json requires magento/magento2-functional-testing-framework 3.6.0 -> satisfiable by magento/magento2-functional-testing-framework[3.6.0].
    - magento/framework 103.0.3-p1 requires monolog/monolog ^1.17 -> satisfiable by monolog/monolog[1.17.0, ..., 1.26.1].
    - You can only install one version of a package, so only one of these can be installed: monolog/monolog[1.0.0, ..., 1.26.1, 2.0.0, ..., 2.3.5].
    - magento/magento2-functional-testing-framework 3.6.0 requires monolog/monolog ^2.3 -> satisfiable by monolog/monolog[2.3.0, ..., 2.3.5].
    - Conclusion: don't install monolog/monolog 2.3.1 (conflict analysis result)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires magento/product-community-edition 2.4.3-p1 -> satisfiable by magento/product-community-edition[2.4.3-p1].
    - Conclusion: don't install guzzlehttp/guzzle 6.5.0 (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle 6.5.1 (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle 6.5.2 (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle 7.4.1 (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle 6.5.3 (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle 6.5.4 (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle 6.5.5 (conflict analysis result)
    - Root composer.json requires magento/magento2-functional-testing-framework 3.8.0 -> satisfiable by magento/magento2-functional-testing-framework[3.8.0].
    - magento/product-community-edition 2.4.3-p1 requires guzzlehttp/guzzle ^6.3.3 -> satisfiable by guzzlehttp/guzzle[6.3.3, ..., 6.5.5].
    - You can only install one version of a package, so only one of these can be installed: guzzlehttp/guzzle[v1.0.3, v1.0.4, v2.0.0, ..., v2.8.8, v3.0.0, ..., v3.8.1, 4.0.0, ..., 4.2.4, 5.0.0, ..., 5.3.4, 6.0.0, ..., 6.5.5, 7.0.0, ..., 7.4.1].
    - magento/magento2-functional-testing-framework 3.8.0 requires guzzlehttp/guzzle ^7.3.0 -> satisfiable by guzzlehttp/guzzle[7.3.0, 7.4.0, 7.4.1].
    - Conclusion: don't install guzzlehttp/guzzle 7.4.0 (conflict analysis result)
@m2-assistant
Copy link

m2-assistant bot commented Jan 21, 2022

Hi @fooman. Thank you for your report.
To speed up processing of this issue, make sure that you provided sufficient information.

Add a comment to assign the issue: @magento I am working on this


@jonatanrdsantos
Copy link
Member

Same here, trying to install for a Magento cloud project from the docs, but it's not working:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants