USN notification service is failing to detect affected binary packages if dpkg.list file is present and binary contains arch specifier
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
review-tools |
Fix Released
|
High
|
Emilia Torino |
Bug Description
Some special snaps could ship a dpkg.list file (e.g. core snaps). If that's the case, review-tools adds each of the binaries present in such file, as stage-packages in a "faked-
Under certain circumstances, the binary name in the dpkg.list entry could contain an architecture specifier as part of the binary name (e.g liblz4-1:amd64). The review-tools is not considering such situation and is setting the binary name as liblz4-1:amd64 when it should be liblz4-1 only.
This issue makes the the USN notification service to fail detect USNs affecting such binary packages as it uses binary names to compare.
$ review-
{
"core18": {
"2066": {}
}
}
With 2021/05/27 USN DB it should report:
{
"isc-
"4969-1"
],
"liblz4-1": [
"4968-1"
]
}
There is a related bug which is related to the presence of an empty primed-
Related branches
- Alex Murray: Approve
-
Diff: 631 lines (+414/-22)6 files modifiedreviewtools/available.py (+13/-5)
reviewtools/store.py (+19/-14)
reviewtools/tests/test_available.py (+7/-3)
tests/test-updates-available.sh (+9/-0)
tests/test-updates-available.sh.expected (+103/-0)
tests/test.sh.expected (+263/-0)
summary: |
- USN notification service if failing to detect affected binary packages + USN notification service is failing to detect affected binary packages if dpkg.list file is present and binary contains arch specifier |
description: | updated |
Changed in review-tools: | |
assignee: | nobody → Emilia Torino (emitorino) |
status: | New → Confirmed |
Changed in review-tools: | |
status: | Confirmed → Fix Released |
importance: | Undecided → High |