During a fresh AlmaLinux 10.2 minimal installation, iptables-nft-1.8.11-15.el10_2 unexpectedly pulls in the complete kernel-debug package set.
The issue is 100% reproducible and also occurs on Rocky Linux 10.2 and official RHEL 10.2, so it appears to be an upstream packaging or dependency-resolution issue.
Related RHEL issues: RHEL-176386 and RHEL-186232.
Full report and logs:
Could an AlmaLinux maintainer please help triage and route this issue upstream?
Note: update from iptables-nft-1.8.11-13.el10_1 to iptables-nft-1.8.11-15.el10_2 does not pull in any kernel-debug\* packages.
Pay attention, what I’m saying is not an update, but a source installation, that is, directly using the latest version. The solver will introduce a debug kernel. This issue has been adopted and reproduced by the RHEL official and is being prepared for a fix.
Yes. That is the interesting part – that the solver picks different set on fresh install.
dnf repoquery --requires iptables-nft lists things for el10 that it does not for el9 (and of type I don’t recall seeing before):
(kernel-64k-debug-modules-extra if kernel-64k-debug-modules-core)
(kernel-64k-modules-extra if kernel-64k-modules-core)
(kernel-debug-modules-extra if kernel-debug-modules-core)
(kernel-modules-extra if kernel-modules-core)
(kernel-rt-64k-debug-modules-extra if kernel-rt-64k-debug-modules-core)
(kernel-rt-64k-modules-extra if kernel-rt-64k-modules-core)
(kernel-rt-debug-modules-extra if kernel-rt-debug-modules-core)
(kernel-rt-modules-extra if kernel-rt-modules-core)
