Description of problem: If an API user is executing a big transaction like updating many packages it is useful to give some feedback to the user, what is going on. dnf.Base.do_transaction has an non public api parameter display, there takes a subclass based on dnf.yum.rpmtrans.TransactionDisplay. I most cases a only the TransactionDisplay.event is need for soling the need for giving the user feedback. So adding a simple TransactionDisplay subclass to dnf.callback ex. RPMProgress with an progress method the user could overload with a subclass cauld be a way to go and then make this class and do_transaction(display=...) public api cauld be a way to go. I can take a shot of making it, but need to know if it is a way to go or some other approch is better. Version-Release number of selected component (if applicable): 0.4.19
This touches a lot of the old Yum code that we do not want to expose and will probably need massive refactoring. The resulting API for this will have to be aligned with other dnf.callback interfaces, not expose anything from dnf.yum* and follow the 'less is more' principle. Also it needs to be extensible for more types of progress operations later. Generally it is low priority now.
Created attachment 878458 [details] test implementation of rpm callback
My idea was to something like this, and when the old yum code is refactored, then the RPMProgress class is changed to match but the user get the same interface.
Example: import dnf import dnf.callback class MyRPMCallback(dnf.callback.RPMProgress): def progress(self, name, to_do, fraction): print("%s : %s : %f" % (name, to_do, fraction)) base = dnf.Base() base.install("somthing") base.resolve() base.do_transaction(display=MyRPMCallback())
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.