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

Using Graby with Laravel #331

Open
kolaente opened this issue Jun 23, 2023 · 1 comment · May be fixed by #332
Open

Using Graby with Laravel #331

kolaente opened this issue Jun 23, 2023 · 1 comment · May be fixed by #332

Comments

@kolaente
Copy link

kolaente commented Jun 23, 2023

Trying to install Graby in a Laravel application fails because of different monolog requirements:

$ composer require 'j0k3r/graby dev-master' php-http/guzzle7-adapter
./composer.json has been updated
Running composer update j0k3r/graby php-http/guzzle7-adapter
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 j0k3r/graby dev-master -> satisfiable by j0k3r/graby[dev-master].
    - j0k3r/graby dev-master requires monolog/monolog ^1.18.0|^2.3 -> found monolog/monolog[1.18.0, ..., 1.27.1, 2.3.0, ..., 2.9.1] but the package is fixed to 3.4.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 php-http/guzzle7-adapter:*" to figure out if any version is installable, or "composer require php-http/guzzle7-adapter:^2.1" if you know which you need.

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

(Trying the 2.x release fails because the guzzle versions are not compatible)

Laravel appears to require at least monolog 3:

$ composer why monolog/monolog
laravel/framework v10.13.5 requires monolog/monolog (^3.0)

Any way to solve this? Or do I need to wait for 3.0?

If there's interest, I could put up a PR with a migration for monolog 3.

@kolaente kolaente linked a pull request Jun 23, 2023 that will close this issue
@kolaente
Copy link
Author

Opened a PR: #332

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.

1 participant