597748 – sys-apps/portage-2.3.0 with USE=selinux and PYTHON_TARGETS=pypy creates dependency problem at sys-libs/libselinux-2.5-r1 which does not support PYTHON_TARGETS=pypy

Bug 597748 - sys-apps/portage-2.3.0 with USE=selinux and PYTHON_TARGETS=pypy creates dependency problem at sys-libs/libselinux-2.5-r1 which does not support PYTHON_TARGETS=pypy

Summary: sys-apps/portage-2.3.0 with USE=selinux and PYTHON_TARGETS=pypy creates depen...

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	SELinux (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	SE Linux Bugs

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2016-10-22 06:38 UTC by Dennis Schridde
Modified:	2018-10-12 22:13 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Dennis Schridde 2016-10-22 06:38:27 UTC

sys-apps/portage-2.3.0 cannot be built with USE=selinux and PYTHON_TARGETS=pypy, because that creates a dependency problem related to sys-libs/libselinux-2.5-r1, which does not support PYTHON_TARGETS=pypy.

My wish would be for sys-libs/libselinux to gain support for PYTHON_TARGETS=pypy. Otherwise sys-apps/portage would at least need REQUIRED_USE="selinux? ( !python_targets_pypy )".

Comment 1 Mira Ressel 2018-10-12 22:13:15 UTC

The SELinux profiles mask the python_targets_pypy flag for portage, and all non-SELinux profiles mask the selinux flag, so this isn't an issue (anymore?).