Description of problem: Consider the following usage scenario. After an upgrade all packages were improperly marked which precluded dnf autoremove from working. Using dnf mark remove '*'; dnf mark install package-spec messed up dnf reasons without possible way to recover. Re-installing everything would be an overkill. Please, implement something like dnf group mark --force group-spec which would actually mark all group packages as reason 'group'. Then it would be possible to use dnf history userinstalled >somefile; dnf group mark --force group-spec; cat somefile | xargs dnf mark install to clean-up the system. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I think it would be sufficient to just change the reason to group for all installed packages that belong to group A after 'group mark install A'.
Yes, but wouldn't that break the spec? According to the GitHub Wiki the group install has the same semantics as the group mark and removing the group should not remove packages explicitly installed earlier. That's why I proposed it to be explicitly forced by the user.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
The root issue could have been fixed but we should still fix "dnf group mark" command as it's in comment 1.
I created a patch that implements requested feature (https://github.com/rpm-software-management/dnf/pull/854).