On 03/03/2017 10:43 PM, Paul W. Frields wrote:
On Fri, Mar 03, 2017 at 11:57:12AM -0500, Stephen Gallagher wrote:
On 03/03/2017 11:40 AM, Michael Catanzaro wrote:
Hi,
Unfortunately the change deadline has passed, but our coredumpctl
change is not testable due to [1]. Additionally, ABRT is broken due to
[2]. We have workarounds for both issues, but it requires running
SELinux commands locally. Accordingly, is likely that FESCo will reject
the change at its next meeting.
I'm tired of prodding the SELinux developers via email and Bugzilla.
This saga has been ongoing since last summer, which is way too long. I
now have very, very serious doubts as to whether we should continue to
ship with SELinux enabled in the Workstation product. We clearly cannot
fix it even when it's breaking a critical developer feature that's a
priority for the WG... so what happens when it breaks anything less
important?
Michael
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1341829
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1419980
Please propose [1] as a blocker bug for the release and open a ticket on the
FESCo tracker to request that FESCo use its prerogative to declare this a
blocker for the release.
[1] is in MODIFIED and selinux-policy-3.13.1-235.fc26 was supposed to
have the fix. Michael, are you saying the fix isn't working? Because
I see no comment in the bug to that effect.
Putting that on the blocker list may be useful, but what would be more
useful is testing the bug and reporting the results back.
I add comment to BZ, it's fixed in the latest selinux-policy package for
F26.
Lukas.
--
Lukas Vrabec
SELinux Solutions
Red Hat, Inc.
_______________________________________________
desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
