Skip to content

Conversation

@pkratoch
Copy link
Contributor

@pkratoch pkratoch commented Dec 9, 2025

In case of REASON_CHANGE action, the reason must change even for the
GROUP reason, even though it is not used in the package states directly
(the DEPENDENCY in combination with the package name on the list of
packages belonging to a group is used instead).

Otherwise, the package can be still considered user-installed (if that
was the original reason).

Resolves: #935

Tests: rpm-software-management/ci-dnf-stack#1803

In case of REASON_CHANGE action, the reason must change even for the
GROUP reason, even though it is not used in the package states directly
(the DEPENDENCY in combination with the package name on the list of
packages belonging to a group is used instead).

Otherwise, the package can be still considered user-installed (if that
was the original reason).

Resolves: rpm-software-management#935
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

'dnf5 mark group' does not work properly

1 participant