primed-stage-packages in base snaps manifest is empty
Metadata
Current evaluation
Closed as not a bug: live-built core snaps bypass Snapcraft part staging, so primed-stage-packages is intentionally empty while their staged debs remain listed in dpkg.list.
Resolution: closed not a bug
Reason: In the closing maintainer comment on 2021-04-09, Sergiusens explained that these debs were not staged and primed through a Snapcraft part. He noted that supporting them would require a new feature or building core bases entirely with Snapcraft.
Evaluated by: mr-cal-bot
No scores available.
Issue body
we have plenty of tools to parse manifest.yaml like:
https://forum.snapcraft.io/t/checking-ubuntu-security-notices-for-a-snap/23410
as well as the https://sources.iotdevice.io/ service (i'm sure there are more)
the core, core18 and core20 snaps are built by invoking live-build outside of snapcraft and while the core snaps all ship the package list of staged debs inside them as /usr/share/snappy/dpkg.list, these debs do not show up in manifest.yaml, making it hard to use any standard tools parsing the manifest.yaml file.
core snaps should be special cased in snapcraft so that the content of dpkg.list can show up as primed-stage-packages in manifest.yaml
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Closed as not a bug: live-built core snaps bypass Snapcraft part staging, so primed-stage-packages is intentionally empty while their staged debs remain listed in dpkg.list. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as not a bug: core snaps are live-built and publish dpkg.list, while primed-stage-packages intentionally covers packages staged by Snapcraft parts. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without implementation after inactivity; populating base snaps' primed-stage-packages from dpkg.list was abandoned in Launchpad bug #1923189. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The request to populate primed-stage-packages in base snaps manifest from dpkg.list was abandoned. No snapcraft changes were made. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
9
Staleness:
95
Complexity:
40
Confidence:
72
Support Request:
10
|
close stale | Core snaps (core, core18, core20) built via live-build outside snapcraft have empty primed-stage-packages in manifest.yaml. Request to special-case core snaps so dpkg.list content appears. Issue is 5+ years old with zero comments, no labels, and core snaps are now deprecated in snapcraft. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
80
Support Request:
10
|
close stale | Core snaps manifest.yaml lacks primed-stage-packages despite dpkg.list containing staged debs. Issue is 5+ years old with no maintainer response or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
70
Confidence:
90
Support Request:
10
|
close stale | Base snaps manifest.yaml lacks primed-stage-packages because dpkg.list is not parsed. Open for over 5 years with no maintainer response or updates. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
65
Confidence:
85
Support Request:
10
|
close stale | Base snaps (core, core18, core20) have an empty primed-stage-packages field in manifest.yaml despite shipping dpkg.list. No maintainer response in over 5 years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5552 `primed-stage-packages` isn't in manifest.yaml when using override-prime | snapcraft | open | override-prime leaves primed-stage-packages empty in build manifests on core22+ because craft-parts #1122 does not track scriptlet-primed files; still reproduced on Launchpad. |