#110291Extension list and status report break on conflicting dependency versions
Description
Problem
“ListUtility::getUpdateableVersion()” reports whether a newer version of an
installed extension is available. It walks the update candidates of an extension
key, newest first, and returns the first one whose dependencies resolve.
Determining that is a query, but “DependencyUtility::checkDependencies()” marks
dependent extensions for download, update and installation as a side effect.
Those queues are shared, so every probed candidate leaves its dependencies
behind – including the candidates which have been rejected, and those of all
extensions listed before.
Impact
Extension keys maintained for two core versions in parallel turn this into a
hard error. Their major lines depend on different major versions of a shared
base extension, so probing them queues that base extension twice in conflicting
versions and “DownloadQueue::addExtensionToQueue()” throws:
bc. TYPO3\CMS\Extensionmanager\Exception\ExtensionManagerException:
deepl_base was requested to be downloaded in different versions (2.0.2 and 1.0.3).
The exception aborts
“ListUtility::getAvailableAndInstalledExtensionsWithAdditionalInformation()”,
which renders the Extension Manager list module and feeds the extension status
report of EXT:reports. Both break entirely, although the request is not going to
download anything at all.
Reproduction
A functional test covering the constellation is part of the patch. It registers
TER records for three extensions, where a shared base extension is offered in
two major version lines – one for the previous and current core version, one for
the current and next core version – and is required in conflicting major
versions by the two depending extensions.
The constellation is not artificial. It is the release layout of
“deepltranslate_core”, “deepl_write” and their shared base extension
“deepl_base”, which is what surfaced the problem.
Affected versions
The affected code is identical in main and 14.3, and equivalent in 13.4 (still
on the Extbase mapped model with getters). All three branches are affected.