Bug 587712

Summary:	sys-libs/libselinux does not properly set up selinux python module with current swig (3.0.10)
Product:	Gentoo Linux	Reporter:	anoteros <anoteros>
Component:	Current packages	Assignee:	Jason Zaman <perfinion>
Status:	RESOLVED FIXED
Severity:	normal	CC:	selinux
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	https://bugzilla.redhat.com/show_bug.cgi?id=1349954
Whiteboard:
Package list:		Runtime testing required:	---

Description anoteros 2016-07-01 14:42:21 UTC

While sys-libs/libselinux properly creates a selinux directory with module files in /usr/lib64/python2.7/site-packages/, all python tools that depend on this module are broken, and spit out the error "no module named _selinux".

As seen on https://bugzilla.redhat.com/show_bug.cgi?id=1349954, this is probably an incompatibility with new versions of swig. The workaround on one of those posts, (coping _selinux.so to /usr/lib64/python2.7/site-packages, in other words bringing it out of the selinux directory) works around the issue.

Comment 1 Robert Förster 2016-07-05 13:28:59 UTC

upstream does exactly that now
https://github.com/SELinuxProject/selinux/commit/a9604c30a5e2f71007d31aa6ba41cf7b95d94822

Comment 2 Vladimir Datsevich 2016-09-14 12:42:47 UTC

Are there any news on this?

Comment 3 Jason Zaman gentoo-dev

2016-09-15 10:45:30 UTC

I just pushed libselinux-2.5-r1 to the tree with this patch backported.