Hi,
I'm on 2.4.2-p2, going to 2.4.3. Running the same composer commands as the last upgrade, but running into an issue:
[mysystem]$ COMPOSER_MEMORY_LIMIT=-1 composer update
Loading composer repositories with package information
In Laminas\DependencyPlugin\DependencyRewriterV2::onPrePoolCreate
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires magento/magento2-functional-testing-framework ^3.0 -> satisfiable by magento/magento2-functional-testing-framework[3.0.0, ..., 3.11.1].
- csharpru/vault-php 3.5.3 requires cache/cache ^0.4.0 -> satisfiable by cache/cache[0.4.0].
- Conclusion: install csharpru/vault-php 3.5.3 (conflict analysis result)
- magento/product-community-edition 2.4.3 requires magento/module-aws-s3 100.4.1 -> satisfiable by magento/module-aws-s3[100.4.1].
- Root composer.json requires magento/product-community-edition 2.4.3 -> satisfiable by magento/product-community-edition[2.4.3].
- Root composer.json requires allure-framework/allure-phpunit ~1.2.0 -> satisfiable by allure-framework/allure-phpunit[1.2.0, ..., 1.2.4].
- cache/cache 0.4.0 requires league/flysystem ^1.0 -> satisfiable by league/flysystem[1.0.0, ..., 1.1.10].
- You can only install one version of a package, so only one of these can be installed: league/flysystem[1.0.0, ..., 1.1.10, 2.0.0, ..., 2.5.0].
- magento/module-aws-s3 100.4.1 requires league/flysystem ^2.0 -> satisfiable by league/flysystem[2.0.0, ..., 2.5.0].
- Conclusion: don't install league/flysystem 2.5.0 (conflict analysis result)
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.So I then tried:
[mysystem]$ COMPOSER_MEMORY_LIMIT=-1 composer update --with-all-dependencies
Loading composer repositories with package information
In Laminas\DependencyPlugin\DependencyRewriterV2::onPrePoolCreate
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires magento/magento2-functional-testing-framework ^3.0 -> satisfiable by magento/magento2-functional-testing-framework[3.0.0, ..., 3.11.1].
- csharpru/vault-php 3.5.3 requires cache/cache ^0.4.0 -> satisfiable by cache/cache[0.4.0].
- Conclusion: install csharpru/vault-php 3.5.3 (conflict analysis result)
- magento/product-community-edition 2.4.3 requires magento/module-aws-s3 100.4.1 -> satisfiable by magento/module-aws-s3[100.4.1].
- Root composer.json requires magento/product-community-edition 2.4.3 -> satisfiable by magento/product-community-edition[2.4.3].
- Root composer.json requires allure-framework/allure-phpunit ~1.2.0 -> satisfiable by allure-framework/allure-phpunit[1.2.0, ..., 1.2.4].
- cache/cache 0.4.0 requires league/flysystem ^1.0 -> satisfiable by league/flysystem[1.0.0, ..., 1.1.10].
- You can only install one version of a package, so only one of these can be installed: league/flysystem[1.0.0, ..., 1.1.10, 2.0.0, ..., 2.5.0].
- magento/module-aws-s3 100.4.1 requires league/flysystem ^2.0 -> satisfiable by league/flysystem[2.0.0, ..., 2.5.0].
- Conclusion: don't install league/flysystem 2.5.0 (conflict analysis result)
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.I'm running on Nexcess, with php 7.4, and Composer 2.4.4.
Here are the full set of commands I'm running each time to upgrade:
php bin/magento maintenance:enable
COMPOSER_MEMORY_LIMIT=-1 composer update
cp composer.json composer.json.bakb4243
bin/magento cron:remove
bin/magento cron:run --group=consumers
COMPOSER_MEMORY_LIMIT=-1 composer require magento/product-community-edition=2.4.3 --no-update
COMPOSER_MEMORY_LIMIT=-1 composer update
rm -rf var/cache/*
rm -rf var/page_cache/*
rm -rf generated/code/*
nano app/etc/di.xml
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy -f
php bin/magento cache:flush
php bin/magento maintenance:disable
I already upgraded:
2.4.2->2.4.2-p1
2.4.2-p1->2.4.2-p2
With the same commands this morning, on this same system.
I can't imagine what's wrong....
Any help on this?
Thank you!!
