| 2021-05-28 22:34:32 |
Emilia Torino |
bug |
|
|
added bug |
| 2021-05-28 22:35:26 |
Emilia Torino |
description |
When the support for reading snaps stage-packages from the primed-stage-packages manifest key was added, it was considered that if that the primed-stage-packages key was present, it should take precedence over all stage-packages of each part.
This is correct in general scenarios, but is failing under special scenarios such as the core snap, where the primed-stage-packages key is present in the snap manifest but is always empty. |
When the support for reading snaps stage-packages from the primed-stage-packages manifest key was added, it was considered that if that the primed-stage-packages key was present, the packages inside this key should take precedence over all stage-packages of each part.
This is correct in general scenarios, but is failing under special scenarios such as the core snap, where the primed-stage-packages key is present in the snap manifest but is always empty. |
|
| 2021-05-28 22:35:57 |
Emilia Torino |
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 |
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 |
|
| 2021-05-28 22:37:23 |
Emilia Torino |
description |
When the support for reading snaps stage-packages from the primed-stage-packages manifest key was added, it was considered that if that the primed-stage-packages key was present, the packages inside this key should take precedence over all stage-packages of each part.
This is correct in general scenarios, but is failing under special scenarios such as the core snap, where the primed-stage-packages key is present in the snap manifest but is always empty. |
When the support for reading snaps stage-packages from the primed-stage-packages manifest key was added, it was considered that if that the primed-stage-packages key was present, the packages inside this key should take precedence over all stage-packages of each part.
This is correct in general scenarios, but is failing under special scenarios such as the core snap, where the primed-stage-packages key is present in the snap manifest but is always empty.
$ review-tools.check-notices core18_2066.snap
{
"core18": {
"2066": {}
}
}
With 2021/05/27 USN DB it should report:
{
"isc-dhcp-client": [
"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://bugs.launchpad.net/review-tools/+bug/1930105. Both bugs need to be resolved together for this result to be properly provided. |
|
| 2021-05-28 22:37:30 |
Emilia Torino |
review-tools: assignee |
|
Emilia Torino (emitorino) |
|
| 2021-05-28 22:37:45 |
Emilia Torino |
review-tools: status |
New |
Confirmed |
|
| 2021-05-28 22:54:20 |
Emilia Torino |
merge proposal linked |
|
https://code.launchpad.net/~emitorino/review-tools/+git/review-tools/+merge/403485 |
|
| 2021-06-01 18:48:55 |
Emilia Torino |
review-tools: status |
Confirmed |
Fix Released |
|
| 2021-06-01 18:49:04 |
Emilia Torino |
review-tools: importance |
Undecided |
High |
|
