Run YAML validity/schema linters before `snapcraft`
Metadata
Current evaluation
Feature request to run YAML/schema linters before snapcraft. Maintainer tigarmo triaged: missing `base:` and stale-build-dir errors are Snapcraft/craft-parts bugs, not bugs here; author conceded reticketing elsewhere.
Suggested action: close not a bug
Reason: The maintainer already triaged this as out-of-scope for this repo: tigarmo stated "The lack of `base` is, and should be, handled by Snapcraft itself... That second one is also a bug in Snapcraft, or craft-parts. I don't think it's a bug here," and the author replied "Maybe mods on the payroll can move or reticket it to the relevant repos?" The repo is a thin rock-definition repo (4 root files, one CI workflow, per-core recipe branches) whose README states "Every argument provided after the image name is forwarded to Snapcraft," so end-user project YAML is Snapcraft's concern, not this image's. The only in-repo sub-concern — hidden Snapcraft output — is now documented in the README ("To see `snapcraft` output, add flags: ... `; -v`") by commit 4538525 "docs: update repo location, branch links and verbosity (#61)". Note the request is a rough enhancement wish, not a defect report, so no code path in this repo is broken.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
22
Quick Win:
4
Complexity:
45
Confidence:
82
Actionability:
30
|
close not a bug | Feature request to run YAML/schema linters before snapcraft. Maintainer tigarmo triaged: missing `base:` and stale-build-dir errors are Snapcraft/craft-parts bugs, not bugs here; author conceded reticketing elsewhere. | |
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
6
Complexity:
40
Confidence:
78
Actionability:
38
|
close not a bug | Feature request to run YAML schema linters before `snapcraft` in rock builds; maintainer @tigarmo triaged it as a Snapcraft/craft-parts concern, not snapcraft-rocks. Left open, no reticket, idle 735 days. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
11
Complexity:
40
Confidence:
70
Actionability:
60
|
close not a bug | Feature request to add YAML validation before snapcraft runs; maintainer indicated it belongs in snapcraft/craft-parts | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14
Staleness:
85
Complexity:
30
Confidence:
80
Support Request:
15
|
close not a bug | Feature request to run YAML validity/schema linters before snapcraft to catch typos like a missing base: key. Maintainer redirected it to snapcraft/craft-parts as not a bug in this repo; reporter asked for a move, but it has sat unlabelled and inactive for ~23 months. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Feature request to add YAML linting before snapcraft execution. Maintainer redirected to Snapcraft/craft-parts over a year ago. No maintainer labels or follow-up. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
80
Support Request:
10
|
close not a bug | Suggests adding pre-snapcraft YAML validation to catch missing keys. Maintainer clarified validation belongs in Snapcraft itself and noted the issue is misplaced here, suggesting it be moved or reticketed. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft-rocks#57
(confidence 92%)
The originating report; issue summary confirms root cause was stale build dirs causing ConstructorError, with clearer diagnostics tracked via #58/#59.
-
Related To:
canonical/snapcraft-rocks#59
(confidence 78%)
Sibling open request to set SNAPCRAFT_BUILD_ENVIRONMENT=host for in-container troubleshooting, addressing the same 'errors are hard to see' complaint.
Related issues
No related issues found above the similarity threshold.