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.

Description of problem:
Installing the libselinux Python bindings via the python3-libselinux package is not recognized by Python packaging tools.

Version-Release number of selected component (if applicable):
python3-libselinux-2.8-6.el8

Steps to Reproduce:
1. dnf install python3-libselinux
2. pip3 list | grep -i selinux

Actual results:
no output

Expected results:
selinux         2.8

Additional info:
I have a CLI tool that imports selinux in order to run a restorecon.  That works, but the tool is installed with a setuptools entry point, which uses pkg_resources to verify all the requirements are installed.  The missing metadata causes pkg_resources to abort the CLI execution.  The only way to work around it is to not list selinux in my setup.py requirements.

This has recently been fixed in Fedora Rawhide (bug 1709576), so I was hoping that fix could be backported to RHEL 8.

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/RHBA-2019:3533