Cannot retrace both crashes from -proposed and those not from it

[Evan]

If we enable both precise and precise-proposed in our apt sources for the retracers, we will not be able to retrace any crash from a system where proposed is not enabled, but a newer version of the package that crashed or one of its dependencies exists in precise-proposed.

This is because the sandbox building logic only looks at the current package in apt, and the version from precise-proposed will always be newer. Instead, it should try to find debug symbol packages for the versions in Package and Dependencies.

[Evan (ev)]

https://pastebin.canonical.com/87608/ is an example of this

[Brian Murray (brian-murray)]

This was fixed a while ago.

2.13.2 (2014-01-27)
-------------------
 * Fix crash if systemd cgroup is unreadable in /sys, such as in containers.
   (LP: #1270783)
 * apt/dpkg: Also consider Contents.gz from updates/security/proposed pockets,
   so that e. g. apport-retrace works for crash reports with files that are new
   in those. Thanks to Brian Murray for the initial patch. (LP: #1271258)
 * Only drop internal/private keys (starting with '_') from uploading to the
   crash DB and from the UI report views, but not already when updating the
   report. (LP: #1272505)
 * data/apport: Fix stdout/stderr initialization of the error log, don't close
   the original fd after dup2'ing as it is usually already fd 1. This makes
   Apport work with Python 3.4. (LP: #1272355)
 * Adjust report tests to work with Python 3.4 (LP: #1272355)