Bug 521008

Summary: [5.4] yum returns the error when updating the package which doesn't exist.
Product: Red Hat Enterprise Linux 5 Reporter: Issue Tracker <tao>
Component: yumAssignee: James Antill <james.antill>
Status: CLOSED ERRATA QA Contact: Petr Sklenar <psklenar>
Severity: high Docs Contact:
Priority: high    
Version: 5.4CC: bugzilla, gbarros, jhutar, psklenar, tao, vgaikwad
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
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 04:29:41 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 499522    

Comment 7 Vishal Gaikwad 2009-10-07 04:20:26 EDT
Public Summary:

When you try to update for non-exist packages with yum-3.2.22-20.el5 included Red Hat Enterprise Linux 5.4, yum returns  an error status.

# rpm -q yum; yum update none_exist > /dev/null; echo $?
Error: No Package Matching none_exist

yum earlier than this version returns a normal status.

# rpm -q yum; yum update none_exist > /dev/null; echo $?

We have identified this as a bug. A patch has been committed upstream which resolves this issue.

Comment 11 David Mansfield 2009-11-19 11:02:15 EST
is there a "snapshot" build of this updated yum I can test with?  I'm hitting this bug right now.
Comment 18 David Mansfield 2010-03-11 13:57:37 EST
i realize there are other bugs/comments i cannot see, and I'm hoping one of them contains a link to a fixed version of this package.  is that possible?
Comment 19 Guil Barros 2010-03-11 14:16:16 EST
Hi David,

There should be a fixed release shortly, stay tuned!

Comment 20 errata-xmlrpc 2010-03-30 04:29:41 EDT
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.