Contrib.social

Won't install on a fresh drupal 11

Open on Drupal.org →
Created on 10 September 2024, 2 months ago

Problem/Motivation

Won't install on a fresh Drupal 11

Steps to reproduce

leo@mint-leo-Dell:~/projects/drupal11$ ddev composer require 'drupal/tasks:^2.0@beta'
./composer.json has been updated
Running composer update drupal/tasks
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires drupal/tasks ^2.0@beta -> satisfiable by drupal/tasks[2.0.0-beta1].
- drupal/tasks 2.0.0-beta1 requires drupal/core ~8.0 -> found drupal/core[8.0.0, ..., 8.9.20] but the package is fixed to 11.0.2 (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.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
Composer [require drupal/tasks:^2.0@beta] failed, composer command failed: exit status 2. stderr=
leo@mint-leo-Dell:~/projects/drupal11$ ddev composer require 'drupal/tasks:^1.0'
./composer.json has been updated
Running composer update drupal/tasks
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- drupal/tasks[1.0.0, ..., 1.0.1] require drupal/core ^8 || ^9 -> found drupal/core[8.0.0, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 11.0.2 (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.
- drupal/tasks 1.0.2 requires drupal/core ^8 || ^9 || ^10 -> found drupal/core[8.0.0, ..., 8.9.20, 9.0.0, ..., 9.5.11, 10.0.0, ..., 10.3.3] but the package is fixed to 11.0.2 (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.
- drupal/tasks 1.0.3 requires drupal/flag ^4.0@beta -> found drupal/flag[dev-4.x, 4.0.0-alpha1, ..., 4.x-dev (alias of dev-4.x)] but it does not match your minimum-stability.
- Root composer.json requires drupal/tasks ^1.0 -> satisfiable by drupal/tasks[1.0.0, 1.0.1, 1.0.2, 1.0.3].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

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

🐛 Bug report
Status

Active

Version

2.0

Component

Code

Created by

🇦🇷Argentina leofishman

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @leofishman
  • Comment about 1 month ago →
    🇦🇺Australia jasp888

    I'm experiencing a similar issue:

    ubuntu@drupal:/var/www/directory1/site_portal$ composer require 'drupal/css_editor:^2.0' -W
    ./composer.json has been updated
    Running composer update drupal/css_editor --with-all-dependencies
    Loading composer repositories with package information
    Updating dependencies
    Your requirements could not be resolved to an installable set of packages.

    Problem 1
    - drupal/css_editor 2.0.1 requires drupal/core ^8 || ^9 -> found drupal/core[8.0.0, ..., 8.9.20, 9.0.0, ..., 9.5.11] but these were not loaded, likely because it conflicts with another require.
    - drupal/css_editor 2.0.2 requires drupal/core ^9 || ^10 -> found drupal/core[9.0.0, ..., 9.5.11, 10.0.0, ..., 10.3.6] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires drupal/css_editor ^2.0 -> satisfiable by drupal/css_editor[2.0.1, 2.0.2].

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

    ???

    I used the recommended composer install:
    $ composer create-project drupal/recommended-project my_site_name

    Any suggestions would be appreciated - thks!

  • First commit to issue fork.
  • Merge request !1Resolve #3473270 "Wont install on" → (Open) created by Unnamed author
  • Comment 19 days ago →
    🇮🇳India abhinesh

    Drupal.org appends metadata to the code associated with the module page, specifically incorporating "drupal/core ~8.0" automatically. I encountered a similar challenge with one of my recipes. The resolution that proved effective was altering the project type from "module" to "general projects."

    https://www.drupal.org/project/infrastructure/issues/3483086 💬 Request to Change Project Type Active

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024