Description of problem:
up2date is not running under a context that allows it to install rpm
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to run up2date
You need to modify /etc/security/console.apps/up2date
ROLE and TYPE will cause up2date to run with the rpm_t policy and
allow it to install rpm's on a SELinux box. If the box
is not SELinux these fields will be ignored.
Could you add them to the up2date package.
I don't know whether this is the same issue, but for my case up2date
couldn't even run.
If I start up2date as a normal user, I get the following error after
entering root password:
"Could not set exec context to user_u:sysadm_r:sysadm_t."
If I start update as root user, it runs.
I tried making the change recommended, it had no effect.
I tried to modify "/etc/security/console.apps/up2date" to add the
following lines as recommended by the bug reporter:
I got the following error:
[chennan@localhost chennan]$ up2date
Could not set exec context to user_u:rpm_t:sysadm_r.
You need to update the usermode package and grab the latest policy files.
committed to cvs, 4.3.15 or higher should have it
running uptodate stated there was an ethereal dependency problem..
after rebooting i got to:
Kernel Panic: attempted to kill init!
to fix this i had to boot into rescue mode...and edit the following:
this originally read:
in order to boot my system I changed it to:
then had to:
to get back into fedora core 2 test 2
hope this info helps... just reporting my similar problem.
Initially I had the same problem as #3 above, but upgrading to
policy-1.10.1-4 and kernel-2.6.5-1.308 from the development tree on an
otherwise blank fc2test2 resolves this.
My recomendation would be to close this as RAWHIDE