removing parts should clean stage and prime… stages?
Metadata
Current evaluation
Removing a part leaves its prior files in stage/prime and packages them; the report has a clear reproducer and maintainer confirmation, but no fix reference is recorded.
Suggested action: keep open
Reason: The body provides exact Multipass commit and PR revisions demonstrating that removing libvirt leaves its contents in the snap. Sergiusens confirmed that state belonging to parts no longer defined in snapcraft.yaml should be cleaned, establishing a valid bug, but no resolving commit or PR was found.
Evaluated by: mr-cal-bot
Impact:
62
Quick Win:
31
Complexity:
44
Confidence:
78
Actionability:
88
Issue body
Steps to reproduce:
- build https://github.com/CanonicalLtd/multipass/commit/7f4e951f98f492832c100ca26208d087a4a5ab74
- build https://github.com/CanonicalLtd/multipass/pull/850 which removes the `libvirt` part
Expected:
- the snap does not have the `libvirt` part's contents
Current:
- the snap includes the old `libvirt` part's contents
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
62
Quick Win:
31
Complexity:
44
Confidence:
78
Actionability:
88
|
keep open | Removing a part leaves its prior files in stage/prime and packages them; the report has a clear reproducer and maintainer confirmation, but no fix reference is recorded. | |
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
28
Complexity:
48
Confidence:
90
Actionability:
92
|
keep open | Removing a part leaves its previously staged and primed files in incremental builds; the Multipass reproducer is pinned, and a maintainer confirmed stale part state should be cleaned. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
16
Complexity:
50
Confidence:
70
Actionability:
80
|
needs triage | When a part is removed from snapcraft.yaml, its contents remain in stage and prime directories instead of being cleaned up. Issue is open with no maintainer engagement after 7 years. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18
Staleness:
95
Complexity:
40
Confidence:
55
Support Request:
10
|
close stale | Bug report from 2017: removing a part from snapcraft.yaml does not clean its contents from stage/prime, so the built snap still includes the removed part's files. No labels, no comments, no maintainer activity in ~7 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
10
|
close stale | Reports that removing a snapcraft part fails to clean stage and prime directories, leaving stale contents in the built snap. Issue is 7 years old with no maintainer response or activity. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Bug in snapcraft where removing a part from the configuration fails to clean previously staged and primed contents, leaving old artifacts in the final snap. Issue remains open with no maintainer response or comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
85
Support Request:
5
|
close stale | Bug report stating that removing a snapcraft part fails to clean the stage and prime directories, leaving old contents in the built snap. Open for over 7 years with no maintainer response or activity. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.