TYPO3 Core

Did you test current master as of today evening?

For some reason, package manager wants to write to PackageState.php on each page reload (even if the file is writable).
The condition
if ($this->packageStatesConfiguration != $previousPackageStatesConfiguration) {
from line 389 of typo3/sysext/core/Classes/Package/PackageManager.php
is always true...

After comparing both arrays the only difference is 'classesPath' value for
'Doctrine.Instantiator' and 'mikey179.vfsStream' and 'symfony.yaml'

$previousPackageStatesConfiguration

'Doctrine.Instantiator' => 
    array (
      'manifestPath' => '',
      'composerName' => 'doctrine/instantiator',
      'state' => 'inactive',
      'packagePath' => 'Packages/Libraries/doctrine/instantiator/',
      'classesPath' => 'src/',
      'suggestions' => 
      array (
      ),
    ),
...
'mikey179.vfsStream' => 
    array (
      'manifestPath' => '',
      'composerName' => 'mikey179/vfsStream',
      'state' => 'inactive',
      'packagePath' => 'Packages/Libraries/mikey179/vfsStream/',
      'classesPath' => 'src/main/php/',
      'suggestions' => 
      array (
      ),
    ),
...
 'symfony.yaml' => 
    array (
      'manifestPath' => 'Symfony/Component/Yaml/',
      'composerName' => 'symfony/yaml',
      'state' => 'inactive',
      'packagePath' => 'Packages/Libraries/symfony/yaml/',
      'classesPath' => '',
      'suggestions' => 
      array (
      ),
    ),

$this->packageStatesConfiguration

'Doctrine.Instantiator' =>
    array (
      'manifestPath' => '',
      'composerName' => 'doctrine/instantiator',
      'state' => 'inactive',
      'packagePath' => 'Packages/Libraries/doctrine/instantiator/',
      'classesPath' => 'Classes/',
      'suggestions' =>
      array (
      ),
    ),

'mikey179.vfsStream' =>
    array (
      'manifestPath' => '',
      'composerName' => 'mikey179/vfsStream',
      'state' => 'inactive',
      'packagePath' => 'Packages/Libraries/mikey179/vfsStream/',
      'classesPath' => 'Classes/',
      'suggestions' =>
      array (
      ),
    ),
'symfony.yaml' =>
    array (
      'manifestPath' => 'Symfony/Component/Yaml/',
      'composerName' => 'symfony/yaml',
      'state' => 'inactive',
      'packagePath' => 'Packages/Libraries/symfony/yaml/',
      'classesPath' => 'Classes/',
      'suggestions' =>
      array (
      ),
    ),

have you run composer update before? e.g. for running unit tests?

I always copy the composer.json from typo3_src into web-root and run composer update.

What's the state of this issue?

Can this "break" existing 6.2 installations?

Markus Klein wrote:

Can this "break" existing 6.2 installations?

no. The thing is, that in the PackageStates.php file the classes path is always "Classes" this is the case before and after the patch
The only difference is, that the PackageStates.php file is not rewritten any more if composer packages are used, which have a psr-0 autoload section defined (which triggers a cache rebuild, which is quite expensive)

6.2 installations without composer packages are not affected, neither before, nor after the patch

Then I think 6.2 should get that one too.