-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TransactionReplay: handle group package types #1569
TransactionReplay: handle group package types #1569
Conversation
68e4051
to
a8e187b
Compare
Hi, can you please rebase? Not that there are merge requests, but in the commit 1090963 , |
82289e6
to
db4b0a7
Compare
Thank you for catching that. 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is probably just a matter of personal preference, but I would find it more logical if the "." were in the original TransactionReplayError
s instead of adding it in the LogEvent::to_string
, especially when I imagine that there could be a TransactionReplayError
with multiple sentences as a message. That way, it would be well formatted on it's own. But I don't insist on this.
This information is stored in system state for each group and is used during group upgrade.
The ending dot is added later when the string is formatted. For example in `LogEvent::to_string()`.
db4b0a7
to
70ab999
Compare
I don't have a strong preference here, I would be fine either way but it seems most exceptions in libdnf5 don't end with the |
This matches the dnf4 behavior. It fixes confusing behavior where when a `group upgrade` is executed on a new version of a group with new packages it installs only the new packages that match the stored (in system state) package types but it also overrided the package types with the currently configured `group_package_types`.
I have added one more commit that fixes a related problem with group upgrade and package types. |
Thank you! |
17860b6
This information is stored in system state for each group and is used during group upgrade.