Bug 2344204

Summary:	iptables-legacy needs updated build against latest iptables-libs in epel 9
Product:	[Fedora] Fedora EPEL	Reporter:	jason.corley <jason.corley>
Component:	iptables-epel	Assignee:	Michel Lind <michel>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	davide, jean-louis.mas, michel, trevor
Target Milestone:	---
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:	2025-02-11 14:49:44 UTC	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 jason.corley 2025-02-06 15:25:01 UTC

Description of problem:
installation of iptables-legacy requires iptables-libs-1.8.10-4.el9 and iptables-libs itself has been updated to 1.8.10-11.el9_5. I checked the version in iptables-next https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2024-42901ed523 and this version is also not new enough to resolve the problem. this is essentially the same as https://bugzilla.redhat.com/show_bug.cgi?id=2310158

Version-Release number of selected component (if applicable):
iptables-legacy-1.8.10-4.1.el9.x86_64 from epel
iptables-legacy-1.8.10-6.1.el9.next from epel next

How reproducible:
Have iptables-libs installed and updated to latest and try to install iptables-legacy from epel

Comment 1 Trevor Hemsley 2025-02-09 15:15:04 UTC

Duplicate of 2343682

Comment 2 jason.corley 2025-02-11 14:49:44 UTC


*** This bug has been marked as a duplicate of bug 2343682 ***