Packages file(s)? for wily out of date
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Apport |
Undecided
|
Unassigned | ||
| | ddeb-retriever |
Undecided
|
Unassigned | ||
Bug Description
Seb pinged me about a retrace that failed:
https:/
Reviewing the retracer log files I found the following:
./e-t-retracer-
./e-t-retracer-
However, as Seb mentioned the ddebs do exist:
http://
Looking at the Packages file for wily/main/
This seems sort of familiar, and I think it has to do with the source package being in universe and the binary being in main.
Related branches
- Martin Pitt: Approve on 2015-09-30
-
Diff: 38 lines (+15/-3)1 file modifiedbackends/packaging-apt-dpkg.py (+15/-3)
| Brian Murray (brian-murray) wrote : | #1 |
| Brian Murray (brian-murray) wrote : | #2 |
Looking at the apport code some more, I think we could prevent this being a problem and have apport just check Launchpad if the corresponding -dbgsym package is not found in the cache.
| Martin Pitt (pitti) wrote : | #3 |
Brian's Apport fix landed upstream in trunk r3014.
| Changed in apport: | |
| status: | New → Fix Released |

apport will not check Launchpad for a package that it does not find in the package cache from packaging- apt-dpkg. py we have:
try:
dbgsym_pkg = pkg + '-dbgsym'
dbgsym = cache[dbgsym_pkg]
....
except KeyError:
obsolete += 'no debug symbol package found for %s\n' % pkg
So because the Packages file is out of date / incorrect apport-retrace is running into issues.