Bug #84617
closedGenerating package states stopped working as expected after updates in symfony/finder component
0%
Description
After updates in symfony/finder component https://github.com/symfony/finder/commit/c72995d9f5999b3fcdd8660c0c9690243252e1e1 running now "php vendor/bin/typo3cms install:generatepackagestates" is having trouble installing packages because of the real path.
The wrong path now is showin only for sysext and not for custom extension (e.g. ext:news).
How to replicate:- Have one custom extension which also depends in "core" extension.
- Delete all extension in PackageStates.php
- Try to run in cli "php vendor/bin/typo3cms install:generatepackagestates"
Result:
[ UnexpectedValueException ]
The package "some extension" depends on "core" which is not present in the system.
Note: The reason for this error is the wrong path now because of symfony finder component
Expected result:
The following extensions have been added to the generated PackageStates.php file: core, extbase, fluid, ....
Suggestion:
A solution can be modifying PackageManager.php->registerPackagesFromConfiguration(...)
$sysExtension = strpos($stateConfiguration['packagePath'], 'sysext');
if ($sysExtension !== false) {
$packagePath = PathUtility::sanitizeTrailingSeparator($stateConfiguration['packagePath']);
} else {
$packagePath = PathUtility::sanitizeTrailingSeparator($this->packagesBasePath . $stateConfiguration['packagePath']);
}
Updated by Helmut Hummel over 6 years ago
- Is duplicate of Bug #84601: Installation fails with "extbase" not found exception added
Updated by Helmut Hummel over 6 years ago
- Status changed from New to Closed
thanks for the report.
a fix for that (adding a conflict) has been merged already.
closed as duplicate
Updated by Stephan Großberndt over 6 years ago
- Subject changed from Generating package states stoped working as expected after updates in symfony/finder component to Generating package states stopped working as expected after updates in symfony/finder component