Some linked bug reports are private duplicates
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Apport |
Triaged
|
Medium
|
Martin Pitt | ||
| Errors |
New
|
Undecided
|
Unassigned | ||
Bug Description
Right now, the #1 error listed on errors.ubuntu.com -- /usr/bin/
Bug 979278 is a private duplicate of public bug 975320. The problem is that unless you are in the the ubuntu-bugcontrol team, you can't follow the chain through the private report to find the public report.
To fix this, a cron job should take the existing bug in the duplicates database and update to the one it is a duplicate of.
Also, errors.ubuntu.com should tag any bug reports that it synthetically creates.
The cron job should check this tag and, if it is present, prefer a report created by crashdigger over one created by errors.ubuntu.com.
Fixing this is also necessary to tell users whether there is a fix for a crash with a particular signature.
| description: | updated |
| Martin Pitt (pitti) wrote | #1 |
| Changed in apport: | |
| status: | New → Triaged |
| assignee: | nobody → Martin Pitt (pitti) |
| importance: | Undecided → Medium |
| Brian Murray (brian-murray) wrote | #2 |
| Matthew Paul Thomas (mpt) wrote | #3 |
| Martin Pitt (pitti) wrote | #4 |
We need to revive the old concept of "crash db consolidation" and run that daily, in addition to updating the bug status when we run into the next master bug. We should implement this in a more clever way than iterating through all existing master bugs, such as querying for all "apport-crash" and "daisy-created" tagged bugs which changed since the last run (modified_since in the searchTasks argument).