Update issue from 3.0 to 4.0

[aloksinha3110]

ortliebakeneo@ortlieb-akeneo pim-community-dev]$ ea-php73 /opt/cpanel/composer/bin/composer require symfony/flex Using version ^1.15 for symfony/flex ./composer.json has been updated Running composer update symfony/flex Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages.

Problem 1

• akeneo/pim-community-dev is locked to version v4.0.123 and an update of this package was not requested.
• akeneo/pim-community-dev v4.0.123 requires symfony/flex 1.10.* -> found symfony/flex[v1.10.0] but it conflicts with your root composer.json require (^1.15).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content. [ortliebakeneo@ortlieb-akeneo pim-community-dev]$

[aloksinha3110]

Run:

• composer recipes vendor/package to see details about a recipe.
• composer recipes:install vendor/package --force -v to update that recipe.

[ortliebakeneo@ortlieb-akeneo pim-community-dev]$ composer recipes:install vendor/package --force -v Cannot update: some packages are not installed: vendor/package [ortliebakeneo@ortlieb-akeneo pim-community-dev]$

[aloksinha3110]

I have Edition CE Version 3.2.22 Need to update to 5.0 Please help me in doing so

[janmyszkier]

@aloksinha3110 your composer seems to be wrong, please use https://github.com/akeneo/pim-community-dev/blob/4.0/composer.json as a guide on what versions you should be using for 4.0 update

also, I don't think this is akeneo issue, and 3.0 is not supported already so this should not be submitted here. Feel free to find me on Akeneo slack channel, and I'll try to help you with your issue.

[Reiner030]

tha problem is that Akeneo documentation is very bad maintained ...

• Akeneo 3.1 and 3.2 need still composer 1.x while Akeneo 4.0 and 5.0 can use composer 2.x
• Akeneo 4.0 has a bug in its migration script which made me also crazy upgrading from 3.1 to 5.0 path because it didn't migrate database tables
• Akeneo 4.0 and later switches completely the setup structure. so in your case you have to call "make prod" in your test environment to get it setup.