stage-packages for classic snaps silently drop core20 snap debs
Metadata
Current evaluation
Classic snaps using stage-packages lose dependencies already present in core20 because base-package filtering silently omits them; a bare-base workaround exists, but the underlying filtering bug remains open.
Suggested action: keep open
Reason: The maintainer provided base: bare with build-base: core20 as a workaround, but also explicitly stated, "We have a bug to fix," and said better logging would show skipped packages. The report includes a concrete deb and stage-packages reproduction with expected-versus-actual behavior, so the underlying valid bug remains actionable despite its age.
Evaluated by: mr-cal-bot
Impact:
58
Quick Win:
25
Complexity:
45
Confidence:
92
Actionability:
78
Issue body
I'm updating the git-ubuntu classic snap to be based on core20. In doing this, I'm building a deb, and then installing it using stage-packages. See bug 1918968 for a deeper explanation of this use case.
Expected: "stage-packages: [git-ubuntu]" ships all required dependencies in the snap.
Actual: packages already in the core20 snap are elided from the effective "stage-packages" list. Since this classic snap cannot make use of what is in the core20 snap safely, the result is a snap with missing dependencies.
Workaround: explicitly specify every single required dependency, recursively, that is also present in the core20 snap.
The list of packages to use for the workaround is tedious to determine.
To fix, maybe the eliding behaviour should be disabled for a classic snap, or able to be turned off with an option.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
25
Complexity:
45
Confidence:
92
Actionability:
78
|
keep open | Classic snaps using stage-packages lose dependencies already present in core20 because base-package filtering silently omits them; a bare-base workaround exists, but the underlying filtering bug remains open. | |
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
24
Complexity:
42
Confidence:
90
Actionability:
86
|
close resolved | Classic snaps lost staged core20 dependencies due to base-package filtering; supported `base: bare` with `build-base: core20` now avoids the runtime base dependency. | |
| qwen/qwen3.6-35b-a3b |
Impact:
50
Quick Win:
24
Complexity:
30
Confidence:
60
Actionability:
70
|
keep open | Classic snaps using stage-packages silently drop packages present in the base snap (e.g. core20), causing missing dependencies. Issue open ~5 years with no maintainer response. | |
| qwen/qwen3.8-27b |
Impact:
55
Quick Win:
19
Staleness:
95
Complexity:
65
Confidence:
60
Support Request:
10
|
needs triage | Classic snaps using stage-packages silently drop dependencies already present in the core20 base, causing missing dependencies at runtime. Open 5+ years with zero maintainer interaction; workaround is to manually list every transitive dependency. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
85
Support Request:
10
|
close stale | Classic snaps using stage-packages silently drop dependencies already present in the core20 base, causing missing dependencies. Issue is 5+ years old with zero maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
60
Confidence:
90
Support Request:
10
|
close stale | Classic snaps using stage-packages silently drop dependencies already in the core20 base, causing missing runtime deps. Issue is untriaged with no maintainer activity in nearly five years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
55
Confidence:
85
Support Request:
10
|
close stale | Classic snap stage-packages silently drops packages present in the core20 base, causing missing dependencies. No maintainer response in over 5 years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1918968
(confidence 95%)
The issue body explicitly references bug 1918968 as providing deeper context for the classic-snap/core20 use case.
Related issues
No related issues found above the similarity threshold.