Issue a warning when building a snap that stages another snap built on a different base
Metadata
Current evaluation
Feature request (c/p from forum) to warn at build time when a part stages a snap built on a different base, which causes glibc/AppArmor denials at runtime. Only a bot comment linking internal ticket CRAFT-3126; no maintainer triage.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and no maintainer response — the only comment is the autogenerated sync bot note (2024-07-16) pointing at internal ticket CRAFT-3126, so it has never been triaged. Repo inspection shows the feature is still absent: `stage-snaps` appears only in snapcraft/parts/grammar.py and colcon_plugin.py, and no code compares a staged snap's base against the project base (e.g. snapcraft/services/project.py only validates ua-services/license against the base), and git log has no commit adding such a warning. The request is well-scoped with a concrete reproducer (core18 app + node from 10/stable track) and a chosen behavior (warn, not error), but real complexity remains: staging/unpacking lives in craft-parts, so the snap's base must be surfaced, and edge cases (base: bare, core24 components, build-snaps vs stage-snaps, warning noise) are unspecified.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
9
Complexity:
55
Confidence:
62
Actionability:
64
|
needs triage | Feature request (c/p from forum) to warn at build time when a part stages a snap built on a different base, which causes glibc/AppArmor denials at runtime. Only a bot comment linking internal ticket CRAFT-3126; no maintainer triage. | |
| qwen/qwen3.6-35b-a3b |
Impact:
70
Quick Win:
29
Complexity:
40
Confidence:
70
Actionability:
70
|
needs triage | Feature request to warn when staging a snap with a different base, which can cause apparmor denials and runtime failures | |
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
20
Staleness:
75
Complexity:
55
Confidence:
70
Support Request:
10
|
needs triage | Request to add a build-time warning when a snap stages another snap built on a different base, preventing runtime AppArmor denials. Open, unlabelled, no maintainer response; only an automated Jira sync comment. Inactive for ~18 months. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
20
Confidence:
80
Support Request:
10
|
needs triage | Request to add a build-time warning when staging a snap with a mismatched base, preventing runtime AppArmor denials and crashes. Currently unlabelled and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
35
Confidence:
90
Support Request:
10
|
needs triage | Feature request to warn or fail builds when staging a snap with a different base, preventing runtime AppArmor and library errors. Currently unlabelled and untriaged. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.