dupdb-admin - Manage the duplicate database for apport-retrace.
dupdb-admin -f dbpath status
dupdb-admin -f dbpath dump
dupdb-admin -f dbpath changeid oldid newid
apport-retrace(1) has the capability of checking for duplicate bugs
(amonst other things). It uses an SQLite database for keeping track of
master bugs. dupdb-admin is a small tool to manage that database.
The central concept in that database is a "crash signature", a string
that uniquely identifies a particular crash. It is built from the
executable path name, the signal number or exception name, and the
topmost functions of the stack trace.
The database maps crash signatures to the 'master' crash id and thus
can close duplicate crash reports with a reference to that master ID.
It also tracks the status of crashes (open/fixed in a particular
version) to be able to identify regressions.
status Print general status of the duplicate db. For now, it only shows
the time when the database was "consolidated" last, i. e. when
the bug states (open/fixed) in the SQLite database where updated
to the actual states in the bug tracking system.
dump Print a list of all database entries.
Change the associated crash ID for a particular crash.
-f path, --database-file=path
Instead of processing the new crash reports in /var/crash/,
report a particular report in an arbitrary file location. This
is useful for copying a crash report to a machine with internet
connection and reporting it from there. This defaults to
apport and the accompanying tools are developed by Martin Pitt