Hi,

        I am in the process of uploading the 20090828, but I think this
 bug was actually fixed in 20080818. Please re-test the new policy
 version (0.2.20090828, which should in uploaded later today).


On Sat, Aug 22 2009, Philipp Kern wrote:

> Locating modules
> Calculating dependencies between modules
> libsepol.print_missing_requirements: ricci's global requirements were not 
> met: type/attribute consoletype_exec_t

        This has been fixed in a newer upload.

> semodule_deps:  Error while linking packages
> Ordering modules based on dependencies
> Selecting modules based on installed packages
> libsepol.context_from_record: type httpd_cvs_script_exec_t is not defined
> libsepol.context_from_record: could not create context structure
> libsepol.context_from_string: could not create context structure
> libsepol.sepol_context_to_sid: could not convert 
> system_u:object_r:httpd_cvs_script_exec_t:s0 to sid
> invalid context system_u:object_r:httpd_cvs_script_exec_t:s0

        I can no longer see this in 20090818 version of the policy.

> libsemanage.semanage_install_active: setfiles returned error code 1.


> libsemanage.semanage_install_active: Could not copy 
> /etc/selinux/default/modules/active/policy.kern to 
> /etc/selinux/default/policy/policy.24. (No such file or directory).
> semodule:  Failed!
> Error running "semodule -b base.pp -s default -n  -i unconfined.pp -i 
> netutils.pp -i cvs.pp -i dbus.pp -i lvm.pp -i loadkeys.pp -i ssh.pp -i 
> vbetool.pp -i consolekit.pp -i tzdata.pp -i setroubleshoot.pp -i xserver.pp 
> -i apm.pp -i tcpd.pp -i usbmodules.pp -i gpg.pp -i cdrecord.pp -i 
> dmidecode.pp -i dhcp.pp -i sudo.pp -i pythonsupport.pp", please load policy 
> manually and report a bug.

        This seems to work now.

        manoj
-- 
Neutrinos are into physicists.
Manoj Srivastava <[email protected]> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to