Bug 1261917 - Transactions by PackageKit aren't recorded the DNF transaction log
Transactions by PackageKit aren't recorded the DNF transaction log
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: PackageKit (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Richard Hughes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-10 08:36 EDT by Neal Gompa
Modified: 2015-09-14 06:43 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-09-14 06:43:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Neal Gompa 2015-09-10 08:36:22 EDT
Description of problem:
Transactions (such as package updates, installs, etc.) are not recorded in the DNF transaction log. Consequently, it's not possible to audit or roll back updates through DNF if they are bad.

Version-Release number of selected component (if applicable):
PackageKit-1.0.8-2.fc22

How reproducible:
Always

Steps to Reproduce:
1. Be notified of updates
2. Update through PackageKit (pkcon, apper, GNOME Software, etc.)
3. Do "dnf history info"

Actual results:
The latest transaction shown is the last one triggered through DNF

Expected results:
The latest transaction shown is the one done by PackageKit
Comment 1 Richard Hughes 2015-09-14 06:43:56 EDT
yum and PackageKit have traditionally recorded changes to the yumdb. DNF logs changes to the dnfdb, which is exactly the same format but in a different place (overzealous sed script?). Kalev changed PackageKit to record history information in the dnfdb instead of the yumdb for f23.

Note You need to log in before you can comment on or make changes to this bug.