** Changed in: whoopsie (Ubuntu Raring)
Status: New => Won't Fix
** Changed in: apport (Ubuntu Raring)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/957177
Title:
support multiple crashdbs
Status in “apport” package in Ubuntu:
Triaged
Status in “whoopsie” package in Ubuntu:
New
Status in “apport” source package in Raring:
Won't Fix
Status in “whoopsie” source package in Raring:
Won't Fix
Bug description:
Right now Apport only supports sending reports to one crashdb.
With whoopsie we actually have two now, which we want to send reports
to at the same time. whoopsie support is currently bolted on at the
side, but it would be more elegant to create an actual whoopsie
CrashDB backend, and then change /etc/apport/crashdb.conf to send to
multiple DBs at the same time (e. g. launchpad+whoopsie during
development, and just whoopsie post-release).
I just discussed the addition of a new "problem_types" CrashDB option
with Evan, which is a list of "ProblemType" values this crashdb
accepts. So e. g. after release, the launchpad DB could say
"problem_types: ['Bug', 'Package']" if we don't want LP bug reports
for crashes any more.
If we have that, ui.py could then check if any of the active CrashDBs
takes that particular ProblemType, and present the report. If no
crashdb takes it, it wouldn't show the report at all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/957177/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
