Bug 526064
Summary: | yum check-update ignores --obsoletes parameter | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Trevor Hemsley <trevor.hemsley> |
Component: | yum | Assignee: | James Antill <james.antill> |
Status: | CLOSED ERRATA | QA Contact: | Petr Sklenar <psklenar> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.4 | CC: | ajb, jhutar, psklenar |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | yum-3.2.22-23.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-30 08:30:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Trevor Hemsley
2009-09-28 16:08:08 UTC
"yum check-update --verbose" will list obsoletes packages, in the 5.4 version of yum (3.2.22-20) and the last part of the man page about check-update says: Running in verbose mode also shows obsoletes. The obsoletes flag is almost always on, so the cmd line option does nothing (see yum.conf which has obsoletes=1 in it). This is illogical behaviour and should be fixed. Check-update should do the same as update or there is no point in having it. Check-upate should respect teh same options that update does. I am running 5.3 as my hosting provider has not rolled out 5.4 yet and man yum says nothing about this. What's the point in check-update using a different switch to obtain the same result. Fair enough, I've made it output when obsoletes is on now. It'll be changed in 5.5. Great, I'll look forward to 5.5 then. Thanks. adding qa-keywords: RHTSdone=/CoreOS/yum/Regression/bz526064-yum-check-update-ignores-obsoletes-parameter An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0254.html |