in order to clean, the snapcraft.yaml has to be valid and the parts cache up-to-date
Metadata
Current evaluation
Abandoned without resolution. The reported limitation where snapcraft clean fails on invalid YAML or outdated cache remains unaddressed, as no fix or pull request was provided.
Suggested action: —
No scores available.
Issue body
When you try to clean up the snapcraft workspace, it will fail if the yaml file is not valid or if you are using a wiki part and haven't run snapcraft update.
This happens because in order to clean up a step or a part, parsing the yaml is necessary. But it shouldn't be necessary to parse it if we just want to clean up everything. It should just delete the dirs even if the yaml is not valid.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned without resolution. The reported limitation where snapcraft clean fails on invalid YAML or outdated cache remains unaddressed, as no fix or pull request was provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Cleanup failures caused by invalid YAML or stale cache were not addressed. The request to bypass YAML parsing during workspace deletion was closed without resolution, indicating the enhancement was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Requested snapcraft clean behavior bypassing YAML validation was closed without resolution. No fix or pull request was implemented, indicating the report was abandoned due to inactivity. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1777501 snapcraft clean should require a minimal valid yaml with at least a name | snapcraft (launchpad) | closed | Abandoned without a recorded fix. The requirement to validate minimal YAML before snapcraft clean was never implemented. | |
| #1869542 snapcraft unable to find snap/snapcraft.yaml file | snapcraft (launchpad) | open | snapcraft 3.11 (2019) loses snap/snapcraft.yaml after a few builds and drops to the VM shell; workaround is snapcraft clean. 6+ years old, no labels, no maintainer comments, tied to a long-superseded build environment. | |
| #1615060 snapcraft clean is incomplete | snapcraft (launchpad) | closed | Reporting that snapcraft clean skips local .snap files was closed without comments or resolution, indicating the report was abandoned or left unresolved. | |
| #1608032 snapcraft crashes with useless message on bad YAML | snapcraft (launchpad) | closed | Abandoned. Snapcraft crashed with an unhelpful error on invalid YAML. No fix or follow-up was provided. | |
| #1799925 snapcraft gives conflicting advice for cleaning parts | snapcraft (launchpad) | closed | Closed without a fix. Snapcraft incorrectly advised running snapcraft clean with part and step flags, which were unsupported. The author worked around it with a full clean. The report appears abandoned or superseded by later updates. | |
| #1561328 cleaning a step on a dir built with an old snapcraft doesn't mention that a full clean is needed too | snapcraft (launchpad) | closed | Closed without resolution. The missing error guidance for cleaning steps on legacy snapcraft builds was not fixed. Issue appears abandoned due to age and zero comments. | |
| #1578170 Your first snap: snapcraft clean needed before second snapcraft stage | snapcraft (launchpad) | closed | Closed and abandoned without resolution. The issue highlights a documentation gap where the Ubuntu snap tutorial skips steps on re-runs unless snapcraft clean is run first. No fix or update was applied. |