# make -f /usr/share/selinux/devel/Makefile foo.pp
cat: /selinux/mls: No such file or directory
make: `foo.pp' is up to date.
# grep /selinux/mls /usr/share/selinux/devel/Makefile
MLSENABLED := $(shell cat /selinux/mls)
# rpm -qf /usr/share/selinux/devel/Makefile
- but I wonder why it looks at the running SE configuration at module "compile" time. It seems like that would do the wrong when run in a chroot (which I do). I would expect it to look at the configuration in /etc/selinux/config instead.
(seen when testing a patch for bug 728576)
It seems like this has been fixed in selinux-policy-3.10.0-18.fc16.noarch with
MLSENABLED := $(shell python -c "import selinux; print(selinux.is_selinux_mls_enabled())")
There is no explicit dependency to libselinux-python (and thus Python). Are there sufficient implicit dependencies - and are they sufficiently stable?
I have changed it to just hard code the one and allow a developer to override it. No python used any longer. Since all Red Hat/Fedora releases use the flag, we should just ship it with our default and not worry about someone installing some random non default policy.
Fixed in selinux-policy-3.10.0-22.fc16
selinux-policy-3.10.0-25.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.10.0-25.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
selinux-policy-3.10.0-25.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.