-
Notifications
You must be signed in to change notification settings - Fork 47
Your requirements could not be resolved to an installable set of packages #18
Comments
@sam452 Yikes! Looks like I need to bump the Guzzle version and see if it still works. I will see what I can do about this. Are you requiring Guzzle 6 for something else? Can you put your |
Yes, happy to share this. This is a greenfield project, so I am unsure if I need Guzzle 6 for something else.
|
@sam452 Thanks a lot. I need to dig into this. I need to update the package to a Guzzle 6 implementation anyways, and honestly need to make it swappable at some point too. That would probably be best with different adapters so you can manage it how you need to. Might take me a little bit because I am going out of town and starting a new job but I will try to get a solution for you. |
No news yet on Bumping Guzzle version to 6? I tried forking this repo and bumping the version but they are not compatible anymore. hehe |
Hey guys, my issue relates to kinda-same problem. Is there info what to do when your custom package uses guzzle version same as another vendor package? Funny thing that they cannot use same version, both of packages. I'm wondering why is this even a problem in composer. |
First-time Laravel 5 user here and it appears that there is a conflict with another library that uses Guzzle?
I guess my Q is could your library use the guzzlehttp version 6.0? Or check the jeroen-g/laravel-packager to see if it can be downgraded to an earlier version? unsure which way to go here.
The text was updated successfully, but these errors were encountered: