Tested build and work with python-request-1.12.5.
Created attachment 464766 [details, diff] Patch for docker-compose.
Created attachment 464768 [details] Ebuild Requested patch attached.
(In reply to gavk from comment #1) > Created attachment 464766 [details, diff] [details, diff] > Patch for docker-compose. Maybe we can just remove the maximum version restriction entirely. I suspect that upstream is restricting it only for the sake of restricting it.
Comment on attachment 464768 [details] Ebuild For ebuild changes, please attach a unified diff created as follows: > diff -u docker-compose-1.14.0.ebuild.orig docker-compose-1.14.0.ebuild > docker-compose-1.14.0.ebuild.diff
Looks like upstream is restricting it on purpose. See https://github.com/docker/compose/issues/4431
The reason given in https://github.com/docker/compose/issues/4431#issuecomment-277846958 is: > We make a fairly unconventional use of requests (HTTP over UNIX sockets) > which makes us particularly sensitive to updates of the requests package - > even when they're just bugfixes. My feeling is that we should specify the dependency more optimistically, and then react to reports of breakage if and when they arise.
In https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/docker-compose we can see that for docker-compose-1.15.0, Arch uses sed to make it a >= dependency as follows: > # Remove upper bound on requires > sed -i 's/==/>=/g' requirements.txt > sed -i "s/, < .*',$/',/" setup.py
This should be fixed in docker-compose-1.17.1 and later.
