Bug 468252
Summary: | Sofware Log Viewer appears not to talk to the backend | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bill Nottingham <notting> |
Component: | gnome-packagekit | Assignee: | Robin Norwood <robin.norwood> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | rhughes, richard, robin.norwood, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-24 09:03:34 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bill Nottingham
2008-10-23 18:58:05 UTC
No, I don't think it should -- PK transactions have tons more detail that what we can glean from yum.log or the rpmdb, for instance the user, the duration, what packages were deps and what was the point of the transaction. For some backends we need to know the transaction ID, which is needed for audit or rollback. You just can't get that from yum or rpm. Also, the point of the PK log viewer was to see all the high level stuff you've done or was done automatically, like openoffice installing clipart, or me installing kernel-devel. If you users want to use yum or rpm, sure, that's no problem, but they don't get the GUI info in the log viewer. You can use pkcon on the command line, but if you use rpm or yum directly PK has no idea what's going on. |