Bug 521008 - [5.4] yum returns the error when updating the package which doesn't exist.
[5.4] yum returns the error when updating the package which doesn't exist.
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: James Antill
Petr Sklenar
Depends On:
Blocks: 499522
  Show dependency treegraph
Reported: 2009-09-03 02:51 EDT by Issue Tracker
Modified: 2014-01-21 01:14 EST (History)
6 users (show)

See Also:
Fixed In Version: yum-3.2.22-23.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-03-30 04:29:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
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.


Note You need to log in before you can comment on or make changes to this bug.