Skip to content
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.

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

Update composer.json to not error on 8+ #5

Closed
iNilo opened this issue Mar 9, 2022 · 3 comments · Fixed by #6
Closed

Update composer.json to not error on 8+ #5

iNilo opened this issue Mar 9, 2022 · 3 comments · Fixed by #6

Comments

@iNilo
Copy link

iNilo commented Mar 9, 2022

composer require bref/logger
Using version ^1.0 for bref/logger
./composer.json has been updated
Running composer update bref/logger
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - bref/logger 1.0.0 requires php ^7.2 -> your php version (8.1.2) does not satisfy that requirement.
    - bref/logger 1.0.1 requires psr/log ^1.1 -> found psr/log[1.1.0, ..., 1.1.4] but the package is fixed to 3.0.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.
    - Root composer.json requires bref/logger ^1.0 -> satisfiable by bref/logger[1.0.0, 1.0.1].

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

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
@mnapoli
Copy link
Member

mnapoli commented Mar 9, 2022

Oh I think it's needed to update the psr/log dependency: https://github.com/brefphp/logger/blob/master/composer.json#L20

PRs welcome!

@iNilo
Copy link
Author

iNilo commented Mar 9, 2022

@mnapoli I've never PR'd stuff like this, otherwise I would have done that ❤ I was more comfy making an issue 🙃

@deleugpn
Copy link
Member

deleugpn commented Mar 9, 2022

hey @iNilo let me know if 1.0.3 solved it for you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants