Ratchet: Guzzle out of date?

Created on 4 Mar 2015  ·  20Comments  ·  Source: ratchetphp/Ratchet

Writing a new app with Ratchet & Composer is complaining that the Guzzle reference is out of date / abandoned.

Any chance you can use "guzzlehttp/guzzle": "5.0.*@dev" instead?

Most helpful comment

The 0.4 branch is ready for testing to be merged into master. Feel free to test it out and open any issues that come as a result. Documentation will then have to be updated to tag it.

Deprecated messages don't mean anything; it means the package is no longer maintained, not that it doesn't work. Ratchet's use of Guzzle is take an HTTP string, parse, and return an object.

All 20 comments

See #285, it will be updated in the near future.

It would be quite usefull, until then my IDE suggest me both libraries when I write a code, but of couse, I wanna just guzzlehttp.

I started replacing it with Guzzle 5 yesterday. Unfortunately quite a bit has changed so it's not just a quick upgrade.

In the mean time, composer is just issuing a warning. Guzzle 3 is stable and still works.

@cboden thanks for a feedback, of course, it's not so big deal :-)

+1 for "guzzlehttp/guzzle", current version is 6.0.1. which has PSR7 support. Might make sense- if you consider upgrading- to go for PSR7?

Ratchet v0.4 will be PSR-7. See the 0.4-wip/* branches.

Question : Is it safe to add "guzzle/guzzle" to composer.json as Composer recommends to use it instead ?
Because I tried to add this line and when updating, it deleted all guzzle/ to install guzzle/guzzle.

My app seems to keep running but I do not know if it will be less stable or not. What is the recommend things to do for now ? To keep "guzzle/guzzle" or to delete this line and let composer reinstall "guzzle/" ?

Thanks !

@RynnHeldeD guzzle/http, guzzle/parser, and the other guzzle/ packages are git subtree splits from guzzle/guzzle. The author of Guzzle just stopped splitting the sub repositories from the main repo. You're safe doing what you're doing. The only reason Ratchet doesn't do this is because guzzle/guzzle requires ext/curl which is not needed by Ratchet and would introduce a BC break.

👍

Any news on this? Thanks!

News on this?

Still, for production delivery having deprecated messages on composer update is not really nice, do you have any ETA when this could be resolved?

The 0.4 branch is ready for testing to be merged into master. Feel free to test it out and open any issues that come as a result. Documentation will then have to be updated to tag it.

Deprecated messages don't mean anything; it means the package is no longer maintained, not that it doesn't work. Ratchet's use of Guzzle is take an HTTP string, parse, and return an object.

+1 Trying to clean up our code now that PHP 7.1 and Symfony 3.2 is out. I know it's just a warning, but it's the last one in our list of dependencies.

August 29 2017... Any news?

what should i do?

screenshot from 2017-10-05 04 00 05

Using version ^6.3 for guzzlehttp/guzzle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for guzzlehttp/guzzle ^6.3 -> satisfiable by guzzlehttp/guzzle[6.3.0].
- Conclusion: remove guzzlehttp/psr7 1.3.1
- Conclusion: don't install guzzlehttp/psr7 1.3.1
- guzzlehttp/guzzle 6.3.0 requires guzzlehttp/psr7 ^1.4 -> satisfiable by guzzlehttp/psr7[1.4.0, 1.4.1, 1.4.2].
- Can only install one of: guzzlehttp/psr7[1.4.0, 1.3.1].
- Can only install one of: guzzlehttp/psr7[1.4.1, 1.3.1].
- Can only install one of: guzzlehttp/psr7[1.4.2, 1.3.1].
- Installation request for guzzlehttp/psr7 (locked at 1.3.1) -> satisfiable by guzzlehttp/psr7[1.3.1].

Installation failed, reverting ./composer.json to its original content.
screenshot from 2017-10-05 04 00 05

@saydulk Try doing a composer upgrade guzzlehttp/psr7 before you add guzzlehttp/guzzle.

... or upgrade both at the same time, see https://stackoverflow.com/questions/46510542/howto-upgrade-selected-package-when-composer-lock-is-present?noredirect=1#comment79983904_46510542

Am 05.10.2017 um 00:42 schrieb Chris Boden notifications@github.com:

@saydulk Try doing a composer upgrade guzzlehttp/psr7 before you add guzzlehttp/guzzle.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@saydulk What's the output of composer show?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lubatti picture lubatti  ·  6Comments

Hemant3105 picture Hemant3105  ·  6Comments

nazar-pc picture nazar-pc  ·  8Comments

Erseni picture Erseni  ·  5Comments

Lugia101101 picture Lugia101101  ·  7Comments