Bug 1719771

Summary:	python3-libselinux: missing Python metadata
Product:	Red Hat Enterprise Linux 8	Reporter:	Carl George <carl>
Component:	libselinux	Assignee:	Petr Lautrbach <plautrba>
Status:	CLOSED ERRATA	QA Contact:	Milos Malik <mmalik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	ajacocks, dwalsh, lvrabec, mmalik, plautrba, prjagtap, ssbarnea, ssekidde, vmojzis
Target Milestone:	rc
Target Release:	8.1
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:06:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Carl George 2019-06-12 14:11:13 UTC

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.

Comment 18 errata-xmlrpc 2019-11-05 22:06:29 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/RHBA-2019:3533