- Issue created by @HasinaNjaratin
- Status changed to Closed: cannot reproduce
over 1 year ago 11:20pm 20 September 2023 - 🇫🇷France HasinaNjaratin
This is cause of wrong version of drupal core. to fix it, make sure getting a right drupal core version.
- 🇺🇸United States codechefmarc
Hi HasinaNjaratin, I'm running into this as well. You mentioned that the fix is to get the right Drupal core version. I've got the following in my root
composer.json
file:"drupal/core-composer-scaffold": "^10", "drupal/core-project-message": "^10", "drupal/core-recommended": "^10",
Which should get us 10.1, but I'm still getting errors like you were. What did you eventually put as your Drupal version to make this work? Thanks!
- 🇮🇸Iceland drupalviking
+2 on this, I had a problem updating to 10. The best I can go now is 10.0.0 :-(
I get similar errors:
Problem 1 - Root composer.json requires drupal/core-recommended ^10.1, found drupal/core-recommended[10.1.0-alpha1, ..., 10.2.x-dev] but the package is fixed to 10.0.0 (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. Problem 2 - drupal/twig_tweak is locked to version 3.2.1 and an update of this package was not requested. - drupal/twig_tweak 3.2.1 requires twig/twig ^2.12 || ^3.3.8 -> found twig/twig[v2.12.0, ..., 2.x-dev, v3.3.8, ..., 3.x-dev] but these were not loaded, likely because it conflicts with another require. Problem 3 - drupal/core 10.0.0 requires twig/twig ^3.4.3 -> found twig/twig[v3.4.3, ..., 3.x-dev] but these were not loaded, likely because it conflicts with another require. - drupal/stage_file_proxy 2.1.3 requires drupal/core ^9 || ^10 -> satisfiable by drupal/core[10.0.0]. - drupal/stage_file_proxy is locked to version 2.1.3 and an update of this package was not requested. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions. Composer [update twig/twig:3.6 --dry-run] failed, composer command failed: exit status 2. stderr=
- Status changed to Active
11 months ago 4:32pm 12 January 2024 - 🇮🇸Iceland drupalviking
I opened this issue again since I just encountered this problem today, so clairly I was able to reproduce.
- 🇷🇺Russia Chi
Use the option --with-all-dependencies (-W) to allow upgrades,
Have you tried this?
Composer is known for its pure description of dependency conflicts. Sometimes it's easier to just remove the package that you think is blocking update, then update what you need and install the package again.
- Status changed to Closed: cannot reproduce
11 months ago 5:57am 28 January 2024