New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev-python/elasticsearch-curator: Add missing dependencies #19538
Conversation
Add missing importlib_metadata and cx_Freeze dependencies Closes: https://bugs.gentoo.org/761325 Signed-off-by: Peter Vielberth <code@peter-vielberth.de> Package-Manager: Portage-3.0.14, Repoman-3.0.2
Pull Request assignmentSubmitter: @vibpe dev-python/elasticsearch-curator: @gentoo/proxy-maint (maintainer needed) Linked bugsBugs linked: 761325 In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Pull request CI reportReport generated at: 2021-02-19 09:45 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
|
||
EAPI=7 | ||
|
||
PYTHON_COMPAT=( python3_7 ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it not support python3_8 and python3_9?
https://archives.gentoo.org/gentoo-dev/message/ba2fc4854ed6bb49813819ae6f5e9552
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It probably also compiles with python3_8 and python3_9. I just copied the existing -r2 ebuild and added the missing dependencies.
Now I tried to change this line in a local overlay to PYTHON_COMPAT=( python3_{7..9} )
But then emerge demands a use flag change:
# required by dev-python/elasticsearch-curator (argument)
>=dev-python/elasticsearch-curator-5.8.1-r3 -python_targets_python3_8
I don't know why. All dependencies listed in the ebuild support at least python3_8.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like curator still has some problems with python3_8 (failing tests)
elastic/curator#1512
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like curator still has some problems with python3_8 (failing tests)
elastic/curator#1512
Please see elastic/curator#1587 (comment)
You also want to bump to most recent version which is presently 5.8.3 instead of sticking to 5.8.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It probably also compiles with python3_8 and python3_9. I just copied the existing -r2 ebuild and added the missing dependencies.
Now I tried to change this line in a local overlay to
PYTHON_COMPAT=( python3_{7..9} )
But then emerge demands a use flag change:
# required by dev-python/elasticsearch-curator (argument)
>=dev-python/elasticsearch-curator-5.8.1-r3 -python_targets_python3_8
I don't know why. All dependencies listed in the ebuild support at least python3_8.
You want use elasticsearch-curator-5.8.3 and add python3_9 to importlib_metadata-3.4.0 and elasticsearch-py-7.7.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also had to add python3_9 to dev-python/click
I added a 5.8.3 ebuild for elasticsearch-curator, it compiled using python targets 3_7, 3_8 and 3_9. Tested it against my elasticsearch instance. Looks fine to me.
However when I run repoman ci
on the importlib_metadata-3.4.0 change (adding python3_9), I get an error:
dependency.bad [fatal] 80
dev-python/importlib_metadata/importlib_metadata-3.4.0.ebuild: BDEPEND: ~alpha(default/linux/alpha/17.0)
[ '>=dev-python/importlib_resources-1.3.0[python_targets_pypy3(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]']
dev-python/importlib_metadata/importlib_metadata-3.4.0.ebuild: BDEPEND: ~alpha(default/linux/alpha/17.0/desktop)
[ '>=dev-python/importlib_resources-1.3.0[python_targets_pypy3(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)
...
I thought of adding python3_9 to importlib_resources, too. But this comment in the ebuild kept me from doing so:
This is a backport of Python 3.9's importlib.
I'm not a Python developer and don't want to mess with dependencies and version conflicts which I don't understand
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyway, I added the python3_9 dependency to importlib_resources and importlib_metadata to get past the CI analysis.
Please have a look at this change if its sensible.
>=dev-python/certifi-2019.9.11[${PYTHON_USEDEP}] | ||
>=dev-python/requests-2.20.0[${PYTHON_USEDEP}] | ||
>=dev-python/urllib3-1.24.2[${PYTHON_USEDEP}] | ||
<dev-python/urllib3-1.26[${PYTHON_USEDEP}] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Try without downgrading urllib3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would like to use a current urllib3 version. But this is a requirement of elasticsearch curator. Please see this commit: elastic/curator@99bb6d4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As compilation with dev-python/urllib3-1.26.2-r3 works here, can you find out what's upsteam's intention with pinning that dependency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Compiling with dev-python/urllib3-1.26.2-r3 works here, too. Also got no errors while testing.
Asked upstream: elastic/curator#1589
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you also comment this on https://bugs.gentoo.org/714860 please?
Pull request CI reportReport generated at: 2021-02-20 17:40 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
e6e8fa2
to
bf16da8
Compare
Pull request CI reportReport generated at: 2021-02-20 18:20 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
dev-python/click/click-6.7-r2.ebuild
Outdated
@@ -1,9 +1,9 @@ | |||
# Copyright 1999-2020 Gentoo Authors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
6.7-r2 is already partly stable and should not be changed without revbump
And there is also 7.1.2-r2 ...
@@ -1,9 +1,9 @@ | |||
# Copyright 1999-2020 Gentoo Authors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't change PYTHON_COMPAT on stable versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it's okay to do that -- please do add new PYTHON_COMPAT wherever it works (and tests pass - FEATURES=test emerge ...)
Pull request CI reportReport generated at: 2021-02-22 00:10 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
elasticsearch-curator updated to 5.8.3 Signed-off-by: Peter Vielberth <code@peter-vielberth.de> Package-Manager: Portage-3.0.14, Repoman-3.0.2
Package-Manager: Portage-3.0.14, Repoman-3.0.2 Signed-off-by: Peter Vielberth <code@peter-vielberth.de>
Package-Manager: Portage-3.0.14, Repoman-3.0.2 Signed-off-by: Peter Vielberth <code@peter-vielberth.de>
Package-Manager: Portage-3.0.14, Repoman-3.0.2 Signed-off-by: Peter Vielberth <code@peter-vielberth.de>
Package-Manager: Portage-3.0.14, Repoman-3.0.2 Signed-off-by: Peter Vielberth <code@peter-vielberth.de>
5d7eefb
to
69cd79d
Compare
Pull request CI reportReport generated at: 2021-02-22 12:45 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Merged, thank you! (Dropped the 3.9 commits for importlib*) |
Add missing importlib_metadata and cx_Freeze dependencies
Closes: https://bugs.gentoo.org/761325
Signed-off-by: Peter Vielberth code@peter-vielberth.de
Package-Manager: Portage-3.0.14, Repoman-3.0.2