Closed hemendrametawolf closed 1 month ago
Hi @hemendrametawolf. 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@magento I am working on this
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.
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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Hi @hemendrametawolf
Thanks for reporting and collaboration.
Verified the issue on Magento 2.4.7-p1 after upgrading the instance from 2.3.5-p1.
We can upgrade the 2.3.5-p1 instance to 2.4.7-p1 successfully without any errors.
Please refer to the attached screenshots. Let us know if we missed anything.
Before upgrading Magento 2.3.5-p1:
After updating to 2.4.7-p1 instance:
Hi @engcom-Delta. 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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hi @hemendrametawolf
Thanks for reporting and collaboration.
Verified the issue on Magento 2.4.7-p1 after upgrading the instance from 2.3.5-p1.
We can upgrade the 2.3.5-p1 instance to 2.4.7-p1 successfully without any errors.
Please refer to the attached screenshots. Let us know if we missed anything.
Before upgrading Magento 2.3.5-p1:
After updating to 2.4.7-p1 instance:
Should I try to need to use 2.4.7-p1 ??
I would suggest you read the warning with yellow background in your screenshot and update composer v1 to v2. I'm not sure if the composer plugins shipping with Magento > 2.4.5 are still compatible with composer v1. Switching to composer v2 should hopefully give you better results.
But please, this is not a Magento bug, this is a user problem, so this ticket should be closed. It's probably better to move the discussion to https://magento.stackexchange.com/ or https://community.magento.com/ in case you still run into problems after switching to composer v2.
As suggestion i changed magento version to 2.4.7-p1 and updated composer i am getting this
It sounds to me that the following line in your composer.json
file is not set to stable
, can that be?
"minimum-stability": "stable"
So it sounds like you're dealing with an ancient version of composer.json
and you didn't update it properly during Magento upgrades.
I would suggest you create an empty directory and inside that directory you run the following command:
composer create-project --no-install --repository-url=https://repo.magento.com/ magento/project-community-edition:2.4.7-p1 .
It will ask you for authentication and after you've given it the correct username and password, you should see a clean composer.json
file (for Magento 2.4.7-p1) in that new directory.
Use that composer.json
file to compare it to your own and figure out the changes you need to apply to your own.
Or use that composer.json
file as a base and append changes from your own (like added dependencies).
This should hopefully get you further.
command is working fine and install the magento as
This is my composer file { "name": "magento/project-community-edition", "description": "eCommerce Platform for Growth (Community Edition)", "type": "project", "version": "2.4.7-p1", "license": [ "OSL-3.0", "AFL-3.0" ], "config": { "preferred-install": "dist", "sort-packages": true, "allow-plugins": { "magento/composer-dependency-version-audit-plugin": true, "magento/magento-composer-installer": true, "magento/inventory-composer-installer": true, "dealerdirect/phpcodesniffer-composer-installer": true, "magento/composer-root-update-plugin": true } }, "require": { "ext-intl": "", "ext-json": "", "composer/composer": "@alpha", "firegento/fastsimpleimport": "^1.1", "firegento/magesetup2": "dev-develop", "magenerds/language-de_de": "^1.0", "magento/composer-root-update-plugin": "~2.0", "magento/product-community-edition": "2.4.7-p1", "mageplaza/magento-2-google-analytics": "^1.0", "sabre/xml": "^2.0" }, "require-dev": { "allure-framework/allure-phpunit": "~1.5.0", "dealerdirect/phpcodesniffer-composer-installer": "^0.7.2", "friendsofphp/php-cs-fixer": "~3.4.0", "lusitanian/oauth": "~0.8.10", "magento/magento-coding-standard": "", "magento/magento2-functional-testing-framework": "~3.7", "pdepend/pdepend": "2.10.0", "phpcompatibility/php-compatibility": "^9.3", "phpmd/phpmd": "@stable", "phpstan/phpstan": "^1.6.8", "phpunit/phpunit": "~9.5.20", "sebastian/phpcpd": "~6.0.3", "squizlabs/php_codesniffer": "~3.6.0" }, "replace": { "amzn/amazon-pay-and-login-magento-2-module": "", "dotmailer/dotmailer-magento2-extension": "", "klarna/module-core": "", "klarna/module-kp": "", "klarna/module-ordermanagement": "", "magento/module-analytics": "", "magento/module-authorizenet": "", "magento/module-braintree": "", "magento/module-catalog-analytics": "", "magento/module-customer-analytics": "", "magento/module-dhl": "", "magento/module-downloadable": "", "magento/module-downloadable-import-export": "", "magento/module-fedex": "", "magento/module-marketplace": "", "magento/module-multishipping": "", "magento/module-new-relic-reporting": "", "magento/module-quote-analytics": "", "magento/module-review-analytics": "", "magento/module-sales-analytics": "", "magento/module-sample-data": "", "magento/module-signifyd": "", "magento/module-ups": "", "magento/module-usps": "", "magento/module-version": "", "magento/module-wishlist-analytics": "", "shopialfb/facebook-module": "", "temando/module-shipping-m2": "", "vertex/module-tax": "" }, "conflict": { "gene/bluefoot": "*" }, "autoload": { "psr-4": { "Magento\Framework\": "lib/internal/Magento/Framework/", "Magento\Setup\": "setup/src/Magento/Setup/", "Magento\": "app/code/Magento/", "Zend\Mvc\Controller\": "setup/src/Zend/Mvc/Controller/", "Bss\MultiWishlist\": "" }, "psr-0": { "": [ "app/code/", "generated/code/" ] }, "files": [ "app/etc/NonComposerComponentRegistration.php" ], "exclude-from-classmap": [ "/dev/", "/update/", "/Test/" ] }, "autoload-dev": { "psr-4": { "Magento\Sniffs\": "dev/tests/static/framework/Magento/Sniffs/", "Magento\Tools\": "dev/tools/Magento/Tools/", "Magento\Tools\Sanity\": "dev/build/publication/sanity/Magento/Tools/Sanity/", "Magento\TestFramework\Inspection\": "dev/tests/static/framework/Magento/TestFramework/Inspection/", "Magento\TestFramework\Utility\": "dev/tests/static/framework/Magento/TestFramework/Utility/", "Magento\PhpStan\": "dev/tests/static/framework/Magento/PhpStan/" } }, "minimum-stability": "alpha", "prefer-stable": true, "repositories": { "0": { "type": "composer", "url": "https://repo.magento.com/" }, "firegento_magesetup": { "type": "vcs", "url": "git@github.com:firegento/firegento-magesetup2.git" }, "bubbleshop": { "type": "artifact", "url": "var/zip/" } }, "extra": { "magento-force": "override" } }
It's up to you to figure it out now, sorry, github is meant for reporting bugs and feature requests, not to help out with user problems.
I think you have enough info to continue now, this ticket can be closed in my opinion @engcom-Dash
Hi @hostep ,
Thanks for contribution. As per your comment we are closing this issue.
@hemendrametawolf , Please feel free to reopen the ticket if you are still facing any issue.
Summary
I am trying to update magento version but it showing package not installed error
Examples
Proposed solution
it should be updated with version
Release note
No response
Triage and priority