Bug 1018833 - yum install @foo doesn't give errors when 'foo' doesn't exist
yum install @foo doesn't give errors when 'foo' doesn't exist
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-10-14 09:33 EDT by Branko Grubić
Modified: 2015-06-29 21:24 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-06-29 21:24:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Branko Grubić 2013-10-14 09:33:46 EDT
Description of problem:
On f20 when you try to install groups with  'yum install @groupname1 @groupname2' and one of them is not available you only get "Nothing to do", it doesn't say group 'foo' (for example) doesn't exist, same happens if you try only one group which doesn't exist. (yum install @foo (where foo is not a valid group name)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. yum install @<non_existing_group>

Actual results:
No error message tha group doesn't exist

Expected results:
Shows error message group 'xyz' doesn't exist

Additional info:
Comment 1 Branko Grubić 2013-10-14 09:49:18 EDT
I made a mistake in my first comment/original report, "Nothing to do" only appears when one group or probably multiple but all of them are invalid/non-existing groups are in the "yum install" command, if you have one valid and other invalid group (or probably any mix of them (but at least one valid and one invalid) it will install valid groups and won't say anything about invalid.
Comment 2 James Antill 2013-10-14 15:51:00 EDT
 Fixed upstream.

commit ff5416b1532fe43c68bf51ae30751504885a501a
Author: James Antill <james@and.org>
Date:   Mon Oct 14 15:49:35 2013 -0400

    Give same non-exist msg. for install @foo as group install foo. BZ 1018833.
Comment 3 Adam Williamson 2013-12-14 17:17:19 EST
I believe this change is the cause of quite a lot of the recent reports that yum is printing 'Warning: group (group) does not exist.' errors when they run 'yum update' recently. See https://bugzilla.redhat.com/show_bug.cgi?id=1043202 .
Comment 4 Fedora End Of Life 2015-05-29 05:34:26 EDT
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 5 Fedora End Of Life 2015-06-29 21:24:35 EDT
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

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

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