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.
Bug 466499 - RFE: yum install ./pkg*.rpm shouldn't install packages obsoleted by another package (rpm too)
Summary: RFE: yum install ./pkg*.rpm shouldn't install packages obsoleted by another p...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On: 461898
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-10 16:02 UTC by James Antill
Modified: 2010-11-10 22:00 UTC (History)
7 users (show)

Fixed In Version: yum-3.2.27-7.el6
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 22:00:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Bill Nottingham 2008-10-10 18:10:56 UTC 
If you change this in RPM, it can still cause gotchas with yum under the following scenario:

- A obsoletes B
- you have neither installed
- you install B
- upgrade then pulls in A

So, I'm not sure the simple fix here helps, but a complex fix that doesn't allow installing B in the situation above won't be applicable to RPM, since it doesn't deal at the repository level.
Comment 2 John W. Lockhart 2008-10-10 18:31:39 UTC 
Why is the scenario in Comment 1 a problem?  It's exactly what you'd get if B were in a channel, and then A was released.  Packages that obsolete one another are always worth an extra few doses of caution, and why things like --exclude exist.  Correct?  or am I missing something?
Comment 3 James Antill 2008-10-10 18:40:43 UTC 
Yeh, I think that's fine ... as long as rpm doesn't allow both to be installed I'm fine ... even if it allows you to do: rpm -e A && rpm -ivh B ... that's fine, yum can deal with the result.
Comment 4 RHEL Program Management 2009-06-15 21:02:12 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 5 James Antill 2010-05-20 19:48:06 UTC 
On the yum side, if obsoletes processing is turn on we now look at that. So this is "fixed" I guess.
Comment 9 releng-rhel@redhat.com 2010-11-10 22:00:24 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.