RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1711361 - libnftnl-devel package not available to install via dnf install
Summary: libnftnl-devel package not available to install via dnf install
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libnftnl
Version: 8.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.2
Assignee: Phil Sutter
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks: 1763729
TreeView+ depends on / blocked
 
Reported: 2019-05-17 15:18 UTC by Quentin Armitage
Modified: 2023-02-12 23:01 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:06:56 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-28700 0 None None None 2023-02-12 23:01:22 UTC
Red Hat Product Errata RHEA-2020:1763 0 None None None 2020-04-28 16:08:22 UTC

Description Quentin Armitage 2019-05-17 15:18:46 UTC
There does not appear to be an libnftnl-devel package available for installation via dnf. The iptables package is build using libnftnl-devel, and it is therefore not possible to build an rpm for the iptables package, since the BuildRequires on pkgconfig(libnftnl) fails.

Further, when keepalived is upgraded to the next version, it requires the libnftnl-devel package.

Version-Release number of selected component (if applicable):
libnftnl-1.1.1-4.el8

How reproducible:
Always

Steps to Reproduce:
1. dnf install libnftnl-devel
2.
3.

Actual results:
No match for argument: libnftnl-devel

Expected results:
Package is installed

Additional info:
I have enabled the codeready-builder-for-rhel-8 repo, since that was necessary for the libmnl-devel and libnfnetlink-devel packages.

The libnftnl.spec file shows that a devel package is built.

Bug 1708735 reported a similar issue in respect of ipset-devel.

https://bugzilla.redhat.com/show_bug.cgi?id=1660234 reported that nothing provides libnftnl-devel, but the resolution ofthat does not appear to have carried forward into the package being installed by a customer using dnf.

Stefano Brivio <sbrivio> is aware of this issue.

Comment 1 Phil Sutter 2019-07-05 12:56:53 UTC
Moving this to RHEL8.2 since there won't be an update of libnftnl package in RHEL8.1.

Comment 11 errata-xmlrpc 2020-04-28 16:06:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1763


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