Change package guzzle/guzzle for guzzlehttp/guzzle

[arimourao]

Steps to reproduce

1. clone the repo
2. run composer install
3. message alerts at the end that guzzle/guzzle package is abandoned. Suggests to use guzzlehttp/guzzle instead

Expected behaviour

Composer should install everything without warnings

[devenbansod]

I think we don't have a direct dependency on guzzle, but I think it is php-coveralls (on which we have a require-dev dependency).

I believe since their composer.json has already got the change, the next major release of php-coveralls (i.e. 2.0) (and we shifting our dependency to the newer version, which is based on the compatibility of the minimum PHP version that it requires and the one that we require) would remove that warning in future.

[nijel]

This is not really our bug, see php-coveralls/php-coveralls#80 and php-coveralls/php-coveralls#152.

[nijel]

This has been fixed in php-coveralls/php-coveralls@07473e6, but it still is not part of released version.

[ibennetch]

Based on the age of the discussion there (it's from 2015), I don't expect a quick release of the corrected version. I've been thinking about this for some time and they don't seem motivated to fix this problem (which would only require performing a release; the fix has already been committed). Is it worth us creating a fork (at least for now, until they release a proper fix) just to avoid the warning? That might become the optimal solution.

[nijel]

Another way to fix this for us is to stop using coveralls, would anybody mind?

[MauricioFauth]

Is there any alternative to satooshi/php-coveralls?
Is there any benefit in continuing to use Coveralls?

[ibennetch]

Unless I am mistaken, the only benefit from Coveralls is seeing the percentage of our code which is covered by tests. Since it's not nearly 100%, referring to that number is not very meaningful for me so I am fine dropping that aspect.

[nijel]

We have codecov as well, so I don't think we will miss it much...