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

Bug #1930106 reported by Emilia Torino
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
review-tools
High
Emilia Torino

Bug 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.

$ 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.

Related branches

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers