Epic #47018: Implement Composer support and clean package manager API
In some matter the package manager duplicates entries in PackageState which leads to fatals
Upon installing an extension which dependencies could not be resolved I ended up with
"Fatal error: Uncaught exception 'TYPO3\Flow\Package\Exception\InvalidPackageStateException' with message 'Package "filemetadata" is already registered.' "
In the packagestates file entries for sysexts where duplicated... needed to delete the packagestates file.
#3 Updated by Steffen Ritter about 5 years ago
Yes composer.json present
a, had solr master installed version 3.0.0-dev
b, wanted to install solrfal
ext_emconf.php depency: typo3 6.2.0-6.2.99
php >= 5.3.7
solr could not be fulfilled because it is -dev....
Trying the second time I had a totatlly messed up PackageStates.php
#6 Updated by Martin Holtz about 5 years ago
i got the same issue, while updating from Beta4 to Beta6
PackageStates.php: has two entries for filemetadata
'typo3.cms.filemetadata' => array ( 'manifestPath' => '', 'composerName' => 'typo3/cms/filemetadata', 'state' => 'inactive', 'packagePath' => 'typo3/sysext/filemetadata/', 'classesPath' => 'Classes/', ),
'filemetadata' => array ( 'manifestPath' => '', 'composerName' => 'typo3/cms-filemetadata', 'state' => 'inactive', 'packagePath' => 'typo3/sysext/filemetadata/', 'classesPath' => 'Classes/', ),