Composer showing error during version upgrade from 2.3.6-p1 to 2.4.7-p1

[Haidersajid]

Summary

while upgrading Magento, I updated all plugin versions to be compatible with the new version and PHP 8.3. I also removed unnecessary plugins and added some from the 2.4.7-p1 composer as well.

While running the following command:

composer2 update

or

composer2 update --no-plugins --with-all-dependencies

Showing Error:

• magento/magento2ce is present at version 2.3.6-p1 and cannot be modified by Composer
• magento/product-community-edition 2.4.7-p1 requires magento/magento2-base 2.4.7-p1 -> satisfiable by magento/magento2-base[2.4.7-p1].
• magento/magento2-base[2.4.7-p1] cannot be installed as that would require removing magento/magento2ce[2.3.6-p1]. They both replace trentrichardson/jquery-timepicker-addon and thus cannot coexist.
• Root composer.json requires magento/product-community-edition 2.4.7-p1 -> satisfiable by magento/product-community-edition[2.4.7-p1].

Note: tha magento/magento2ce its name specified at the beginning of the composer.json file, not as a plugin.

"name": "magento/magento2ce",

Also there is no "magento/magento2-base" in composer but its showing in command problem

Examples

Proposed solution

I tried upgrading Magento to version 2.4.2 and encountered the same problem

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.
• [X] 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.
• [X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @Haidersajid. 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:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  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.

[hostep]

Just some notes:

• magento/magento2ce doesn't exist, try to figure out where that comes from and remove it sorry I misunderstood, this is just the name of your own project, that's fine, then it's not important
• magento/magento2-base does exists, it's a dependency of magento/product-community-edition
• It might be best to create an empty directory to setup a clean composer.json file from a new Magento install, if you use the following command, it should generate a clean composer.json file that you can use to compare with your own, to try to figure out the problem in your own composer.json file:

  composer create-project --no-install --repository-url=https://repo.magento.com/ magento/project-community-edition:2.4.7-p1 ./some-empty-directory

[Haidersajid]

Just some notes:

• ~magento/magento2ce doesn't exist, try to figure out where that comes from and remove it~ sorry I misunderstood, this is just the name of your own project, that's fine, then it's not important
• magento/magento2-base does exists, it's a dependency of magento/product-community-edition
• It might be best to create an empty directory to setup a clean composer.json file from a new Magento install, if you use the following command, it should generate a clean composer.json file that you can use to compare with your own, to try to figure out the problem in your own composer.json file:

composer create-project --no-install --repository-url=https://repo.magento.com/ magento/project-community-edition:2.4.7-p1 ./some-empty-directory

i have 2..4.7-p1 files in my pc already, I checked the compressor file more than once and compared it, but I was unable to solve the problem. Can I simply replace the compressor with a new one, 2.4.7-p1, and only change the name and version?

[m2-assistant[bot]]

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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[hostep]

Can I simply replace the compressor with a new one, 2.4.7-p1, and only change the name and version?

That's up to you to decide, you'll probably have to take over all the modules - if any - you installed extra from your old composer.json file...