commit:     2950f52fbd4d3e6657af8e33d059484e91c51fc0
Author:     WGH <wgh <AT> torlan <DOT> ru>
AuthorDate: Mon Feb 24 18:45:54 2020 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Tue Feb 25 14:50:34 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2950f52f

dev-python/python-language-server: fix dep versions

Copy dependency version bounds from the upstream setup.py:
https://github.com/palantir/python-language-server/blob/0.31.8/setup.py#L38

This fixes the problem when e.g. older jedi satisfies the ebuild
dependency, but the package itself checks dependency specified it
in its setup.py at runtime, refusing to work on mismatch (see #710684).
If pyls silently accepted wrong package version it could've been worse,
though.

Closes: https://bugs.gentoo.org/710684
Signed-off-by: Maxim Plotnikov <wgh <AT> torlan.ru>
Closes: https://github.com/gentoo/gentoo/pull/14761
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 .../python-language-server/python-language-server-0.31.8.ebuild   | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git 
a/dev-python/python-language-server/python-language-server-0.31.8.ebuild 
b/dev-python/python-language-server/python-language-server-0.31.8.ebuild
index 0ebc9ebc1a9..53b3086f0cd 100644
--- a/dev-python/python-language-server/python-language-server-0.31.8.ebuild
+++ b/dev-python/python-language-server/python-language-server-0.31.8.ebuild
@@ -19,10 +19,12 @@ KEYWORDS="~amd64 ~x86"
 
 BDEPEND="dev-python/versioneer[${PYTHON_USEDEP}]"
 
-RDEPEND="dev-python/jedi[${PYTHON_USEDEP}]
+RDEPEND="
+       >=dev-python/jedi-0.14.1[${PYTHON_USEDEP}]
+       <dev-python/jedi-0.16.0[${PYTHON_USEDEP}]
        dev-python/pluggy[${PYTHON_USEDEP}]
-       dev-python/python-jsonrpc-server[${PYTHON_USEDEP}]
-       dev-python/ujson[${PYTHON_USEDEP}]"
+       >=dev-python/python-jsonrpc-server-0.3.2[${PYTHON_USEDEP}]
+       <=dev-python/ujson-1.35[${PYTHON_USEDEP}]"
 
 DEPEND="test? (
        dev-python/autopep8[${PYTHON_USEDEP}]

Reply via email to