Issue Bug Closed

#67542TYPO3 6.2.13 - The package "install" depends on "typo3/cms-extbase" which is not present in the system.

Christoph Lehmann 06/17/15, 11:09 updated 10/02/18, 11:44

Description

I updated from 6.2.12 to 6.2.13, cleared all caches and can’t execute the Extension Manager with the Exception

The package “install” depends on “typo3/cms-extbase” which is not present in the system.

The PackageStates.php looks like this

    'extbase' => 
    array (
      'state' => 'active',
      'packagePath' => 'typo3/sysext/extbase/',
      'classesPath' => 'Classes/',
      'manifestPath' => '',
      'composerName' => 'typo3/cms-extbase',
      'suggestions' => 
      array (
      ),
    ),

…

    'install' =>
    array (
      'manifestPath' => '',
      'composerName' => 'typo3/cms-install',
      'state' => 'active',
      'packagePath' => 'typo3/sysext/install/',
      'classesPath' => 'Classes/',
      'suggestions' =>
      array (
      ),
    ),

And the composer.json of the install extension

{
        "name": "typo3/cms-install",
        "type": "typo3-cms-framework",
        "description": "TYPO3 Core",
        "homepage": "http://typo3.org",
        "license": ["GPL-2.0+"],
        "version": "6.2.0",

        "require": {
                "typo3/cms-core": "*",
                "typo3/cms-fluid": "*",
                "typo3/cms-extbase": "*"
        },
        "replace": {
                "install": "*"
        },
        "extra": {
                "typo3/cms": {
                        "Package": {
                                "protected": true,
                                "partOfFactoryDefault": true,
                                "partOfMinimalUsableSystem": true
                        }
                }
        },
        "autoload": {
                "psr-4": {
                        "TYPO3\\CMS\\Install\\": "Classes/"
                }
        },
        "autoload-dev": {
                "psr-4": {
                        "TYPO3\\CMS\\Install\\Tests\\": "Tests/"
                }
        }
}

What to do now?

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.