Closed eerison closed 2 years ago
well the first update of 3.x was smoothly, But in this one I got too much conflicts between dependencies :/
Can you show what kind of dependency problems you got?
Problem 1
- Root composer.json requires sonata-project/page-bundle 3.x-dev as 3.26.0 -> satisfiable by sonata-project/page-bundle[3.x-dev].
- sonata-project/page-bundle 3.x-dev requires doctrine/doctrine-bundle ^2.5 -> found doctrine/doctrine-bundle[2.5.0, ..., 2.7.0] but it conflicts with your root composer.json require (^1.12).
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
then I try to req the doctrine/doctrine-bundle ^2.5
and I get those errors
Problem 1
- Root composer.json requires sonata-project/page-bundle 3.x-dev as 3.26.0, found sonata-project/page-bundle[3.x-dev] but the package is fixed to 3.26.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 2
- doctrine/doctrine-migrations-bundle is locked to version v1.3.2 and an update of this package was not requested.
- doctrine/doctrine-migrations-bundle v1.3.2 requires doctrine/doctrine-bundle ~1.0 -> found doctrine/doctrine-bundle[v1.0.0, ..., 1.12.13] but it conflicts with your root composer.json require (^2.5).
Problem 3
- doctrine/orm is locked to version 2.7.5 and an update of this package was not requested.
- sonata-project/doctrine-orm-admin-bundle 3.35.3 requires doctrine/doctrine-bundle ^1.8 || ^2.0 -> satisfiable by doctrine/doctrine-bundle[2.5.0, ..., 2.7.0].
- doctrine/doctrine-bundle 2.7.0 conflicts with doctrine/doctrine-bundle 2.7.0.
- doctrine/doctrine-bundle 2.6.4 conflicts with doctrine/doctrine-bundle 2.6.4.
- doctrine/doctrine-bundle 2.6.3 conflicts with doctrine/doctrine-bundle 2.6.3.
- doctrine/doctrine-bundle 2.6.2 conflicts with doctrine/doctrine-bundle 2.6.2.
- doctrine/doctrine-bundle 2.6.1 conflicts with doctrine/doctrine-bundle 2.6.1.
- doctrine/doctrine-bundle 2.6.0 conflicts with doctrine/doctrine-bundle 2.6.0.
- doctrine/doctrine-bundle 2.5.7 conflicts with doctrine/doctrine-bundle 2.5.7.
- doctrine/doctrine-bundle 2.5.6 conflicts with doctrine/doctrine-bundle 2.5.6.
- doctrine/doctrine-bundle 2.5.5 conflicts with doctrine/doctrine-bundle 2.5.5.
- doctrine/doctrine-bundle 2.5.4 conflicts with doctrine/doctrine-bundle 2.5.4.
- doctrine/doctrine-bundle 2.5.3 conflicts with doctrine/doctrine-bundle 2.5.3.
- doctrine/doctrine-bundle 2.5.2 conflicts with doctrine/doctrine-bundle 2.5.2.
- doctrine/doctrine-bundle 2.5.1 conflicts with doctrine/doctrine-bundle 2.5.1.
- doctrine/doctrine-bundle 2.5.0 conflicts with doctrine/doctrine-bundle 2.5.0.
- sonata-project/doctrine-orm-admin-bundle is locked to version 3.35.3 and an update of this package was not requested.
and then composer req doctrine/doctrine-bundle:^2.5 sonata-project/doctrine-orm-admin-bundle:^3.0 -W
Problem 1
- Root composer.json requires sonata-project/page-bundle 3.x-dev as 3.26.0, found sonata-project/page-bundle[3.x-dev] but the package is fixed to 3.26.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 2
- doctrine/doctrine-migrations-bundle is locked to version v1.3.2 and an update of this package was not requested.
- doctrine/doctrine-migrations-bundle v1.3.2 requires doctrine/doctrine-bundle ~1.0 -> found doctrine/doctrine-bundle[v1.0.0, ..., 1.12.13] but it conflicts with your root composer.json require (^2.5).
Problem 3
- api-platform/core is locked to version v2.6.8 and an update of this package was not requested.
- Conclusion: don't install doctrine/doctrine-bundle 2.5.2 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.5.3 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.5.4 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.5.5 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.5.6 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.5.7 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.6.0 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.6.1 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.6.2 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.6.3 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.6.4 (conflict analysis result)
- Conclusion: don't install doctrine/doctrine-bundle 2.7.0 (conflict analysis result)
- doctrine/orm[2.8.2, ..., 2.9.6] require doctrine/common ^3.0.3 -> satisfiable by doctrine/common[3.0.3, ..., 3.3.0].
- doctrine/orm[2.8.0, ..., 2.8.1] require doctrine/common ^3.0 -> satisfiable by doctrine/common[3.0.0, ..., 3.3.0].
- You can only install one version of a package, so only one of these can be installed: doctrine/common[2.2.0, ..., 2.13.3, 3.0.0, ..., 3.3.0].
- orf/transcoding-bundle 0.7.5 requires doctrine/common ^2.2 -> satisfiable by doctrine/common[2.2.0, ..., 2.13.3].
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 3.2.1.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 3.2.0.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 3.1.2.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 3.1.1.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 3.1.0.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 3.0.3.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 3.0.2.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 3.0.1.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 3.0.0.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 2.13.2.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 2.13.1.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 2.13.0.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common 2.12.0.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common v2.11.0.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common v2.10.0.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common v2.9.0.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common v2.8.1.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common v2.8.0.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common v2.7.3.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common v2.7.2.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common v2.7.1.
- myclabs/deep-copy 1.11.0 conflicts with doctrine/common v2.7.0.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.12.3.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.12.2.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.12.1.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.12.0.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.11.3.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.11.2.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.11.1.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.11.0.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.10.5.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.10.4.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.10.3.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.10.2.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.10.1.
- gedmo/doctrine-extensions v3.2.0 conflicts with doctrine/orm 2.10.0.
- roave/security-advisories dev-master conflicts with doctrine/orm 2.8.3.
- phpunit/phpunit 8.5.26 requires myclabs/deep-copy ^1.10.0 -> satisfiable by myclabs/deep-copy[1.11.0].
- stof/doctrine-extensions-bundle v1.7.0 requires gedmo/doctrine-extensions ^2.3.4 || ^3.0.0 -> satisfiable by gedmo/doctrine-extensions[v3.2.0].
- api-platform/core v2.6.8 conflicts with doctrine/common v2.6.2.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.6.1.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.6.0.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.5.3.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.5.2.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.5.1.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.5.0.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.4.3.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.4.2.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.4.1.
- api-platform/core v2.6.8 conflicts with doctrine/common v2.4.0.
- api-platform/core v2.6.8 conflicts with doctrine/common 2.3.0.
- api-platform/core v2.6.8 conflicts with doctrine/common 2.2.3.
- api-platform/core v2.6.8 conflicts with doctrine/common 2.2.2.
- api-platform/core v2.6.8 conflicts with doctrine/common 2.2.1.
- api-platform/core v2.6.8 conflicts with doctrine/common 2.2.0.
- orf/transcoding-bundle is locked to version 0.7.5 and an update of this package was not requested.
- stof/doctrine-extensions-bundle is locked to version v1.7.0 and an update of this package was not requested.
- doctrine/doctrine-fixtures-bundle is locked to version 3.4.2 and an update of this package was not requested.
- phpunit/phpunit is locked to version 8.5.26 and an update of this package was not requested.
- roave/security-advisories is locked to version dev-master and an update of this package was not requested.
- Conclusion: don't install doctrine/doctrine-bundle 2.5.1 (conflict analysis result)
- doctrine/doctrine-fixtures-bundle 3.4.2 requires doctrine/orm ^2.6.0 -> satisfiable by doctrine/orm[v2.7.0, ..., 2.12.3].
- doctrine/doctrine-bundle 2.5.0 conflicts with doctrine/orm 2.7.5.
- doctrine/doctrine-bundle 2.5.0 conflicts with doctrine/orm 2.7.4.
- doctrine/doctrine-bundle 2.5.0 conflicts with doctrine/orm v2.7.3.
- doctrine/doctrine-bundle 2.5.0 conflicts with doctrine/orm v2.7.2.
- doctrine/doctrine-bundle 2.5.0 conflicts with doctrine/orm v2.7.1.
- doctrine/doctrine-bundle 2.5.0 conflicts with doctrine/orm v2.7.0.
- Root composer.json requires doctrine/doctrine-bundle ^2.5 -> satisfiable by doctrine/doctrine-bundle[2.5.0, ..., 2.7.0].
Before starting to bump SonataPageBundle you'll need to bump doctrine.
try
doctrine/doctrine-bundle ^2.7
doctrine/doctrine-migrations-bundle ^3.2
doctrine/orm ^2.12
doctrine/common ^3.3
Before starting to bump SonataPageBundle you'll need to bump doctrine.
try
doctrine/doctrine-bundle ^2.7 doctrine/doctrine-migrations-bundle ^3.2 doctrine/orm ^2.12 doctrine/common ^3.3
well it's not "just" bump 😄 , it starts to touch in others dependencies and so on, well as I said without touch in doctrine dependencies it was easy to update, when you force me to bump, I need to change more things from my side, But I guess it's not a really problem, because the people need to do this now or in 4.x
, I guess we could do this only in 4.x, But it will be more work to let this working as before and apply those changes only in 4.x
.
and I'm still struggle with dependencies from the project that I'm working on!
But I guess I'm almost there (I hope 😄 )
it's my current blocks
Problem 1
- Root composer.json requires sonata-project/page-bundle 3.x-dev as 3.26.0 -> satisfiable by sonata-project/page-bundle[3.x-dev].
- Conclusion: don't install doctrine/persistence 1.3.1 (conflict analysis result)
- Conclusion: don't install doctrine/persistence 2.2.2 (conflict analysis result)
- Conclusion: don't install doctrine/persistence 1.3.2 (conflict analysis result)
- Conclusion: don't install doctrine/persistence 2.2.3 (conflict analysis result)
- Conclusion: don't install doctrine/persistence[2.4.0] | install doctrine/persistence[1.3.3] (conflict analysis result)
- Conclusion: don't install doctrine/persistence[1.3.3] | install one of doctrine/persistence[2.2.4, 2.3.0] (conflict analysis result)
- Conclusion: don't install doctrine/persistence[2.3.0] | install doctrine/persistence[1.3.5] (conflict analysis result)
- Conclusion: don't install doctrine/persistence[2.2.4] | install doctrine/persistence[1.3.5] (conflict analysis result)
- Conclusion: don't install doctrine/persistence 1.3.5 (conflict analysis result)
- Conclusion: don't install doctrine/persistence 2.4.1 (conflict analysis result)
- Conclusion: don't install doctrine/persistence 2.4.2 (conflict analysis result)
- Conclusion: don't install doctrine/persistence 2.5.0 (conflict analysis result)
- Conclusion: don't install doctrine/persistence 2.5.1 (conflict analysis result)
- Conclusion: don't install doctrine/persistence 2.5.2 (conflict analysis result)
- Conclusion: don't install doctrine/persistence 2.5.3 (conflict analysis result)
- sonata-project/page-bundle 3.x-dev requires doctrine/persistence ^2.1 -> satisfiable by doctrine/persistence[2.1.0, ..., 2.5.3].
- You can only install one version of a package, so only one of these can be installed: doctrine/persistence[v1.0.0, ..., 1.3.8, 2.0.0, ..., 2.5.3, 3.0.0, 3.0.1, 3.0.2].
- Conclusion: install one of doctrine/persistence[1.3.0, ..., 1.3.5] (conflict analysis result)
What version do you have of doctrine/persistence?
What version do you have of doctrine/persistence?
1.3.8
You need at least ^2.1
Good thing about those updates is you can do them before updating SonataPageBundle. When you have them all in place, then you can update SonataPageBundle and be kind of ready for 4.0
Good thing about those updates is you can do them before updating SonataPageBundle. When you have them all in place, then you can update SonataPageBundle and be kind of ready for 4.0
exactly, I can identify many depends that are not necessary or that should be updated already.
Finally I could use 3.x ❤️ , now I can test it :)
well I could install the 3.x
, But I got others issues related with translation :'(, I can not test it for the project that I'm working on, it need to be updated first we were stuck by php 7.2
, and it wasn't updated yet, I was trying to update this in a different branch (using php 7.4, But there are a lot of things to do, I fix one thing and appear other shit), what I can do is test in other small project that I created. what do you think?
it need to be updated first we were stuck by php 7.2
Oh, good luck with the update. Be aware 7.4 is soon EOL and previous version are already ^^
what I can do is test in other small project that I created. what do you think?
If it doesn't take too much time on your side it would be great.
Hey @VincentLanglet
what I tested
and averything looks good, do you have anything else in mind?
@VincentLanglet @jordisala1991 @Hanmac
I'm creating this issue just to note the results before release 3.27 release