The result is (which I think is strange and I have no clue yet):
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
drupal/core-dev[9.2.0-alpha1, ..., 9.4.x-dev] require symfony/css-selector ^4.4 -> found symfony/css-selector[v4.4.0-BETA1, ..., 4.4.x-dev] but the package is fixed to v5.3.4 (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.
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 drupal/core-dev:*" to figure out if any version is installable, or "composer require drupal/core-dev:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
composer [require --dev drupal/core-dev drush/drush phpunit/phpunit drupal/coder phpspec/prophecy-phpunit drupal/devel drupal/devel_debug_log drupal/devel_php] failed, composer command failed: exit status 2. stderr=
"ddev composer require --dev drupal/core-dev drush/drush phpunit/phpunit drupal/coder phpspec/prophecy-phpunit drupal/devel drupal/devel_debug_log drupal/devel_php" command filed with exit code 1.
Failed to run drowl-init-from-existing.sh ; error=exit status 1
JPustkuchen
commented
1 year ago
For example for a composer.json with:
The result is (which I think is strange and I have no clue yet):