policycoreutils-python has explicit runtime requirements on selinux-policy-devel and on checkpolicy (which is also for development only). Could we split the devel parts of this package out so that this isn't necessary? We shouldn't have -devel packages pulled into the basic cloud image, and cloud-init uses this.
Ugg the bigest concern I have here is moving audit2allow out of the base install. Since users are used to using this, and might have a difficult time finding it. I made this change to policycoreutils-2.1.13-30.fc19 I guess if we updated base to include policycoreutils-devel instead of python we could put this into F18.
(In reply to comment #1) > Ugg the bigest concern I have here is moving audit2allow out of the base > install. Since users are used to using this, and might have a difficult > time finding it. Ahh, that explains the whole thing. In a sense, that's development, so it makes sense that devel packages are pulled in. I'm a big fan of audit2allow as a smaller hammer than the, ahem, normal response of disabling selinux forever. :) Still, I think we want it not in core. I think it makes sense to put it in @standard, the new group in F18+ that replaces "@base".
Fixed in policycoreutils-2.1.13-32.fc18 I setup policycoreutils-gui to require -devel.
policycoreutils-2.1.13-44.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/policycoreutils-2.1.13-44.fc18
Package policycoreutils-2.1.13-44.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing policycoreutils-2.1.13-44.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20070/policycoreutils-2.1.13-44.fc18 then log in and leave karma (feedback).
policycoreutils-2.1.13-44.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.