Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1277115 - gnome-software doesn't write data to dnf's history database
Summary: gnome-software doesn't write data to dnf's history database
Keywords:
Status: CLOSED DUPLICATE of bug 1259865
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-software
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-02 12:14 UTC by Christian Stadelmann
Modified: 2016-09-28 19:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-28 19:59:31 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Christian Stadelmann 2015-11-02 12:14:38 UTC 
Description of problem:
After using gnome-software you can not see your package transactions (installation, removal, update, …) in dnf's history database. This renders `dnf history` pretty unreliable and `dnf history userinstalled` can't be used any more to get a kickstart file.

Version-Release number of selected component (if applicable):
dnf-1.1.3-1.fc23.noarch
gnome-software-3.18.2-2.fc23.x86_64
Comment 1 Kalev Lember 2015-11-04 16:36:27 UTC 
AFAIK the plan here is to make both DNF and gnome-software use libhif and have libhif write to the shared database.
Comment 2 Georg Sauthoff 2015-11-21 20:38:48 UTC 
Similar story when a package was installed via /usr/libexec/pk-command-not-found (part of PackageKit-command-not-found) then it also isn't listed in the output of `dnf history userinstalled`.

(cf. #1284194)
Comment 3 Christian Stadelmann 2016-09-28 19:59:31 UTC 

*** This bug has been marked as a duplicate of bug 1259865 ***
Note You need to log in before you can comment on or make changes to this bug.