snapcraft init doesn't fail if there is a .snapcraft.yaml file
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without resolution. The snapcraft init command remains unchanged and still creates snapcraft.yaml when .snapcraft.yaml exists, indicating the bug was abandoned or superseded by newer project changes.
Suggested action: —
No scores available.
Issue body
$ touch .snapcraft.yaml
$ snapcraft init
Created snapcraft.yaml.
Edit the file to your liking or run `snapcraft` to get started
Instead of creating the snapcraft.yaml, it should fail with:
.snapcraft.yaml already exists!
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The snapcraft init command remains unchanged and still creates snapcraft.yaml when .snapcraft.yaml exists, indicating the bug was abandoned or superseded by newer project changes. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The issue requested snapcraft init to fail when .snapcraft.yaml already exists. No resolution or merge details were provided. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The snapcraft init command should detect an existing .snapcraft.yaml file and exit with an error instead of creating snapcraft.yaml. No fix or pull request was submitted. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #1448 snapcraft build using manifest.yaml | snapcraft | closed | Closed without discussion or comments. The issue appears abandoned or superseded by newer snapcraft build workflows. No resolution or merge details were recorded. | |
| #1660880 snapcraft init doesn't finish the yaml with an empty line | snapcraft (launchpad) | closed | Closed. The missing trailing newline in generated snapcraft.yaml was fixed. The update ensures generated files adhere to standard formatting conventions. | |
| #1990550 snapcraft init creates boilerplate which opaquely fails to build by default | snapcraft (launchpad) | closed | Closed without resolution. The report recommended updating snapcraft init to default to core22 instead of core20, preventing opaque build failures and CLI mismatches. No fix or pull request was submitted, leaving the request abandoned. | |
| #1803776 snapcraft init missing a base | snapcraft (launchpad) | closed | Closed without resolution. The base requirement for snapcraft init was later implemented in subsequent releases, superseding this report. | |
| #1939713 snapcraft init create base: core18 snap | snapcraft (launchpad) | closed | Closed without direct resolution, likely abandoned due to inactivity. Subsequent Snapcraft releases updated the init default to core20 and core22, effectively resolving the reported behavior. | |
| #1567041 snapcraft init creates icon entry | snapcraft (launchpad) | closed | Closed without resolution. The request to prevent snapcraft init from generating an icon entry was abandoned after over 3800 days with no associated pull requests or follow-up comments. | |
| #4300 snapcraft fails for python projects if there is no setup.py | snapcraft | closed | Closed as stale due to inactivity. Maintainers identified the failure as a missing entry_points or scripts configuration in pyproject.toml, not a snapcraft bug. | |
| #1795780 Snapcraft complains about "snapcraft.yaml~" in snap/ dir | snapcraft (launchpad) | open | Snapcraft warns about editor backup files like snapcraft.yaml~ in the snap/ directory, creating noise that can mask real problems. The issue has been open and unaddressed for 2890 days with no maintainer response. | |
| #4 snapcraft.yaml needs to make all stages dirty (was: the can't add file without recreating entire package) | snapcraft | closed | Closed without a direct fix. The maintainer noted snapcraft failed to invalidate stages when snapcraft.yaml changed, requiring an internal --force. Tracking was moved back to Launchpad, superseding this GitHub issue. |