Paul Howarth wrote:
On Sun, 2006-03-26 at 14:37 +0200, A.J. Bonnema wrote:
Paul Howarth wrote:
On Sun, 2006-03-26 at 07:45 -0500, Jim Cornette wrote:
The yumex developer is already on this:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186076
Paul.
Thanks for the hint Paul. I had already made the bug-report (186782).
From yumex I could only find one bug-report which was about updating
packages (186227), like in your link. My problem is about installing new
packages and it only occurs on some packages, not all. An unrelated problem?
Maybe, maybe not. As Jim mentioned, there are problems with scriptlets,
and many packages don't have scriptlets in them.
Paul,
For reference to the problem that I encountered, I included a link to
the bug report that was fixed that related to pup.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177883
Adjust the SELinux settings as described in the bug report Paul
mentioned or run SELinux in permissive mode when using Yumex until the
policy change is applied to yumex of the SELinux policy rules.
setenforce 0 puts you in permissive.
getenforce informs you of what mode you are in.
setenforce 1 will put you into enforcing mode again.
This should probably be added to yumex during its installation. It is a
bit cryptic to me. I do realize that it will set the policy correct for
yumex to work properly. (From bug report on yumex)
[root@localhost ~]# semanage fcontext -a -f -- -t rpm_exec_t
/usr/share/yumex/yumex
[root@localhost ~]# restorecon /usr/share/yumex/yumex
[root@localhost ~]# semanage fcontext -a -f -l -t rpm_exec_t /usr/bin/yumex
[root@localhost ~]# restorecon /usr/bin/yumex
