dnf install iptables-legacy
Last metadata expiration check: 3:43:21 ago on Tue Sep 10 10:39:03 2024.
Error:
Problem: conflicting requests
- nothing provides (iptables-libs(x86-64) = 1.8.10-2.el9 or iptables-libs(x86-64) = 1.8.10-2.el9_1) needed by iptables-legacy-1.8.10-2.2.el9.x86_64 from epel
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
I need iptables-libs(x86-64) = 1.8.10-2.el9 or iptables-libs(x86-64) = 1.8.10-2.el9_1
But rocky won’t provide this version, only a newer one
dnf info iptables-libs
Last metadata expiration check: 3:53:52 ago on Tue Sep 10 10:39:03 2024.
Installed Packages
Name : iptables-libs
Version : 1.8.10
Release : 4.el9_4
Architecture : x86_64
Size : 1.7 M
Source : iptables-1.8.10-4.el9_4.src.rpm
Repository : @System
From repo : baseos
Summary : libxtables and iptables extensions userspace support
URL : https://www.netfilter.org/projects/iptables
License : GPLv2 and Artistic 2.0 and ISC
Description : libxtables and associated shared object files
:
: Libxtables provides unified access to iptables extensions in userspace. Data
: and logic for those is kept in per-extension shared object files.
We use and combine close to forty ansible roles related to iptables on our servers and laptops, not only on Rocky Linux but also on Debian and Ubuntu.
With our Ansible roles, we can do some very fine iptables tuning, in order to meet a wide range of needs
In order to standardise our rules for all systems, we are keeping iptables for now. Change to nftable is planed for Debian 13, but it’s a lot of work and tests for our small team
I think the vault will be ok for a temporary fix of this bug
I have the same problem and I would gladly simply remove iptables-legacy. However it turned out, iptables-legacy is required by podman-docker. podman-docker however is NOT an epel package but from appstream, so maybe docker-podman has to be rebuild as well?