Problem/Motivation

composer update -W "drupal/core-recommended:9.4.8" --dry-run
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/core-recommended ^9 -> satisfiable by drupal/core-recommended[9.4.8].
- drupal/wysiwyg_linebreaks 1.11.0 requires drupal/ckeditor * -> satisfiable by drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.4.3, 10.0.0-alpha1, ..., 10.1.x-dev].
- You can only install one version of a package, so only one of these can be installed: drupal/core[9.3.0-alpha1, ..., 9.5.x-dev].
- drupal/minimalhtml 1.4.0 requires drupal/wysiwyg_linebreaks ^1.9 -> satisfiable by drupal/wysiwyg_linebreaks[1.11.0].
- drupal/core-recommended 9.4.8 requires drupal/core 9.4.8 -> satisfiable by drupal/core[9.4.8].
- drupal/minimalhtml is locked to version 1.4.0 and an update of this package was not requested.

composer [update -W drupal/core-recommended:9.4.8 --dry-run] failed, composer command failed: exit status 2. stderr=

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

mlncn created an issue. See original summary.

mlncn’s picture

mlncn CreditAttribution: mlncn at Agaric for Drutopia commented

For this module maybe we can get away with removing the requirement in the .info file. But what exactly is a module that has ckeditor integration supposed to do?

Remove actual requirement so Drupal won't break

Drupal is doing something very weird, seemingly interpreting this line
which is clearly about the core ckeditor module as something composer
has to go fetch, which is ridiculous, especially since we already have
a composer.json which should be taking precedence over any incorrect
ideas Drupal's shadow packaging system dreams up.

And that leads to holding whole damn sites back at Drupal 9.4.3 and
people are doing various weird workarounds, but what we have to do
here is the weirdest yet.

Related issues:

- https://www.drupal.org/project/ckeditor_config/issues/3309026
- https://www.drupal.org/project/drupal/issues/3309063
- https://www.drupal.org/project/drupal/issues/3292380#comment-14619332
- https://www.drupal.org/project/ckeditor_mentions/issues/3304251

mlncn’s picture

mlncn CreditAttribution: mlncn at Agaric for Drutopia commented
Status: Active » Reviewed & tested by the community

Composer was just lying. The actual module was never mentioned until using this approach, below, to identify the problem.

If you are stuck on Drupal 9.4.3 here is how to find out why:

  1. Edit your composer.json file to have an explicit requirement on "drupal/core-recommended": "9.4.8",
  2. Run composer update
  3. The last problem it lists will give the module that has the old "replace" approach that needs to be fixed.
Anybody’s picture

Anybody
Primary language German
Location Porta Westfalica
CreditAttribution: Anybody at DROWL.de commented

FYI: I never had this issue on any site. We were able to upgrade to ^9.5 successfully.

mlncn’s picture

mlncn CreditAttribution: mlncn at Agaric for Drutopia commented
Status: Reviewed & tested by the community » Postponed (maintainer needs more info)

Yeah… i made a 2.0.x branch and a 2.0.0 release dropping any requirement related to ckeditor just in case. Other modules involving CKEditor are talking about maintaining two branches, one for contrib ckeditor and one for core.