Snapcraft build should fail if using classic and base at the same time
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without comments or resolution. Likely abandoned due to inactivity, with no fix, merge, or official decision documented.
Suggested action: —
No scores available.
Issue body
When running snapcraft, it is possible to specify both base: core18 and confinement: strict in the same snapcraft.yaml. This may lead to unexpected behavior during runtime.
Snapcraft should check for the existence of these two declarations and not proceed with the build if both are specified (until full support for this is enabled).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments or resolution. Likely abandoned due to inactivity, with no fix, merge, or official decision documented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The requested validation to fail builds when incompatible base and confinement settings are specified was abandoned due to inactivity. No fix or merge occurred. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Requesting a build failure for conflicting snapcraft.yaml fields was closed without comments or resolution, indicating it was abandoned. No validation logic was implemented. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2067566 Snapcraft Github build fails when using experimental extensions | snapcraft (launchpad) | closed | Abandoned and closed without implementation. No comments or resolution details were provided, indicating the feature request was not prioritized. | |
| #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. | |
| #1984227 Snapcraft 7.1.1 does not build with core22 on riscv64 | snapcraft (launchpad) | closed | Closed without resolution or comments, effectively abandoned due to lack of activity or lack of riscv64 support. | |
| #1583718 snapcraft command doesn't include expected changes | snapcraft (launchpad) | closed | Closed without resolution or comments. The build caching bug was abandoned or superseded by later improvements, requiring manual cache cleaning as a workaround. | |
| #1973146 snapcraftctl build fails with message "expected string or bytes-like object" | snapcraft (launchpad) | closed | Closed without comments or resolution details. Likely abandoned due to inactivity. No fix was implemented or documented for the snapcraftctl build TypeError. | |
| #1570706 Snapcraft cleanbuild command doesn't work | snapcraft (launchpad) | closed | Closed without resolution, likely abandoned or superseded. The cleanbuild command failed due to LXC hash format incompatibility and container stop errors. | |
| #1794506 Changing the base doesn't change the build VM | snapcraft (launchpad) | closed | Abandoned. Snapcraft fails to update the build VM when the base changes. Closed without resolution or fix due to age and zero activity. No merge details provided. | |
| #4142 snapcraft remote-build exits with return code 0 even when some snaps failed to build for a given arch | snapcraft | closed | Closed without comments or resolution, indicating the request was abandoned. No official fix or merge details were provided. | |
| #1723965 snapcraft doesn't work | snapcraft (launchpad) | closed | Closed without resolution or comments, indicating abandonment. The reported snap command failure and GL driver errors remain unresolved. | |
| #1795501 Better base detection | snapcraft (launchpad) | closed | Abandoned. Closed without comments or resolution. The base detection failure in snapcraft build environments was not addressed. |