allow defining crashdb inline within the report
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Wishlist
|
Martin Pitt |
Bug Description
In an application like bzr we want to record crash files on every platform where apport is installed, Ubuntu or not. These reports are obviously not generally Ubuntu-specific and need to go into the upstream bug tracker (bugs.l.n/bzr). apport has a nice crashdb mechanism for defining this, but unfortunately it depends on having a crashdb definition installed into /etc/apport/
Furthermore, apport aborts if the crashdb referenced in the crash file is not known on the system.
It would be nice if all the information about where to file the report could be recorded at the time the report is written, so the application was more selfcontained.
One way to handle this would be to allow the impl/project/
Changed in apport: | |
assignee: | nobody → Martin Pitt (pitti) |
importance: | Undecided → Wishlist |
status: | New → Triaged |
affects: | apport → apport (Ubuntu) |
tags: | added: arb |
Fixed in trunk r2464. The CrashDB: field can now directly give the DB specification Python dictionary, i. e. what would otherwise go into the crashdb.conf.d/ snippet.