packaging-apt-dpkg.py's _search_contents function guesses sources in use
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
Triaged
|
Undecided
|
Unassigned |
Bug Description
The _search_contents function in packaging-
"for pocket in ['-updates', '-security', '-proposed', '']:"
This ended up preferring the Contents.gz file from -proposed over the one in the release pocket for artful. This caused a bad retrace as seen in bug 1712880 because libgjs0g, from -proposed, was used for the retrace instead of libgjs0f which was installed on the crashing system. I modified the list of pockets so that it now has '-proposed' last, given that most crashes won't be from users with '-proposed' enabled.
However, _search_contents is still guessing at this point as it is not aware of which pockets the system which experienced the crash had enabled. FWIW, get_file_package calls _search_contents and is called by needed_
summary: |
- packaging-apt-dpkg.py's _search_contents function guess sources in use + packaging-apt-dpkg.py's _search_contents function guesses sources in use |
Changed in apport: | |
status: | New → Triaged |
tags: | added: id-599f2f2e1a4034a1018fd25a |