Description of problem:
yum grouplist uses a very uncommon algorithm to find out if a group is installed. See http://lists.baseurl.org/pipermail/yum-devel/2008-June/005310.html for details. Because of this it is not possible to install a group in gpk-application if yum's definition of "installed" is already satisfied.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install all mandatory packages of a group
1. install a single optional package of a group that has no mandatory packages
The group will be shown as installed in gpk-application. Therefor it's not possible to install the rest of that group graphically.
Group should not be treated as installed until all default packages of that group are installed -or-
gpk-app should allow to install packages in a group that is installed.
IMO the bug is not really in PK, but in yum. The yum devs think different and told me to file a bug against PK. See bug 526258 for details.
I can fully understand if you close this bug NOTABUG or WONTFIX, but in that case please help me to convince the yum guys that their definition of an "installed" group is wrong.
Fixed in PackageKit-0.5.7-1 (if not earlier). Thanks for taking care of this.
*** This bug has been marked as a duplicate of bug 489477 ***