Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting Issue Your requirements could not be resolved to an installable set of packages. during install. #237

Open
HDBear opened this issue May 15, 2024 · 1 comment

Comments

@HDBear
Copy link

HDBear commented May 15, 2024

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

Problem 1
- magento/magento-cloud-patches[1.0.21, ..., 1.0.26] require symfony/yaml ^3.3||^4.0||^5.0||^6.0 -> found symfony/yaml[v3.3.0-BETA1, ..., v3.4.47, v4.0.0-BETA1, ..., v4.4.45, v5.0.0-BETA1, ..., v5.4.39, v6.0.0-BETA1, ..., v6.4.7] but the package is fixed to v7.0.7 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- magento/magento-cloud-patches[1.0.11, ..., 1.0.14] require php ^7.0 -> your php version (8.2.19) does not satisfy that requirement.
- magento/quality-patches[1.1.0, ..., 1.1.10] require php ^7.0 -> your php version (8.2.19) does not satisfy that requirement.
- magento/magento-cloud-patches[1.0.15, ..., 1.0.18] require symfony/config ^3.3||^4.4||^5.1 -> found symfony/config[v3.3.0-BETA1, ..., v3.4.47, v4.4.0-BETA1, ..., v4.4.44, v5.1.0-BETA1, ..., v5.4.39] but the package is fixed to v6.4.7 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- magento/magento-cloud-patches[1.0.19, ..., 1.0.20] require symfony/config ^3.3||^4.4||^5.0 -> found symfony/config[v3.3.0-BETA1, ..., v3.4.47, v4.4.0-BETA1, ..., v4.4.44, v5.0.0-BETA1, ..., v5.4.39] but the package is fixed to v6.4.7 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- magento/quality-patches[1.1.11, ..., 1.1.48] require magento/magento-cloud-patches ^1.0.11 -> satisfiable by magento/magento-cloud-patches[1.0.11, ..., 1.0.26].
- Root composer.json requires magento/quality-patches ^1.1 -> satisfiable by magento/quality-patches[1.1.0, ..., 1.1.48].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require magento/quality-patches:*" to figure out if any version is installable, or "composer require magento/quality-patches:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

@HDBear
Copy link
Author

HDBear commented May 15, 2024

[-] Creating cache cleaner script: /usr/local/bin/cacheflush
#!/bin/bash
sudo -u ${SUDO_USER} n98-magerun2 --root-dir=/home/${SUDO_USER}/public_html cache:flush
/usr/bin/systemctl restart php8.2-fpm.service
nginx -t && /usr/bin/systemctl restart nginx.service || echo "[!] Error: check nginx config"

Disabling maintenance mode
Command returned non-zero exit code:
/usr/bin/php8.2 -f /home/lankaprintlk/public_html/bin/magento setup:di:compile

get 2 more errors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant