Description of problem: python3-impacket from epel10 has unresolved dependencies, causing it to be uninstallable. Version-Release number of selected component (if applicable): python3-impacket-0.11.0-6.el10_0 How reproducible: always Steps to Reproduce: 1. dnf install python3-impacket Actual results: Error: Problem: conflicting requests - nothing provides python3-pyOpenSSL needed by python3-impacket-0.11.0-6.el10_0.noarch from epel - nothing provides python3-ldap3 needed by python3-impacket-0.11.0-6.el10_0.noarch from epel - nothing provides python3-pycryptodomex needed by python3-impacket-0.11.0-6.el10_0.noarch from epel - nothing provides python3.12dist(pycryptodomex) needed by python3-impacket-0.11.0-6.el10_0.noarch from epel - nothing provides ((python3.12dist(ldap3) < 2.5 or python3.12dist(ldap3) > 2.5) with (python3.12dist(ldap3) < 2.5.2 or python3.12dist(ldap3) > 2.5.2) with (python3.12dist(ldap3) < 2.6 or python3.12dist(ldap3) > 2.6) with python3.12dist(ldap3) >= 2.5) needed by python3-impacket-0.11.0-6.el10_0.noarch from epel - nothing provides python3.12dist(pyopenssl) >= 21 needed by python3-impacket-0.11.0-6.el10_0.noarch from epel Expected results: successful installation
If you think resolving this will take a long time, and would prefer to remove this uninstallable package from EPEL 10 in the meantime, just say so in this ticket and I can untag the build for you. This won't retire the branch, so as soon as the underlying problem is resolved you can re-publish by creating a new update.
Untagging the branch looks like the right thing to do.
Several of the dependencies have been resolved, but pycryptodomex remains. Error: Problem: conflicting requests - nothing provides python3-pycryptodomex needed by python3-impacket-0.11.0-6.el10_0.noarch from epel - nothing provides python3.12dist(pycryptodomex) needed by python3-impacket-0.11.0-6.el10_0.noarch from epel That has been requested in bug 2313995, but so far there has been no response from the maintainer. Thanks for the confirmation Fabian, I've untagged the build. The branch remains and this can be re-published once pycryptodomex is available.