lp:~wattazoum/apport/trac-crashdb

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1357. By Oumar Aziz OUATTARA on 2009-10-17

* merge with official branch.
* update the crashDB documentation

1356. By Oumar Aziz OUATTARA on 2009-04-10

Check for duplicates before sending
Mark the current report as a duplicate.
Add a comment on the Master report to notice this duplicate.
Add some documentation.

1355. By Oumar Aziz OUATTARA on 2009-04-09

* Updated Documentation
* Fix 2 bugs (typos)
* Add Trac attributes customization capability
  * Use a package-hook to put a "Trac<Attribute>" field to the report
  * The Entry is applied to the ticket as <Attribute> then removed from the report.
* updated the TestCase to use customization capability.

[TODO]
 * password security
 * check for duplicates before sending

[IDEA]
 * allow ui extension to package-hook

1354. By Oumar Aziz OUATTARA on 2009-04-05

- get sure of having a good URL syntax.
- add documentaion.

1353. By Oumar Aziz OUATTARA on 2009-04-05

implement Trac CrashDB

1352. By Martin Pitt on 2009-04-01

releasing version 0.148

1351. By Martin Pitt on 2009-04-01

bin/kernel_oops: Add "kernel-oops" tag. Since both bin/kernel_oops and
bin/apportcheckresume use the "kerneloops" bug class, it previously was
hard to filter out the bug reports which were real oopses. (LP: #349621)

1350. By Martin Pitt on 2009-04-01

bin/apport-retrace: Fix KeyError crash on bugs with an ExecutablePath
which does not exist any more. Close the bug as invalid instead.
(LP: #352331)

1349. By Martin Pitt on 2009-04-01

apport/hookutils.py: Move attach_media_build() to
general-hooks/ubuntu.py, since it is Ubuntu specific.

1348. By Martin Pitt on 2009-04-01

debian/local/ubuntu-bug: Drop generic passthrough of apport-{cli,gtk,kde}
options since this leads to too much confusion. Instead just support a
single argument and check whether it is a pid, a package name, a .crash
file, or a program path. This does the right thing when calling it with a
.crash file (LP: #347392) and fixes the help output (LP: #344923) Update
manpage accordingly.