Bug 1043989

Ok, I was able to fix this with "group mark remove GNOME", but the issue still persists for upgrades: When upgrading F19 to F20, the group will be marked as installed and thus additional packages and their dependencies are being installed.

I have the same problem in Fedora 21. Yum wants to install additional packages (I removed manually) because of "upgraded group GNOME". However, *no such group exists* (notice there is no GNOME anywhere in the list):

$ yum group list
Loaded plugins: langpacks
Available environment groups:
   Fedora Server
   Fedora Workstation
   Fedora Cloud Server
   KDE Plasma Workspaces
   Xfce Desktop
   LXDE Desktop
   Cinnamon Desktop
   MATE Desktop
   Sugar Desktop Environment
   Development and Creative Workstation
   Web Server
   Infrastructure Server
   Basic Desktop
   Minimal Install
Installed groups:
   LibreOffice
Available Groups:
   3D Printing
   Administration Tools
   Audio Production
   Authoring and Publishing
   Books and Guides
   C Development Tools and Libraries
   Cloud Infrastructure
   Cloud Management Tools
   Cloud Server Tools
   Container Management
   D Development Tools and Libraries
   Design Suite
   Development Tools
   Domain Membership
   Editors
   Educational Software
   Electronic Lab
   Engineering and Scientific
   Fedora Eclipse
   FreeIPA Server
   Games and Entertainment
   Headless Management
   MATE Applications
   MATE COMPIZ
   Medical Applications
   Milkymist
   Network Servers
   Office/Productivity
   RPM Development Tools
   Robotics
   Security Lab
   Sound and Video
   System Tools
   Text-based Internet
   Window Managers
Done

I had to guess that I should use the command
$ yum group mark remove gnome-desktop
The command doesn't even complain when you use the name of an invalid group. So I had to try several times and try to run update afterwards to see whether it worked. This is broken as hell.

I see the point of this feature, though the initial description is quite buggy.  I think one thing that needs to be done is that it must be easy to edit/remove groups, preferably through a plain text file somewhere.  It is not obvious what file "yum group mark remove" is using to keep track, and it makes it feel like it's a "registry" type thing.  We should be able to get out of groups by editing a text file like yum.conf or some new file.

I did see /var/lib/yum/groups/installed and environment, but those don't seem to be something easy for the user to play with.

I had at one point installed group mate-desktop from EPEL and then later removed the rpms.  But on doing yum upgrade I would get:

Installing for group upgrade "MATE":
 gnote                    x86_64 3.8.1-3.el7                   base       3.0 M
 pluma                    x86_64 1.8.1-1.el7                   epel       590 k
 xchat                    x86_64 1:2.8.8-22.el7                base       952 k
 yumex                    noarch 3.0.15-2.el7                  epel       431 k

I ran:

[root@meb packages]# yum groups mark remove MATE
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * extras: cluster
Marked remove: MATE

but it still kept happening.  From the group list I finally discovered I had to run 'yum group mark remove mate-desktop' but I claim it is a bug that run 'mark remove' on a non-existant group name gives no error then.

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.

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.