Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1962607 - Fails to install python3-impacket on EPEL8
Summary: Fails to install python3-impacket on EPEL8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-impacket
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Ambroz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1962480
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-20 11:10 UTC by Michal Ambroz
Modified: 2021-06-07 00:31 UTC (History)
2 users (show)

Fixed In Version: python-impacket-0.9.22-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-07 00:31:31 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Michal Ambroz 2021-05-20 11:10:47 UTC 
Description of problem:
package python3-impacket fails to install on EPEL8 due to missing dependency to python3-crypto
Comment 1 Fedora Update System 2021-05-22 20:09:58 UTC 
FEDORA-EPEL-2021-897f7567fe has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-897f7567fe
Comment 2 Fedora Update System 2021-05-23 01:57:37 UTC 
FEDORA-EPEL-2021-897f7567fe has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-897f7567fe

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2021-06-07 00:31:31 UTC 
FEDORA-EPEL-2021-897f7567fe has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.