History is incomplete

Bug #743498 reported by EricDHH
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: synaptic

For debugging purposes old versions has remembered every package change with calendar in the system. But with last updates i only see some own changes, but not package updates and deinstallations. Don't know if this is a bug or a new feature?

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: synaptic 0.75.1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-genusername 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Sun Mar 27 09:44:09 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110318)
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: synaptic
UpgradeStatus: Upgraded to natty on 2011-03-25 (2 days ago)

Revision history for this message
EricDHH (ericdhh) wrote :
Revision history for this message
Robert Roth (evfool) wrote :

I am marking this as Confirmed, as indeed, Synaptic only shows the changes made from synaptic. You did see updates and removals in synaptic history before, because update-manager was also using synaptic as it's backend, but switched to using aptdaemon, thus it's operations are not visible from synaptic history.

The inconsistency here is that synaptic changes are visible in the installation history from software center, but the reverse is not true, package changes made by anything else but synaptic are not visible in synaptic. I guess synaptic should also read apt history (or dpkg history) as seeing only the changes made by synaptic is rarely useful (if at all).

What do you think, mvo? If you agree, I could check the migration to apt history from the custom synaptic log used now.

Changed in synaptic (Ubuntu):
status: New → Confirmed
summary: - Chronicles are not complete
+ History is incomplete
Revision history for this message
dg1727 (dg1727) wrote :

This may be a duplicate of bug 217413.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.