Bug 2313903

Summary:	python3-pwntools: fails to install from epel8/epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Carl George 🎩 <carl>
Component:	python-pwntools	Assignee:	Jonathan Wright <jonathan>
Status:	NEW ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	epel-packagers-sig, jonathan, rebus, redhat
Target Milestone:	---	Flags:	carl: needinfo? (jonathan)
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Carl George 🎩 2024-09-21 01:59:39 UTC

Description of problem:
python3-pwntools from epel8 and epel9 has missing dependencies, causing it to be uninstallable.


Version-Release number of selected component (if applicable):
python3-pwntools-4.9.0-1.el8
python3-pwntools-4.9.0-1.el9


How reproducible:
always


Steps to Reproduce:
1. dnf install python3-pwntools


Actual results:

Error: 
 Problem: conflicting requests
  - nothing provides python3.6dist(six) >= 1.12.0 needed by python3-pwntools-4.9.0-1.el8.noarch from epel
  - nothing provides python3.6dist(unicorn) >= 1.0.2rc1 needed by python3-pwntools-4.9.0-1.el8.noarch from epel

Error: 
 Problem: conflicting requests
  - nothing provides python3.9dist(rpyc) needed by python3-pwntools-4.9.0-1.el9.noarch from epel
  - nothing provides python3.9dist(unicorn) >= 1.0.2~rc1 needed by python3-pwntools-4.9.0-1.el9.noarch from epel


Expected results:
successful installation

Comment 1 Carl George 🎩 2026-01-08 23:12:19 UTC

To avoid having the uninstallable package present in the repos, I have untagged python-pwntools-4.9.0-1.el8 and python-pwntools-4.9.0-1.el9 so they will not be included in future composes.  The epel8 and epel9 branches have not been retired, so as soon as the dependencies are available you can re-publish the package by creating new builds and updates.