Bug 1079526

Summary: [api][rfe] get access to the yum history from DNF api
Product: [Fedora] Fedora Reporter: Tim Lauridsen <tim.lauridsen>
Component: dnfAssignee: rpm-software-management
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jzeleny, ngompa13, rholy, tim.lauridsen
Target Milestone: ---Keywords: Reopened, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:38:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1167239    
Bug Blocks: 1665453, 1066869, 1214067    

Description Tim Lauridsen 2014-03-21 18:37:41 UTC
Description of problem:

It should be possible to get access to the transaction history from the DNF API

Usecase:

A it shoud be possible to show and search the transaction history from a package management gui.

optional an api for redo/undo a historical transaction would be very useful
to ex. rollback a update transaction there causes problems.

Version-Release number of selected component (if applicable):
0.4.18

Comment 1 Ales Kozumplik 2014-03-24 06:48:16 UTC
True, we should provide this.

What information would you like exposed? I.e. is the use case 'displaying transaction history in yumex' (meaning: list of transactions, their times and packages that got installed/removed/changed) or is it something else?

Comment 2 Tim Lauridsen 2014-03-24 07:25:25 UTC
Yes, a list of transactions with times og actions performed, that it

Comment 3 Honza Silhan 2014-04-25 12:37:59 UTC
Tim, redesigned history db and yumdb will be stored in/accessed from Swdb. Swdb will be a standalone library with C/C++/Python API used by Dnf/PackageKit/yum to maintain log of transaction and additional package info (from which repo was package installed, reason, etc.). Experimental preview should be released soon.

Comment 4 Tim Lauridsen 2014-04-25 13:27:18 UTC
@Jan, Thanks for info, looking forward for the preview

Comment 5 Fedora End Of Life 2015-05-29 11:20:11 UTC
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.

Comment 6 Fedora End Of Life 2015-06-29 19:38:07 UTC
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.

Comment 7 Neal Gompa 2017-12-10 16:03:24 UTC
This is still a problem for me today with dnfdaemon, and I still don't see an API documented: http://dnf.readthedocs.io/en/latest/api.html