https://bugzilla.redhat.com/show_bug.cgi?id=1369954
I'm not sure what's caused this, I'm still trying to track it down.
But enforcing=0 does work around it. It might be a recent
selinux-policy of systemd update that's broken it.
--
Chris Murphy
--
devel mailing list
devel@lists.fedoraproject.org
It's already been dealt with, see RHBZ #1368745.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
On Wed, Aug 24, 2016 at 3:31 PM, Alexander Ploumistos
wrote:
> It's already been dealt with, see RHBZ #1368745.
Thanks. Kinda surprising -12 made it to stable...
--
Chris Murphy
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedorapro
On Wed, Aug 24, 2016 at 3:35 PM, Chris Murphy wrote:
> On Wed, Aug 24, 2016 at 3:31 PM, Alexander Ploumistos
> wrote:
>> It's already been dealt with, see RHBZ #1368745.
>
> Thanks. Kinda surprising -12 made it to stable...
So even after 'dnf clean all' the -13 version that should fix this
prob
On Thu, Aug 25, 2016 at 12:48 AM, Chris Murphy wrote:
> So even after 'dnf clean all' the -13 version that should fix this
> problem is not listed as an update in either updates or
> updates-testing. Is that expected?
It hasn't been that long since the update left the pending state, so
I'm guess