I just found about the unpack command. There was a misunderstanding on my side, because you want the versions to be non-restricted. My bad.
Because orm-pack makes no restrictions in the versions for each package, it loads the latest stable. Unfortunately there were breaking changes between DoctrineMigrationsBundle 2.2.x and 3.0. These changes are related to an "incomplete" config file which raises an InvalidConfigurationException.
I assume i just have to update that config file. But maybe that points to the question if its necessary to introduce version restrictions to orm-package libs?
Loading composer repositories with package information
Updating dependencies (including require-dev)
Restricting packages listed in "symfony/symfony" to "4.4.*"
Prefetching 6 packages 🎶 💨
- Downloading (100%)
Package operations: 0 installs, 6 updates, 0 removals
- Updating symfony/flex (v1.7.1 => v1.8.2): Loading from cache
- Updating jaybizzle/crawler-detect (v1.2.95 => v1.2.96): Loading from cache
- Updating sensio/framework-extra-bundle (v5.5.5 => v5.5.6): Loading from cache
- Updating symfony/string (v5.1.1 => v5.1.2): Loading from cache
- Updating doctrine/migrations (2.2.1 => 3.0.0): Loading from cache
- Updating doctrine/doctrine-migrations-bundle (2.1.2 => 3.0.1): Loading from cache
Package zendframework/zend-code is abandoned, you should avoid using it. Use laminas/laminas-code instead.
Package zendframework/zend-eventmanager is abandoned, you should avoid using it. Use laminas/laminas-eventmanager instead.
Afterwards running any commands results in the following exceptions:
PHP Fatal error: Uncaught Symfony\Component\Config\Definition\Exception\InvalidConfigurationException: Unrecognized options "dir_name, namespace" under "doctrine_migrations". Available options are "all_or_nothing", "check_database_platform", "connection", "custom_template", "em", "factories", "migrations", "migrations_paths", "organize_migrations", "services", "storage". in /var/www/html/vendor/symfony/config/Definition/ArrayNode.php:327
Stack trace:
#0 /var/www/html/vendor/symfony/config/Definition/BaseNode.php(382): Symfony\Component\Config\Definition\ArrayNode->normalizeValue(Array)
#1 /var/www/html/vendor/symfony/config/Definition/Processor.php(34): Symfony\Component\Config\Definition\BaseNode->normalize(Array)
#2 /var/www/html/vendor/symfony/config/Definition/Processor.php(50): Symfony\Component\Config\Definition\Processor->process(Object(Symfony\Component\Config\Definition\ArrayNode), Array)
#3 /var/www/html/vendor/symfony/dependency-injection/Extension/Extension.php(113): Symfony\Component\Config\Definition\Processor-> in /var/www/html/vendor/symfony/config/Definition/ArrayNode.php on line 327
Fatal error: Uncaught Symfony\Component\Config\Definition\Exception\InvalidConfigurationException: Unrecognized options "dir_name, namespace" under "doctrine_migrations". Available options are "all_or_nothing", "check_database_platform", "connection", "custom_template", "em", "factories", "migrations", "migrations_paths", "organize_migrations", "services", "storage". in /var/www/html/vendor/symfony/config/Definition/ArrayNode.php:327
Stack trace:
#0 /var/www/html/vendor/symfony/config/Definition/BaseNode.php(382): Symfony\Component\Config\Definition\ArrayNode->normalizeValue(Array)
#1 /var/www/html/vendor/symfony/config/Definition/Processor.php(34): Symfony\Component\Config\Definition\BaseNode->normalize(Array)
#2 /var/www/html/vendor/symfony/config/Definition/Processor.php(50): Symfony\Component\Config\Definition\Processor->process(Object(Symfony\Component\Config\Definition\ArrayNode), Array)
#3 /var/www/html/vendor/symfony/dependency-injection/Extension/Extension.php(113): Symfony\Component\Config\Definition\Processor-> in /var/www/html/vendor/symfony/config/Definition/ArrayNode.php on line 327
My doctrine_migrations.yml looks like:
doctrine_migrations:
dir_name: '%kernel.project_dir%/src/DoctrineMigrations'
# namespace is arbitrary but should be different from App\Migrations
# as migrations classes should NOT be autoloaded
namespace: DoctrineMigrations
I just found about the unpack command. There was a misunderstanding on my side, because you want the versions to be non-restricted. My bad.
Because
orm-pack
makes no restrictions in the versions for each package, it loads the latest stable. Unfortunately there were breaking changes between DoctrineMigrationsBundle 2.2.x and 3.0. These changes are related to an "incomplete" config file which raises anInvalidConfigurationException
.I assume i just have to update that config file. But maybe that points to the question if its necessary to introduce version restrictions to orm-package libs?
Ref:
My setup is:
and i ran
composer update
.Output was:
Afterwards running any commands results in the following exceptions:
My
doctrine_migrations.yml
looks like:Part of my
composer.json
: