Packages file(s)? for wily out of date
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
Fix Released
|
Undecided
|
Unassigned | ||
ddeb-retriever |
Invalid
|
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 (community): Approve
-
Diff: 38 lines (+15/-3)1 file modifiedbackends/packaging-apt-dpkg.py (+15/-3)
Changed in ddeb-retriever: | |
status: | New → Invalid |
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.