Bug 1107742

Summary: Exit code 0 with 'yum install existing not-existing'
Product: [Fedora] Fedora Reporter: Adam Samalik <asamalik>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: admiller, jzeleny, msuchy, packaging-team-maint, pnemade, tim.lauridsen
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1107737 Environment:
Last Closed: 2016-07-19 11:46:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1045076    

Description Adam Samalik 2014-06-10 13:59:38 UTC
+++ This bug was initially created as a clone of Bug #1107737 +++

Description of problem:
When I run for example 'dnf install bash fdfrhewiaur' (first package exists, the second doesn't), I got an exit code 0. 

Version-Release number of selected component (if applicable):
dnf-0:0.5.2-1.fc20.noarch

How reproducible:

Steps to Reproduce:
1. dnf install bash fdfrhewiaur

Actual results:
exit code == 0

Expected results:
exit code != 0

Additional info:
I got the same behaviour with yum as well.

--- Additional comment from Ales Kozumplik on 2014-06-10 09:54:34 EDT ---

Thanks, we'll take a look.

Comment 1 Miroslav Suchý 2014-11-07 10:38:44 UTC
Reproducer for this bug is:
yum install bash fdfrhewiaur

Comment 2 Fedora End Of Life 2015-05-29 12:04:44 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-29 21:03:07 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Miroslav Suchý 2015-06-30 06:56:07 UTC
Still valid in F22.

Comment 5 Fedora End Of Life 2016-07-19 11:46:59 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.