Bug 1754039

Summary:	Review Request: libselinux-python3 - SELinux python 3 bindings for libselinux
Product:	[Fedora] Fedora EPEL	Reporter:	Carl George <carl>
Component:	Package Review	Assignee:	Nobody's working on this, feel free to take it <nobody>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	epel7	CC:	mhroncok, orion, package-review, zpytela
Target Milestone:	---
Target Release:	---
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-09-26 18:54:50 UTC	Type:	---
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-09-20 15:46:25 UTC

Spec URL: https://copr-be.cloud.fedoraproject.org/results/carlwgeorge/reviews/epel-7-x86_64/01037843-libselinux-python3/libselinux-python3.spec
SRPM URL: https://copr-be.cloud.fedoraproject.org/results/carlwgeorge/reviews/epel-7-x86_64/01037843-libselinux-python3/libselinux-python3-2.5-1.el7.src.rpm

Description:
The libselinux-python3 package contains python 3 bindings for developing
SELinux applications.

Fedora Account System Username: carlwgeorge

This is an EPEL7-only package.  Red Hat added python3 to RHEL 7.7, but has declined to turn on the python3 subpackage in the libselinux spec file.  This spec file is essentially that subpackage extracted.  See bug 1719978 for more information.

Comment 1 Miro Hrončok 2019-09-20 17:36:09 UTC

Can this be python3-libselinux to match Fedora? It can provide libselinux-python3.

See https://src.fedoraproject.org/rpms/python3-rpm for a similar package.

Comment 2 Miro Hrončok 2019-09-20 17:54:07 UTC

Also, technically by the "de facto" EPEL guidelines, this package should generate a python36-libselinux subpackage (see the rpm example from previous comment). However there are no "de jure" Python 3 EPEL guidelines.

Comment 3 Carl George 2019-09-20 19:43:34 UTC

I would like to keep it libselinux-python3, so that if RHEL does eventually enable that subpackage, it will be a natural upgrade without messing with obsoletes.

I also think it would be confusing to users to see libselinux-python and python3-libselinux.

Comment 4 Carl George 2019-09-22 19:21:21 UTC

Of course if this is a blocker, I don't mind renaming it to python3-libselinux.  It's just not my first choice.

Comment 5 Miro Hrončok 2019-09-23 08:37:34 UTC

I don't really care. It was only my suggestion. The fact that the 34/36 guidelines don't exists makes this mostly about compromises.

Comment 6 Miro Hrončok 2019-09-26 15:05:54 UTC

This information just came in: https://bugzilla.redhat.com/show_bug.cgi?id=1719978#c26

Comment 7 Carl George 2019-09-26 18:54:50 UTC

Excellent new, thanks for the heads up Miro.  Closing the review since it will not be needed.