Merge lp:~shnatsel/apport/dont-break-report-if-dbgsym-is-outdated into lp:~apport-hackers/apport/trunk
Status: | Rejected |
---|---|
Rejected by: | Martin Pitt |
Proposed branch: | lp:~shnatsel/apport/dont-break-report-if-dbgsym-is-outdated |
Merge into: | lp:~apport-hackers/apport/trunk |
Diff against target: |
28 lines (+4/-3) 2 files modified
backends/packaging-apt-dpkg.py (+3/-2) po/apport.pot (+1/-1) |
To merge this branch: | bzr merge lp:~shnatsel/apport/dont-break-report-if-dbgsym-is-outdated |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Pitt (community) | Disapprove | ||
Review via email: mp+132761@code.launchpad.net |
Description of the change
It seems that ddebs.ubuntu.com packages for Precise are outdated as of late. Apport doesn't handle such cases well; on encountering an outdated dbgsym package crash-digger blames the reporter and removes the core dump from the report, thus making the report unretraceable (bug 1069401).
This branch fixes this; instead of breaking the report it makes apport-retrace exit with a transient error code.
As opposed to the current version, this one does not list all the outdated dbgsym packages; instead it prints only the first version mismatch, adds "and possibly others" and exits with a transient error. Perhaps this can be improved later. The change involved a string change but I didn't update the .pot file because I don't know how to regenerate it.
Unmerged revisions
- 2523. By Sergey "Shnatsel" Davidoff
-
Clarified error message on outdated dbgsym errors. I should update po/apport.pot too but I don't know how to do it.
- 2522. By Sergey "Shnatsel" Davidoff
-
exit with an error instead of borking the report upon encountering outdated dbgsym packages
I'm not that keen on this, to be honest. Due to the brittle nature of ddebs.u.c. there is little chance of ddebs.u.c. "fixing itself" in a lot of cases, so you'd just end up with a lot of retracer aborts and other reports piling up.
Also, having one outdated dbsym is often not the end of the world: in many cases the crash doesn't even go through that one library or extra dependency, so it retraces perfectly well.
We are currently planning to enable ddeb support on Launchpad proper, so that we can directly fetch the correct ddeb version from the librarian. That way we'll never have outdated ddebs any more, and confusions like this cannot happen any more.