Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionBranislav Náter
2011-08-24 13:10:52 UTC
Description of problem:
matahari-selinux rules are now included in selinux-policy package. matahari-selinux package should be removed (obsoleted). When we try to do "yum update" on current tree, we get following error:
# yum update
<snip>
--> Finished Dependency Resolution
Error: Package: matahari-selinux-0.4.2-7.el6.i686 (@rhel6)
Requires: matahari = 0.4.2-7.el6
Removing: matahari-0.4.2-7.el6.i686 (@rhel6)
matahari = 0.4.2-7.el6
Updated By: matahari-0.4.2-8.el6.i686 (rhel6)
matahari = 0.4.2-8.el6
Available: matahari-0.4.0-5.el6.i686 (rhel-i386-server-6)
matahari = 0.4.0-5.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. yum update
Actual results:
see description of problem
Expected results:
smooth update
(In reply to comment #2)
> Why is this our bug?
@dwalsh: Don't know. mgrepl was the one who moved this from matahari to selinux-policy, so probably check with him
(In reply to comment #3)
> (In reply to comment #2)
> > Why is this our bug?
>
> @dwalsh: Don't know. mgrepl was the one who moved this from matahari to
> selinux-policy, so probably check with him
Yeap, by accident.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
No description required
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1569.html
Description of problem: matahari-selinux rules are now included in selinux-policy package. matahari-selinux package should be removed (obsoleted). When we try to do "yum update" on current tree, we get following error: # yum update <snip> --> Finished Dependency Resolution Error: Package: matahari-selinux-0.4.2-7.el6.i686 (@rhel6) Requires: matahari = 0.4.2-7.el6 Removing: matahari-0.4.2-7.el6.i686 (@rhel6) matahari = 0.4.2-7.el6 Updated By: matahari-0.4.2-8.el6.i686 (rhel6) matahari = 0.4.2-8.el6 Available: matahari-0.4.0-5.el6.i686 (rhel-i386-server-6) matahari = 0.4.0-5.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. yum update Actual results: see description of problem Expected results: smooth update