magento/product-enterprise-edition 2.4.8 requires missing package magento/magento-zf-db ^3.21

[lamacias25]

Preconditions and environment

When trying to install Magento EE 2.4.8 via Composer, the installation fails because the package magento/product-enterprise-edition 2.4.8 depends on magento/magento-zf-db ^3.21, which cannot be found in any available repository.

Problem 1
  - Root composer.json requires magento/product-enterprise-edition 2.4.8 -> satisfiable by magento/product-enterprise-edition[2.4.8].
  - magento/product-enterprise-edition 2.4.8 requires magento/magento-zf-db ^3.21 -> could not be found in any version, there may be a typo in the package name.
Problem 2
  - Root composer.json requires magento/magento-cloud-metapackage >=2.4.8 <2.4.9 -> satisfiable by magento/magento-cloud-metapackage[2.4.8, 2.4.8-p1].
  - magento/magento-cloud-metapackage[2.4.8, ..., 2.4.8-p1] require magento/product-enterprise-edition >=2.4.8 <2.4.9 -> satisfiable by magento/product-enterprise-edition[2.4.8].
  - magento/product-enterprise-edition 2.4.8 requires magento/magento-zf-db ^3.21 -> could not be found in any version, there may be a typo in the package name.

Steps to reproduce

1. Set up a new Magento 2.4.8 EE project
2. Run composer install
3. Observe that the installation fails due to a missing package

Expected result

Composer should be able to resolve all dependencies and complete the installation of Magento EE 2.4.8.

Actual result

Composer fails due to a missing dependency: magento/magento-zf-db ^3.21

Additional information

The package magento/magento-zf-db does not appear on Packagist or in private Magento repositories. This might be a typo in the package name or a missing upload. Please advise.

Command used:

composer create-project --repository=https://repo.magento.com/ magento/project-enterprise-edition mage248

Environment:
PHP version: 8.3.15
Composer version: 2.8.0

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• 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”.

[m2-assistant]

Hi @lamacias25. 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.

• 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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]

Hi @engcom-November. 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: 👇

• 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

  - 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!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @lamacias25 ,

Thank you for your report and collaboration.

We attempted to reproduce the issue by installing 2.4.8 via composer but were unable to reproduce it. Please find the attached screenshot for reference.

Steps to Reproduce:

1. Set up a new Magento 2.4.8 EE project
2. Run composer install

We followed these steps and did not encounter any issues. Could you please recheck and let us know if we are missing any steps to reproduce this issue?

Therefore, we are marking this ticket as "Issue: Needs Update".

Thank you!

[hostep]

I can't speak for Adobe Commerce, but in Magento Open Source that package comes from here: https://packagist.org/packages/magento/magento-zf-db, and is published on Github over here: https://github.com/magento/magento-zf-db

So it should be available to everybody.

[engcom-November]

Hello @lamacias25 ,

Just wanted t follow Up on the above comment

Thank You!

[engcom-November]

Hello @lamacias25 ,

We are closing this issue due to prolonged inactivity. If the problem persists, please feel free to reopen the ticket or create a new one.

Thank you!