"Something" has happened to machine that was previously OK. Now when I try and emerge anything I get the following errors (for example trying to emerge the possibly problem package):

How do I debug this kind of thing? How do I fix it? Running "make relabel" just raises the same errors..?

Cheers

Ed W


./usr/share/doc/logrotate-3.7.1-r2/
./usr/share/doc/logrotate-3.7.1-r2/logrotate-default.gz
./usr/share/doc/logrotate-3.7.1-r2/logrotate.cron.gz
./etc/
./etc/cron.daily/
./etc/cron.daily/logrotate.cron
./etc/logrotate.conf
./etc/logrotate.d/
./etc/logrotate.d/.keep
>>> Done.
>>> extracting info
>>> extracting logrotate-3.7.1-r2
>>> Merging app-admin/logrotate-3.7.1-r2 to /
>>> Setting SELinux security labels
/var/tmp/portage/logrotate-3.7.1-r2/temp/file_contexts: line 730 has invalid context system_u:object_r:logrotate_exec_t /var/tmp/portage/logrotate-3.7.1-r2/temp/file_contexts: line 731 has invalid context system_u:object_r:logrotate_exec_t /var/tmp/portage/logrotate-3.7.1-r2/temp/file_contexts: line 733 has invalid context system_u:object_r:logrotate_var_lib_t /var/tmp/portage/logrotate-3.7.1-r2/temp/file_contexts: line 735 has invalid context system_u:object_r:logrotate_exec_t /var/tmp/portage/logrotate-3.7.1-r2/temp/file_contexts: line 736 has invalid context system_u:object_r:logrotate_var_lib_t /var/tmp/portage/logrotate-3.7.1-r2/temp/file_contexts: line 738 has invalid context system_u:object_r:logrotate_tmp_t /var/tmp/portage/logrotate-3.7.1-r2/temp/file_contexts: line 740 has invalid context system_u:object_r:logrotate_exec_t /var/tmp/portage/logrotate-3.7.1-r2/temp/file_contexts: line 870 has invalid context system_u:object_r:screen_exec_t /var/tmp/portage/logrotate-3.7.1-r2/temp/file_contexts: line 871 has invalid context system_u:object_r:user_screen_ro_t
Exiting after 10 errors.

!!! ERROR: app-admin/logrotate-3.7.1-r2 failed.
!!! Function dyn_preinst, Line 1314, Exitcode 1
!!! Failed to set SELinux security labels.
!!! If you need support, post the topmost build error, NOT this status message.

!!! FAILED preinst: 1

--
[email protected] mailing list

Reply via email to