magento2 icon indicating copy to clipboard operation
magento2 copied to clipboard

2.4.7-p1 incompatible with magento/extension-b2b

Open edwinljacobs opened this issue 1 year ago • 4 comments

Preconditions and environment

magento/extension-b2b cannot be installed with magento/product-enterprise-edition:2.4.7-p1

This is due to the following composer error:

╰─$ composer update
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - magento/extension-b2b[1.4.0, ..., 1.4.2] require magento/framework >=103.0.6 <=103.0.7 -> satisfiable by magento/framework[103.0.6-beta1, ..., 103.0.7].
    - You can only install one version of a package, so only one of these can be installed: magento/framework[100.0.2, ..., 100.2.0-rc20, 101.0.0-rc21, ..., 101.0.12, 102.0.0, ..., 102.0.7-p3, 103.0.0-beta1, ..., 103.0.7-p1].
    - magento/product-community-edition 2.4.7-p1 requires magento/framework 103.0.7-p1 -> satisfiable by magento/framework[103.0.7-p1].
    - magento/product-enterprise-edition 2.4.7-p1 requires magento/product-community-edition 2.4.7-p1 -> satisfiable by magento/product-community-edition[2.4.7-p1].
    - Root composer.json requires magento/product-enterprise-edition 2.4.7-p1 -> satisfiable by magento/product-enterprise-edition[2.4.7-p1].
    - Root composer.json requires magento/extension-b2b ^1.4 -> satisfiable by magento/extension-b2b[1.4.0, 1.4.1, 1.4.2].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions

So in essence Enterprise needs community which needs magento/framework 103.0.7-p1. magento/extension-b2b needs magento/framework: <= 103.0.7 So we cannot install. I suspect that its just a version constraint issue and there is no incompatibility but ofcourse I am not sure of that.

AS a workaround we can do: "magento/framework": "103.0.7-p1 as 103.0.7" in composer json but I personally am not a fan of this kind of manipulation. I posted this as well in the community forums but no response yet https://community.magento.com/t5/Magento-2-x-Technical-Issues/Commerce-2-4-7-p1-incompatible-with-magento-b2b-extension/m-p/557149#M21933.

Steps to reproduce

Stock 2.4.7-p1 commerce installation composer require magento/extension-b2b should produce the error mentioned below and above.

Expected result

Install magento/extension-b2b without errors

Actual result

Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - magento/extension-b2b[1.4.0, ..., 1.4.2] require magento/framework >=103.0.6 <=103.0.7 -> satisfiable by magento/framework[103.0.6-beta1, ..., 103.0.7].
    - You can only install one version of a package, so only one of these can be installed: magento/framework[100.0.2, ..., 100.2.0-rc20, 101.0.0-rc21, ..., 101.0.12, 102.0.0, ..., 102.0.7-p3, 103.0.0-beta1, ..., 103.0.7-p1].
    - magento/product-community-edition 2.4.7-p1 requires magento/framework 103.0.7-p1 -> satisfiable by magento/framework[103.0.7-p1].
    - magento/product-enterprise-edition 2.4.7-p1 requires magento/product-community-edition 2.4.7-p1 -> satisfiable by magento/product-community-edition[2.4.7-p1].
    - Root composer.json requires magento/product-enterprise-edition 2.4.7-p1 -> satisfiable by magento/product-enterprise-edition[2.4.7-p1].
    - Root composer.json requires magento/extension-b2b ^1.4 -> satisfiable by magento/extension-b2b[1.4.0, 1.4.1, 1.4.2].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Additional information

No response

Release note

No response

Triage and priority

  • [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

edwinljacobs avatar Jun 21 '24 09:06 edwinljacobs

Hi @edwinljacobs. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

m2-assistant[bot] avatar Jun 21 '24 09:06 m2-assistant[bot]

In addition I just want to say that proposed workaround works for PHP 8.2 and doesn't work for PHP 8.3.

www-data@c829a04f430e:/var/www/html$ composer require magento/extension-b2b:"^1.4.2" "magento/framework": "103.0.7-p1 as 103.0.7"
./composer.json has been updated
Running composer update magento/extension-b2b magento/framework
Loading composer repositories with package information                                                                                                       Updating dependencies                                 
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - magento/module-b2b[100.4.0, ..., 100.4.1] require php ~8.1.0||~8.2.0 -> your php version (8.3.7) does not satisfy that requirement.
    - magento/extension-b2b 1.4.2 requires magento/module-b2b 100.4.1 -> satisfiable by magento/module-b2b[100.4.1].
    - Root composer.json requires magento/extension-b2b ^1.4.2 -> satisfiable by magento/extension-b2b[1.4.2].

yaronish avatar Jun 21 '24 14:06 yaronish

Yes but it's a known issue that B2B is not compatible with php8.3

thomas-kl1 avatar Jun 21 '24 21:06 thomas-kl1

Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

    1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
    1. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
    1. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
      - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
      - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

m2-assistant[bot] avatar Jun 28 '24 05:06 m2-assistant[bot]

Hi @edwinljacobs

Thanks for reporting and collaboration.

Verified the issue on Magento 2.4.7-p1 but the issue is not reproducible.

We can install 2.4.7-p1 with b2b extension.

Steps to reproduce Stock 2.4.7-p1 commerce installation composer require magento/extension-b2b should produce the error mentioned below and above.

Please take a look at the screenshots I've attached. Let us know if we missed anything.

Screenshot 2024-07-16 at 4 25 37 PM Screenshot 2024-07-16 at 6 20 29 PM

engcom-Dash avatar Jul 16 '24 12:07 engcom-Dash

hello @engcom-Dash

Yes it has been fixed with the latest b2b package release, so we can close this ticket. However any idea when b2b is going to be fully compatible with php8.3?

Regards,

thomas-kl1 avatar Jul 16 '24 13:07 thomas-kl1

Hi @edwinljacobs

We are closing the ticket as per the above comments.

Thanks

engcom-Dash avatar Jul 17 '24 13:07 engcom-Dash

Hello,

I have this issue with PHP 8.3 on Magento 2.4.7-p1.

When the b2b will be compatible with php8.3 ? We are in migration to Magento 2.4.6-p6 to 2.4.7-p1 and this uncompatibility blocks our development.

Have a good day.

Update: Error :

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

  Problem 1
    - magento/module-b2b[100.4.0, ..., 100.4.1-p1] require php ~8.1.0||~8.2.0 -> your php version (8.3.6) does not satisfy that requirement.
    - magento/extension-b2b 1.4.2-p1 requires magento/module-b2b 100.4.1-p1 -> satisfiable by magento/module-b2b[100.4.1-p1].
    - Root composer.json requires magento/extension-b2b 1.4.2-p1 -> satisfiable by magento/extension-b2b[1.4.2-p1].

lohoy avatar Jul 18 '24 08:07 lohoy

@engcom-Dash I now see that the package is compatible with version 100.5.0, but i don't see that update on this page: https://experienceleague.adobe.com/en/docs/commerce-admin/b2b/release-notes#b2b-v142-p1

Is it still in beta mode while it has a stable tag?

leonhelmus avatar Oct 30 '24 13:10 leonhelmus

@leonhelmus I was able to upgrade the package to 1.5.0 this morning, so communication will follow soon I guess :D Even some documentation link in the package are still not yet published

thomas-kl1 avatar Oct 30 '24 13:10 thomas-kl1