models/project.py: do not check for base when build-base: devel
Metadata
Current evaluation
Rejected. Maintainers kept the default base validation for all crafts. They advised overriding _validate_devel_base in snapcraft to support the gadget snap use case instead.
Suggested action: —
No scores available.
Issue body
To be able to build pc snap, we have to set the base to point to the upcoming base, in the present case `core26`, while using `build-base: devel`.
This is how we worked on core24 before its release. Verifying the base matches the build base breaks it.
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `make lint && make test`?
- [ ] Have you added an entry to the changelog (`docs/reference/changelog.rst`)?
---
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Rejected. Maintainers kept the default base validation for all crafts. They advised overriding _validate_devel_base in snapcraft to support the gadget snap use case instead. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected. Maintainers declined the change to preserve default validation across all crafts. Instead, they recommended overriding _validate_devel_base in snapcraft to handle the specific use case. Linked to related PR #5496. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1839604 build-base seems broken | snapcraft (launchpad) | open | Seven-year-old question about snapcraft rejecting 'base: bare' with 'build-base: core18' via a confusing validation error. No maintainer response; validation was rewritten in snapcraft 8.x, where build-base is now required for bare bases, so the reported combination is now valid. | |
| #4721 feat: validate devel bases with craft-application | snapcraft | closed | Superseded by pull request #4796. The changes to validate devel bases with craft-application and remove the build-base: devel requirement for core24 snaps were closed in favor of the newer implementation. | |
| #4562 Validity of `base` is not checked when using `--destructive-mode` | snapcraft | closed | Resolved in snapcraft 8.1 via craft-application 2.0 and canonical/craft-application#263. Base validity is now enforced during destructive-mode builds, blocking invalid or unreleased bases. |