Skip to content

Can not install because of version conflict with composer/installers #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
hirasso opened this issue Mar 7, 2025 · 2 comments · May be fixed by #16
Open

Can not install because of version conflict with composer/installers #15

hirasso opened this issue Mar 7, 2025 · 2 comments · May be fixed by #16
Labels
enhancement

Comments

@hirasso
Copy link

hirasso commented Mar 7, 2025 •
edited
Loading

Hi there! Once again it seems like I'm late to the party ;)

...tried to install wps in a current roots/bedrock project I'm working on. The install fails with these errors:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires rarst/wps * -> satisfiable by rarst/wps[dev-master, 1.0, 1.1, 1.2, 9999999-dev].
    - rarst/wps[1.0, ..., 1.1] require composer/installers ~1.0 -> found composer/installers[v1.0.0, ..., 1.x-dev] but the package is fixed to v2.3.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.
    - rarst/wps[dev-master, 1.2] require composer/installers ~1.6 -> found composer/installers[v1.6.0, ..., 1.x-dev] but the package is fixed to v2.3.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.

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 rarst/wps:*" to figure out if any version is installable, or "composer require rarst/wps:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

I'm unsure if and how I can solve this conflict on my end. Would there speak anything against allowing composer/installers v2 in wps?
@Rarst
Copy link
Owner

Rarst commented Mar 7, 2025 •
edited
Loading

It should probably get bumped, but that will bump a PHP version required and it has been years since I touched this so who knows what will happen. :) I will try to take a look and refresh, but unfortunately I am not doing development at the moment so will see how that goes, can't really give it much attention right now. :(

@hirasso
Copy link
Author

hirasso commented Mar 7, 2025 •
edited
Loading

I see... hope to see you active again sometime soon 🌈

For what it's worth: I just installed wps manually in my php 8.2 project and at first glance it seemed to be working fine. I didn't test the AJAX and REST handlers, though.

@philipdowner philipdowner linked a pull request Mar 21, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix Composer version issues philipdowner/wpWhoops
2 participants
@Rarst @hirasso