Description of problem: python3-kubernetes-tests from epel9 and epel10 have missing dependencies, causing them to be uninstallable. Version-Release number of selected component (if applicable): python3-kubernetes-tests-1:26.1.0-2.el9 python3-kubernetes-tests-1:30.1.0-1.el10_0 How reproducible: always Steps to Reproduce: 1. dnf install python3-kubernetes-tests Actual results: Error: Problem: conflicting requests - nothing provides python3-mock needed by python3-kubernetes-tests-1:26.1.0-2.el9.noarch from epel - nothing provides python3-nose needed by python3-kubernetes-tests-1:26.1.0-2.el9.noarch from epel Error: Problem: conflicting requests - nothing provides python3-mock needed by python3-kubernetes-tests-1:30.1.0-1.el10_0.noarch from epel - nothing provides python3-nose needed by python3-kubernetes-tests-1:30.1.0-1.el10_0.noarch from epel - nothing provides python3-py needed by python3-kubernetes-tests-1:30.1.0-1.el10_0.noarch from epel Expected results: successful installation
Do you need the tests sub-package or would it be reasonable to stop creating it for epel given the missing dependencies?
I actually don't need any of the subpackages myself, I was just reporting the fail to install (FTI) problem that I noticed in repoclosure. In general it is valid to conditionally disable subpackages on EPEL when not all the dependencies are available. That said, it seems like it would be straightforward to just sort out these dependencies. mock: This was formerly a third-party PyPI package, but has been in the standard library since Python 3.3. It looks like this software switched from the third-party mock to the standard library mock in version 25, but just forgot to remove it from test-requirements.txt, which is being used as the source for tests_require in setup.py. Patching it out (and sending the patch upstream) would remove this dependency. https://github.com/kubernetes-client/python/commit/f1dfdbba456f1aa53c06e9d063d54c9416f58010 nose: I don't see this imported in the code anywhere. Upstream does seem to be using it as their test runner in kubernetes/.gitlab-ci.yml, but you're not running the tests in %check so you can also patch this one out to avoid the dependency. py: This one is in RHEL 9, so taking care of the first two will fix the EPEL 9 package. It was dropped in RHEL 10, so you'll need to request it for EPEL 10 from the Fedora maintainers. https://docs.fedoraproject.org/en-US/epel/epel-package-request/
FEDORA-EPEL-2024-83b7f13de4 (python-kubernetes-26.1.0-3.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-83b7f13de4
FEDORA-EPEL-2024-83b7f13de4 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-83b7f13de4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-83b7f13de4 (python-kubernetes-26.1.0-3.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
With the addition of python3-py in bug 2314125, and the dependency adjustments in the latest python-kubernetes builds, this is now resolved in both epel9 and epel10.