Bug 2345168 - Please build compatible with iptables-libs-1.8.10-11.el9_5.aarch64
Summary: Please build compatible with iptables-libs-1.8.10-11.el9_5.aarch64
Keywords:
Status: CLOSED DUPLICATE of bug 2343682
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: iptables-epel
Version: epel9
Hardware: aarch64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Michel Lind
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-12 08:55 UTC by JG
Modified: 2025-02-12 21:09 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-12 21:09:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description JG 2025-02-12 08:55:38 UTC
Description of problem:

VM NAME="Rocky Linux"
VERSION="9.5 (Blue Onyx)"

Update is blocked as iptables-legacy package requires iptables-libs (specifically version 1.8.10-4.el9), and the update wants to install a newer ( and incompatible version ).

Version-Release number of selected component (if applicable):

Present version on the system: iptables-legacy-1.8.10-4.1.el9.aarch64
Present version on the system: iptables-libs-1.8.10-4.el9_4.aarch64
Proposed update is iptables-libs-1.8.10-11.el9_5.aarch64 ( released on 2025-02-04 )


How reproducible:

iptables-libs-1.8.10-4.el9_4.aarch64 installed with iptables-legacy-1.8.10-4.1.el9.aarch64. 


Steps to Reproduce:
[XXX ~]# yum update
Last metadata expiration check: 0:49:12 ago on Wed Feb 12 07:37:30 2025.
Error:
 Problem: cannot install both iptables-libs-1.8.10-11.el9_5.aarch64 from baseos and iptables-libs-1.8.10-4.el9_4.aarch64 from @System
  - package iptables-legacy-1.8.10-4.1.el9.aarch64 from @System requires (iptables-libs(aarch-64) = 1.8.10-4.el9 or iptables-libs(aarch-64) = 1.8.10-4.el9_4), but none of the providers can be installed
  - cannot install the best update candidate for package iptables-libs-1.8.10-4.el9_4.aarch64
  - cannot install the best update candidate for package iptables-legacy-1.8.10-4.1.el9.aarch64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Actual results:


Expected results:


Additional info:

Comment 1 Carl George 🎩 2025-02-12 21:09:29 UTC

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


Note You need to log in before you can comment on or make changes to this bug.