dmaicher / doctrine-test-bundle

Symfony bundle to isolate your app's doctrine database tests and improve the test performance
MIT License
1.08k stars 60 forks source link

Impossible to update Doctrine dependencies #209

Closed hhamon closed 2 years ago

hhamon commented 2 years ago

It looks like the latest version of this bundle prevents from upgrading these Doctrine dependencies:

$ symfony composer outdated
Color legend:
- patch or minor release available - update recommended
- major release available - update possible
doctrine/deprecations v0.5.3 v1.0.0 A small layer on top of trigger_error(E_USER_DEPRECATED) or PSR-3 logging with options to disable ...
doctrine/persistence  2.5.1  3.0.2  The Doctrine Persistence project is a set of shared interfaces and functionality that the differen...

When trying to upgrade to doctrine/deprecation:^1.0.0:

symfony composer req doctrine/deprecations:^1.0.0
./composer.json has been updated
Running composer update doctrine/deprecations
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires doctrine/deprecations ^1.0.0, found doctrine/deprecations[v1.0.0] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - doctrine/dbal is locked to version 3.3.6 and an update of this package was not requested.
    - doctrine/dbal 3.3.6 requires doctrine/deprecations ^0.5.3|^1 -> found doctrine/deprecations[v0.5.3, v1.0.0] but these were not loaded, likely because it conflicts with another require.
  Problem 3
    - doctrine/migrations is locked to version 3.5.1 and an update of this package was not requested.
    - doctrine/migrations 3.5.1 requires doctrine/deprecations ^0.5.3 || ^1 -> found doctrine/deprecations[v0.5.3, v1.0.0] but these were not loaded, likely because it conflicts with another require.
  Problem 4
    - doctrine/orm is locked to version 2.12.2 and an update of this package was not requested.
    - doctrine/orm 2.12.2 requires doctrine/deprecations ^0.5.3 || ^1 -> found doctrine/deprecations[v0.5.3, v1.0.0] but these were not loaded, likely because it conflicts with another require.
  Problem 5
    - doctrine/dbal 3.3.6 requires doctrine/deprecations ^0.5.3|^1 -> found doctrine/deprecations[v0.5.3, v1.0.0] but these were not loaded, likely because it conflicts with another require.
    - dama/doctrine-test-bundle v7.0.0 requires doctrine/dbal ^3.0 -> satisfiable by doctrine/dbal[3.3.6].
    - dama/doctrine-test-bundle is locked to version v7.0.0 and an update of this package was not requested.

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.

Same when trying to upgrade doctrine/persistence:^3.0.2:

symfony composer req doctrine/persistence:^3.0.2
./composer.json has been updated
Running composer update doctrine/persistence
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires doctrine/persistence ^3.0.2, found doctrine/persistence[3.0.2] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - doctrine/doctrine-bundle is locked to version 2.6.3 and an update of this package was not requested.
    - doctrine/doctrine-bundle 2.6.3 requires doctrine/persistence ^2.2|^3 -> found doctrine/persistence[2.2.0, ..., 2.5.3, 3.0.0, 3.0.1, 3.0.2] but these were not loaded, likely because it conflicts with another require.
  Problem 3
    - doctrine/orm is locked to version 2.12.2 and an update of this package was not requested.
    - doctrine/orm 2.12.2 requires doctrine/persistence ^2.4 || ^3 -> found doctrine/persistence[2.4.0, ..., 2.5.3, 3.0.0, 3.0.1, 3.0.2] but these were not loaded, likely because it conflicts with another require.
  Problem 4
    - doctrine/doctrine-fixtures-bundle is locked to version 3.4.2 and an update of this package was not requested.
    - doctrine/doctrine-fixtures-bundle 3.4.2 requires doctrine/persistence ^1.3.7|^2.0|^3.0 -> found doctrine/persistence[1.3.7, 1.3.8, 2.0.0, ..., 2.5.3, 3.0.0, 3.0.1, 3.0.2] but these were not loaded, likely because it conflicts with another require.
  Problem 5
    - zenstruck/foundry is locked to version v1.18.2 and an update of this package was not requested.
    - zenstruck/foundry v1.18.2 requires doctrine/persistence ^1.3.3|^2.0|^3.0 -> found doctrine/persistence[1.3.3, ..., 1.3.8, 2.0.0, ..., 2.5.3, 3.0.0, 3.0.1, 3.0.2] but these were not loaded, likely because it conflicts with another require.
  Problem 6
    - doctrine/doctrine-bundle 2.6.3 requires doctrine/persistence ^2.2|^3 -> found doctrine/persistence[2.2.0, ..., 2.5.3, 3.0.0, 3.0.1, 3.0.2] but these were not loaded, likely because it conflicts with another require.
    - dama/doctrine-test-bundle v7.0.0 requires doctrine/doctrine-bundle ^2.2.2 -> satisfiable by doctrine/doctrine-bundle[2.6.3].
    - dama/doctrine-test-bundle is locked to version v7.0.0 and an update of this package was not requested.

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

Definitely not an issue with this bundle. It does not even require any specific versions for doctrine/deprecations and doctrine/persistence.

See https://github.com/dmaicher/doctrine-test-bundle/blob/master/composer.json#L19

What makes you think its an issue here?

hhamon commented 2 years ago

@dmaicher my bad you're right! I've uninstalled the dama/doctrine-test-bundle and then tried to update those dependencies. I'm getting the same problem. Looks like the dependencies conflicts comes from another third party bundle. Closing this issue then.