webfactory / piwik-bundle

Symfony Bundle with twig-function for the Matomo (fka Piwik) tracking code
MIT License
39 stars 16 forks source link

Current version of piwik-bundle can't be installed onto symfony 6.3 #44

Closed computamike closed 11 months ago

computamike commented 11 months ago

There seems to be some dependency pinning. Here's what i get when I attempt to install it :

# composer require webfactory/piwik-bundle
Info from https://repo.packagist.org: #StandWithUkraine
./composer.json has been updated
Running composer update webfactory/piwik-bundle
Loading composer repositories with package information
Restricting packages listed in "symfony/symfony" to "6.3.*"
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires symfony/cache 6.3.*, found symfony/cache[v6.3.0, ..., v6.3.5] but the package is fixed to v6.2.13 (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
    - Root composer.json requires symfony/dotenv 6.3.*, found symfony/dotenv[v6.3.0] but the package is fixed to v6.2.8 (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 3
    - Root composer.json requires symfony/http-client 6.3.*, found symfony/http-client[v6.3.0, v6.3.1, v6.3.2, v6.3.5] but the package is fixed to v6.2.13 (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 4
    - Root composer.json requires symfony/mime 6.3.*, found symfony/mime[v6.3.0, v6.3.2, v6.3.3, v6.3.5] but the package is fixed to v6.2.13 (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 5
    - Root composer.json requires symfony/runtime 6.3.*, found symfony/runtime[v6.3.0, v6.3.1, v6.3.2] but the package is fixed to v6.2.13 (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 6
    - __root__ is present at version 1.0.0+no-version-set and cannot be modified by Composer
    - __root__ 1.0.0+no-version-set conflicts with symfony/symfony 2.0.6.
    - Root composer.json requires symfony/console 6.3.* -> satisfiable by symfony/symfony[2.0.6].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require webfactory/piwik-bundle:*" to figure out if any version is installable, or "composer require webfactory/piwik-bundle:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
sebastiankugler commented 11 months ago

@computamike thanks for pointing this out. Would you be able to open a PR? We'd be happy to merge it.

computamike commented 11 months ago

@computamike thanks for pointing this out. Would you be able to open a PR? We'd be happy to merge it.

Yup - happy to do it. I'll get into it this evening.

computamike commented 11 months ago

PR was created - and rejected. Closin

sebastiankugler commented 11 months ago

@computamike were you able to resolve your problem?

As @relthyg pointed out, the changes suggested were not necessary.

Out of curiosity, I have read the error message in your opening comment. The problem seems to be with the locked versions you have installed in your project, not with the allowed versions in composer.json.

Did you try the suggestion

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

?

Thank you for taking the time to work on the PR!

PS: I would always recommend to link Pull Requests and Issues (this can easily be done by just copying a link or the # followed by the PR/Issue ID in a comment). This gives more context to people who only see the PR.