Fedora Account System
Red Hat Associate
Red Hat Customer
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.
With pycryptodomex now available, a locally-built python3-impacket is now installable and usable. Could we have it back in EPEL now?
python3-impacket-0.11.0-6.el10_0 has been untagged for too long and has been garbage collected. https://koji.fedoraproject.org/koji/buildinfo?buildID=2549274 A new build will be needed, either from a release or version bump.
FEDORA-EPEL-2026-c1e8091ea1 (python-impacket-0.13.1-3.el10_4) has been submitted as an update to Fedora EPEL 10.4. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-c1e8091ea1
Please can you test the https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-c1e8091ea1 It is rebuild of 0.13.1 for EPEL10. Unfortunately I do not have rhel10 at hand to test on.
The new package is definitely installable now for EPEL-10, which is what this bug was about. I can't verify if it actually works because the thing I wanted it for no longer seems to use it.
FYI on bodhi updates there is an automated tests tab. The fedora-ci.koji-build.installability.functional test is an older check that breaks in certain scenarios, but the fedora-ci.koji-build.rmdepcheck.functional test is a more modern version that is more reliable. Both are passing for that latest update. I also manually verified that the new package installs in a CentOS 10 container, which is currently the appropriate platform for EPEL 10.4. RHEL 10 is currently the appropriate platform for EPEL 10.2.
FEDORA-EPEL-2026-c1e8091ea1 has been pushed to the Fedora EPEL 10.4 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-c1e8091ea1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-c1e8091ea1 (python-impacket-0.13.1-3.el10_4) has been pushed to the Fedora EPEL 10.4 stable repository. If problem still persists, please make note of it in this bug report.