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.
On Wed, Aug 24, 2016 at 3:31 PM, Alexander Ploumistos alex.ploumistos@gmail.com wrote:
It's already been dealt with, see RHBZ #1368745.
Thanks. Kinda surprising -12 made it to stable...
On Wed, Aug 24, 2016 at 3:35 PM, Chris Murphy lists@colorremedies.com wrote:
On Wed, Aug 24, 2016 at 3:31 PM, Alexander Ploumistos alex.ploumistos@gmail.com 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 problem is not listed as an update in either updates or updates-testing. Is that expected?
On Thu, Aug 25, 2016 at 12:48 AM, Chris Murphy lists@colorremedies.com 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 guessing it's just a matter of mirrors catching up.