Hello,
Is container-selinux package installed on your system? I believe it's caused due to conflict between selinux-policy and container-selinux packages.
Thanks, Lukas.
On 12/09/2016 08:28 AM, Thomas Mueller wrote:
Am 09.12.2016 um 00:24 schrieb Parker, Michael D.:
Hmmm…..There seems to be some errors in the last released policies on FEDORA 25 from the standards update repo.
.
.
.
Running transaction
Upgrading : selinux-policy-3.13.1-225.1.fc25.noarch 1/18
Re-declaration of boolean virt_sandbox_use_fusefs
Failed to create node
Bad boolean declaration at /var/lib/selinux/targeted/tmp/modules/100/virt/cil:152
semodule: Failed!
Upgrading : selinux-policy-targeted-3.13.1-225.1.fc25.noarch 2/18
Re-declaration of boolean virt_sandbox_use_fusefs
Failed to create node
Bad boolean declaration at /var/lib/selinux/targeted/tmp/modules/100/virt/cil:152
/usr/sbin/semodule: Failed!
Upgrading : NetworkManager-libnm-1:1.4.2-2.fc25.x86_64 3/18
Upgrading : NetworkManager-1:1.4.2-2.fc25.x86_64 4/18
Upgrading : selinux-policy-sandbox-3.13.1-225.1.fc25.noarch 5/18
Re-declaration of boolean virt_sandbox_use_fusefs
Failed to create node
Bad boolean declaration at /var/lib/selinux/targeted/tmp/modules/100/virt/cil:152
semodule: Failed!
Upgrading : selinux-policy-mls-3.13.1-225.1.fc25.noarch 6/18
Upgrading : selinux-policy-minimum-3.13.1-225.1.fc25.noarch 7/18
Failed to resolve typeattributeset statement at /var/lib/selinux/minimum/tmp/modules/100/xserver/cil:472
/usr/sbin/semodule: Failed!
.
i'll see the same error with selinux-policy-minimum-3.13.1-225.1.fc25.noarch .
But there was no error upgrading to selinux-policy-targeted-3.13.1-225.1.fc25.noarch
- Thomas
selinux mailing list -- selinux@lists.fedoraproject.org To unsubscribe send an email to selinux-leave@lists.fedoraproject.org