Mechanism to handle/promote 'devel' bases
Metadata
Current evaluation
Implemented centralized validation for mandatory upstream devel build bases in merged PR #302 (commit aeae554e), avoiding duplicated application logic.
Resolution: closed resolved
Reason: PR #302 was merged as commit aeae554e, adding Craft-wide validation of upstream devel build bases and addressing #298. PR #322 later reverted the related Project abstraction and _providers_base() portion.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
The current task that we have is to update all applications so that the 24.04 base no longer requires the `devel` build-base. The specifics of base description in each project is different but we should keep the core logic in craft-application. Like, a function that tells whether a given craft-provider's `Base` is mandatory "devel" or not.
Of course, we then need to update the applications to make use of this new code.
### Why it needs to get done
To avoid having to do the same work N times
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Implemented centralized validation for mandatory upstream devel build bases in merged PR #302 (commit aeae554e), avoiding duplicated application logic. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented in merged PR #302 as commit aeae554e, adding Craft-wide validation and handling for projects that require upstream devel build bases. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented in canonical/craft-application#302 (merged as aeae554e), adding Craft-wide validation of upstream devel build bases. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The proposal to centralize devel base validation in craft-application and update dependent projects was not addressed. Synced to Jira as CRAFT-2675, but no fix or follow-up pull request was created. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and synced to internal Jira ticket CRAFT-2675 without a technical resolution. The request to centralize devel base logic was abandoned, leaving the task unresolved. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-application#302
(confidence 100%)
Merged implementation for devel-base validation, recorded as commit aeae554e.
-
Related To:
canonical/craft-application#322
(confidence 90%)
Follow-up that reverted the Project abstraction and _providers_base() implementation.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1634 feat: validate devel bases with craft-application | charmcraft | closed | Closed unmerged as unnecessary after craft-application changed; generic devel-base validation had already landed upstream in canonical/craft-application#302. | |
| #302 feat!: validate devel bases | craft-application | merged | Merged PR #302 as aeae554e, adding Craft-wide validation that development bases use the matching devel build-base and fixing #298 (CRAFT-2675). | |
| #85 Allow `devel` in multi-base builds | craft-platforms | open | Enhancement to let `devel` build bases be used in charm multi-base `build-on` entries; design agreed with lengau, implementation PR #217 approved and green but still unmerged with open review threads. | |
| #532 feat: validate devel bases with craft-application | rockcraft | closed | Closed unmerged after #569 bumped craft-application to 2.7.0, delivering the devel-base validation planned in #532. |