Can't install laminas-cache on a fresh mvc installation

[Bro3x]

Composer fails with Version mismatch.

composer require laminas/laminas-mvc
Using version ^3.7 for laminas/laminas-mvc
./composer.json has been updated
Running composer update laminas/laminas-mvc
Loading composer repositories with package information
In Laminas\DependencyPlugin\DependencyRewriterV2::onPrePoolCreate
Updating dependencies
Lock file operations: 19 installs, 0 updates, 0 removals
  - Locking brick/varexporter (0.5.0)
  - Locking laminas/laminas-config (3.9.0)
  - Locking laminas/laminas-escaper (2.14.0)
  - Locking laminas/laminas-eventmanager (3.13.1)
  - Locking laminas/laminas-http (2.20.0)
  - Locking laminas/laminas-json (3.7.0)
  - Locking laminas/laminas-loader (2.11.0)
  - Locking laminas/laminas-modulemanager (2.16.0)
  - Locking laminas/laminas-mvc (3.7.0)
  - Locking laminas/laminas-router (3.14.0)
  - Locking laminas/laminas-servicemanager (3.22.1)
  - Locking laminas/laminas-stdlib (3.19.0)
  - Locking laminas/laminas-uri (2.12.0)
  - Locking laminas/laminas-validator (2.64.1)
  - Locking laminas/laminas-view (2.35.0)
  - Locking nikic/php-parser (v5.3.1)
  - Locking psr/container (1.1.2)
  - Locking psr/http-message (2.0)
  - Locking webimpress/safe-writer (2.2.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 19 installs, 0 updates, 0 removals
  - Downloading psr/container (1.1.2)
  - Downloading laminas/laminas-config (3.9.0)
  - Downloading laminas/laminas-servicemanager (3.22.1)
  - Downloading psr/http-message (2.0)
  - Downloading webimpress/safe-writer (2.2.0)
  - Downloading laminas/laminas-mvc (3.7.0)
  - Installing nikic/php-parser (v5.3.1): Extracting archive
  - Installing brick/varexporter (0.5.0): Extracting archive
  - Installing psr/container (1.1.2): Extracting archive
  - Installing laminas/laminas-stdlib (3.19.0): Extracting archive
  - Installing laminas/laminas-config (3.9.0): Extracting archive
  - Installing laminas/laminas-loader (2.11.0): Extracting archive
  - Installing laminas/laminas-servicemanager (3.22.1): Extracting archive
  - Installing laminas/laminas-json (3.7.0): Extracting archive
  - Installing laminas/laminas-eventmanager (3.13.1): Extracting archive
  - Installing laminas/laminas-escaper (2.14.0): Extracting archive
  - Installing laminas/laminas-view (2.35.0): Extracting archive
  - Installing psr/http-message (2.0): Extracting archive
  - Installing laminas/laminas-validator (2.64.1): Extracting archive
  - Installing laminas/laminas-uri (2.12.0): Extracting archive
  - Installing laminas/laminas-http (2.20.0): Extracting archive
  - Installing laminas/laminas-router (3.14.0): Extracting archive
  - Installing webimpress/safe-writer (2.2.0): Extracting archive
  - Installing laminas/laminas-modulemanager (2.16.0): Extracting archive
  - Installing laminas/laminas-mvc (3.7.0): Extracting archive

composer require laminas/laminas-cache
Using version ^4.0 for laminas/laminas-cache
./composer.json has been updated
Running composer update laminas/laminas-cache
Loading composer repositories with package information
In Laminas\DependencyPlugin\DependencyRewriterV2::onPrePoolCreate
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires laminas/laminas-cache ^4.0 -> satisfiable by laminas/laminas-cache[4.0.0, ..., 4.0.4].
    - laminas/laminas-cache[4.0.0, ..., 4.0.4] require laminas/laminas-servicemanager ^4.1 -> found laminas/laminas-servicemanager[4.1.0, 4.2.0, 4.2.1] but the package is fixed to 3.22.1 (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 laminas/laminas-cache:*" to figure out if any version is installable, or "composer require laminas/laminas-cache:^2.1" if you know which you need.

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

How to reproduce

see above

Expected behavior

Installing the appropriate laminas cache version

[gsteel]

Cache v4 uses service manager v4 which conflicts with mvc requirements of service manager v3.

This isn't a bug, mvc simply does not support the latest version of service manager yet.

You'll have to install cache v3 for now.

[driehle]

However, cache v3 is not supporting PHP 8.4. Would it make sense to have cache v3 support PHP 8.4? I guess this could be easily provided by a PR.

[froschdesign]

@driehle
This will not work because the adapters with support for version 3 of laminas-cache does not support for version 8.4 of PHP.

Example

https://github.com/laminas/laminas-cache-storage-adapter-filesystem/blob/781907961479ac8c7b27b91f10851025bf1dea6b/composer.json#L9-L12

https://github.com/laminas/laminas-cache-storage-adapter-filesystem/blob/5f1329a1da9a68f862d693bdfa5d080cec72ec5d/composer.json#L9-L13

[driehle]

Obviously, this would have to be done for the adapters as well. However, I agree this would be too much effort. For DoctrineModule we'll likely switch to symfony/cache, as discussed in doctrine/DoctrineORMModule#767.