USN notification service is failing to report affected binary packages if primed-stage-packages is present but empty in manifest.yaml and dpkg.list was used to fake stage packages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
review-tools |
Fix Released
|
High
|
Emilia Torino |
Bug Description
When the support for reading snaps stage-packages from the primed-
This is correct in general scenarios, but is failing under special scenarios such as the core snap, where the primed-
$ 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 properly parsing binary names from a dpkg.list file which also affects this result: https:/
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)
description: | updated |
summary: |
USN notification service is failing to report affected binary packages - if primed-stage-packages is present but empty in manifest.yaml but - dpkg.list should be used to fake stage packages + if primed-stage-packages is present but empty in manifest.yaml and + dpkg.list was used to fake stage packages |
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 |