← Back to issue list

Snapcraft build should fail if using classic and base at the same time

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1808514
Type
issue
State
closed
Author
~igorljubuncic-deactivatedaccount
Labels
—
Created
Updated
Closed

Current evaluation

Closed as expired after 60 days without activity; no fix or PR addressed rejecting builds that combine base with classic confinement.

Resolution: closed stale

Reason: @janitor closed the issue as expired on 2019-03-26 after no activity for 60 days. No resolving commit or PR was linked.

Evaluated by: mr-cal-bot

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
stealth/space-bunny-alpha — closed stale Closed as expired after 60 days without activity; no fix or PR addressed rejecting builds that combine base with classic confinement.
stealth/space-bunny-alpha — closed stale Closed as stale after 60 days without activity; no classic/base validation or resolving PR was identified.
stealth/space-bunny-alpha — closed stale Closed without a documented fix or explanation; searches found no resolving commit or related item for the requested classic/base validation.
qwen/qwen3.6-35b-a3b — — Closed without implementation due to inactivity. The requested build validation for incompatible base and confinement options was never added.
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

Date Change
created

Related issues

Issue Project State Summary Similarity
#1791938 Support classic when using bases snapcraft (launchpad) closed Classic confinement with base was implemented by merged PR snapcore/snapcraft#2261, commit 8096c17b3, which injects the base into classic builds.
72%