Hi All,
With the latest rawhide I get a lot of: error: %preun(kernel-2.6.13-1.1594_FC5.x86_64) scriptlet failed, exit status 255 error: %pre(kernel-2.6.14-1.1771_FC5.x86_64) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping kernel-2.6.14-1.1771_FC5 error: %preun(kernel-2.6.14-1.1770_FC5.x86_64) scriptlet failed, exit status 255 error: %preun(kernel-2.6.14-1.1743_FC5.x86_64) scriptlet failed, exit status 255 error: %preun(kernel-2.6.14-1.1644_FC5.x86_64) scriptlet failed, exit status 255
This is when running yum -y update kernel as root. I became root by doing su - in an xterm started as a normal user.
Running yum when directly logged in as root from the console works fine.
Bugzilla?
Regards,
Hans
On 12/18/05, Hans de Goede j.w.r.degoede@hhs.nl wrote:
Running yum when directly logged in as root from the console works fine.
Bugzilla?
selinux issue most likely, look over the archives and bugzilla and relabel your filesystem
-jef
Jeff Spaleta wrote:
On 12/18/05, Hans de Goede j.w.r.degoede@hhs.nl wrote:
Running yum when directly logged in as root from the console works fine.
Bugzilla?
selinux issue most likely, look over the archives and bugzilla and relabel your filesystem
Filesystem has already been relabeled, both manually and automaticly on reboot, this only happened if I've done "su -" to root, not when directly logged in as root.
Regards,
Hans
Hans de Goede wrote:
Jeff Spaleta wrote:
On 12/18/05, Hans de Goede j.w.r.degoede@hhs.nl wrote:
Running yum when directly logged in as root from the console works fine.
Bugzilla?
selinux issue most likely, look over the archives and bugzilla and relabel your filesystem
Filesystem has already been relabeled, both manually and automaticly on reboot, this only happened if I've done "su -" to root, not when directly logged in as root.
Regards,
Hans
What policy are you running?