Open tsuchiclay opened 1 month ago
Thanks for the report, the issue is valid.
To fix this, I think the behavior of group install would need to change, so that it produces an empty transaction if there is nothing to do. Interestingly, it is already so for group remove, so maybe it would be possible to implement it also for group install.
The behavior is the same for dnf5, so it should be fixed there as well - https://github.com/rpm-software-management/dnf5/issues/1492
When nothing changes in the result by
group install
, I would suggest changing the behavior of thehistory
so that nothing appears for that event. But since it is about QoL, it should be a low priority. The version ofdnf
used is as follows.When some packages are installed by
group install
, the history will look like this.Then, when the same is done again, the
history
is updated as follows, even though no updates, new installations, or other things have happened.I would suggest, for example, that the behavior of the
history
withgroup install
be changed to the same asinstall
withoutgroup
, as shown below.However, the current
history
behavior described here may be reasonable in ways I have not thought of. If so, I would appreciate a few hints on that point.