Description of problem: dnf has methods for install, remove & update groups (object) dnf has methods for reading comps groups & categories but there is no public API for check if a group is allready installed. USECASE: In a graphic package manager like yumex-dnf, show groups available on the system and give the user an option to install/remove them. But it dont make much sense if the end user dont can see if a given group is all ready installed. Version-Release number of selected component (if applicable): 1.1.9
We will take a look how to make Group querying API more convenient (like package queries), refactor it and document it.
Thanks
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Please can you provide additional details? Do you search for something like in dnf.comps.Comps(): group_installed() - List of installed contained :class:`dnf.comps.Group` objects ordered by `display_order` tag defined in comps.xml file. environments_installed - List of installed contained :class:`dnf.comps.Environment` objects ordered by `display_order` tag defined in comps.xml file. Thanks for answer?
Or do you prefer function that returns installed, available groups like _group_lists in group command?
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.
Necessary for Unified Software database.
Patch posted https://github.com/rpm-software-management/dnf/pull/892
This bug is currently reported against a Fedora version which is already unsuported. I am changing the version to '27', the latest supported release. Please check whether this bug is still an issue on the '27' release. If you find this bug not being applicable on this release, please close it.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
Closing due to reporter inactivity.