Summary: | =sys-libs/selinux-2.1.12 needs fedora patches to be compatible with >=sys-fs/udev-197 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
Component: | Current packages | Assignee: | Sven Vermeulen (RETIRED) <swift> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | selinux |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | http://bugzilla.redhat.com/show_bug.cgi?id=909826 | ||
Whiteboard: | selinux-utils | ||
Package list: | Runtime testing required: | --- |
Description
Samuli Suominen (RETIRED)
2013-03-21 21:33:12 UTC
Meh, the patch doesn't apply on our (mainly upstream) libselinux. I'll add in the part you mentioned. sys-libs/libselinux-2.1.12-r3 currently in hardened-development overlay with mentioned patch. I'll run a few tests before moving to main tree (still have to test the new udev referenced in bug #462538 as well) Thanks Sven. You can try udev-199 or udev-9999 directly. Don't waste your time with 197 or 198. Booted up successfully with udev-9999; once udev was started the contexts seem to be ok for most devices. A few are left, but I think those are from lvm utilities, not udev (/dev/mapper/*). I've created bug #463690 for this as it is most likely a policy-only issue. sys-libs/libselinux-2.1.12-r3 is in tree, ~arch'ed for now (In reply to comment #4) > Booted up successfully with udev-9999 nice, then udev-200 is OK too, bug 463614 :-) Stabilized |