Since we use rpmtsAddReinstallElement rpm also uninstalls the package #1660
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It calls callbacks for
RPMCALLBACK_INST_START
andRPMCALLBACK_INST_PROGRESS
just like before when the reinstall was done through regural install (rpmtsAddInstallElement) but in addition it also callsRPMCALLBACK_UNINST_START
andRPMCALLBACK_UNINST_PROGRESS
. To ensure they find theDnfPackage
add it toremove_helper
array.Unfortunaly this means that the reinstall action is reported twice to the clients (one install and one uninstall). We could try to hide one of the them but I think a better solution is to report what is actually happening and report one install and one uninstall.
Fixes: #1653
This is for the context part of libdnf (microdnf, packagekit, ...)