TYPO3 Core

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
solr: '3.0.0'

composer.json depency
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

Hi,

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/',
    ),

I got exactly the same problem (two filemetadata entries in PackageStates.php), upgrading from 6.1.5 to 6.2.2.

So the problem, not only exists between Beta versions, but also when upgrading from a Stable Release.

I'm sorry, forget what I wrote above. It doesn't happen, if you properly update from 6.1 to 6.2.

One of my colleagues pushed a PackageStates.php file, he created with RC1, which lead to my problems during upgrade.