Summary: | systemd: (with sys-apps/merge-usr) Failed to set new SELinux execution context | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | bdouxx <bdouxx-gentoo> |
Component: | SELinux | Assignee: | SE Linux Bugs <selinux> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
bdouxx
2022-12-10 11:57:05 UTC
I think there's 2 separate issues here: the SELinux context setting with Portage and the internal file collision. As for the latter, it doesn't look like you set the system profile to a merged-usr one (the split-usr USE flag is still enabled) after running the merge-usr script. So what's happening is the systemd ebuild is installing both a split-usr compatibility symlink and the real binary on the system to the same path. Please switch to a systemd/selinux/merged-usr profile and try rebuilding. thank you with this profile it's good |