Cleaning breaks tried snap
Metadata
Current evaluation
Fixed by merged PR snapcore/snapcraft#2143 (commit fa846914a), preserving the priming area for tried snaps so snapcraft clean no longer breaks snap try.
Resolution: closed resolved
Reason: Commit fa846914a, associated with PR snapcore/snapcraft#2143, changed lifecycle cleanup to retain the priming area when the snap is being tried. This directly addresses the broken snap try state reported in the issue.
Evaluated by: mr-cal-bot
No scores available.
Issue body
There's a disconnect between snapd and the snapcraft CLI when it comes to `snap try`. Snapcraft doesn't know that a given snap is being tried, which means when one runs `snapcraft clean` is completely breaks the tried snap, requiring the user to `snap try` again. This should be a smooth experience.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR snapcore/snapcraft#2143 (commit fa846914a), preserving the priming area for tried snaps so snapcraft clean no longer breaks snap try. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #2143 (commit fa846914a), preserving an active snap try priming area during snapcraft clean so the tried snap is not broken. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by canonical/snapcraft#2143 (commit fa846914a), which stops snapcraft clean from deleting the priming area of a snap installed via snap try. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The snapcraft CLI and snapd disconnect causing snapcraft clean to break snap try states remains unfixed due to inactivity. | |
| qwen/qwen3.6-35b-a3b | — | — | snapcraft clean breaks snap try setups due to missing state tracking. The report was closed without discussion or a fix, indicating the issue was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments or resolution, indicating the issue was likely abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The report describes snapcraft clean breaking snap try snaps due to a snapd-snapcraft disconnect. With zero comments and no fix, the issue was abandoned. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2143
(confidence 99%)
Merged as commit fa846914a with the title "lifecycle: don't clean priming area if the snap is being tried".
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2143 lifecycle: don't clean priming area if the snap is being tried | snapcraft | merged | Merged PR #2143, fixing snapcraft clean to preserve a priming area used by snap try and avoid requiring another snap try after re-priming. | |
| #1805212 snapcraft try (integrated with build environments) | snapcraft (launchpad) | closed | Merged snapcore/snapcraft#2524 as ec579eaa1, adding snapcraft try to expose the prime directory transparently in build environments. |