Cannot build charm when base is Questing and build-base is devel
Metadata
Current evaluation
Build with base ubuntu@25.10 and build-base ubuntu@devel fails with 'Couldn't get EOL data for devel' in charmcraft 4.0.1; fixed in craft-providers 3.2.0 by skipping EOL checks for devel.
Suggested action: close resolved
Reason: The error originates in craft-providers' `_is_eol`, which now returns early for `BuilddBaseAlias.DEVEL`; craft-providers changelog 3.2.0 lists 'Do not check whether the "devel" base is end-of-life', and current charmcraft requires craft-providers>=3.7.1, so the reported failure is resolved.
Evaluated by: mr-cal-bot
Impact:
45
Quick Win:
29
Complexity:
15
Confidence:
90
Actionability:
75
Issue body
### Check existing issues
- [x] I've verified that this bug isn't described by any existing issues.
### Bug description
Hello,
When trying to build a charm with base = `ubuntu@25.10` and build-base = `ubuntu@devel`, I get the following error when running `charmcraft pack`:
```
The development build-base should only be used for testing purposes, as its contents are bound to change with the opening of new Ubuntu releases, suddenly and without warning.
Launching managed ubuntu devel instance...
Creating new instance from remote
Creating new base instance from remote
Couldn't get EOL data for devel.
```
This is when using charmcraft 4.0.1.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest |
Impact:
45
Quick Win:
29
Complexity:
15
Confidence:
90
Actionability:
75
|
close resolved | Build with base ubuntu@25.10 and build-base ubuntu@devel fails with 'Couldn't get EOL data for devel' in charmcraft 4.0.1; fixed in craft-providers 3.2.0 by skipping EOL checks for devel. | |
| qwen/qwen3.6-35b-a3b |
Impact:
20
Quick Win:
13
Complexity:
20
Confidence:
70
Actionability:
80
|
close resolved | Build fails with 'Couldn't get EOL data for devel' when using base=ubuntu@25.10 and build-base=ubuntu@devel. The error originates from craft-application's EOL handling for devel bases. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18
Staleness:
75
Complexity:
55
Confidence:
55
Support Request:
10
|
needs triage | charmcraft pack fails with 'Couldn't get EOL data for devel' when base=ubuntu@25.10 and build-base=ubuntu@devel on charmcraft 4.0.1. Unlabelled, no maintainer activity in 262 days; devel-base support has since been expanded in later releases. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
80
Complexity:
25
Confidence:
90
Support Request:
60
|
needs triage | Untriaged report of a build failure when using ubuntu@devel as build-base with ubuntu@25.10 base. No maintainer response or labels after ~7 months. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
15
Confidence:
80
Support Request:
85
|
close not a bug | User reports charmcraft pack fails with an EOL data error when using ubuntu@25.10 base and ubuntu@devel build-base. Unlabelled, zero comments, inactive for ~7 months. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
25
Confidence:
50
Support Request:
20
|
needs triage | Charmcraft pack fails with an EOL data fetch error when using ubuntu@25.10 base and ubuntu@devel build-base. Unlabeled, no maintainer response, inactive for ~7 months. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-providers#850
(confidence 90%)
Commit 714c8dcb introduced the 'Skipping EOL check for base devel' path and craft-providers 3.2.0 changelog lists the devel EOL fix.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1267 Can't build charm targeted at the current development release: `Skipping 'bases[8].build-on[0]': channel 'devel' does not match host '23.10'.` | charmcraft | closed | Development-release builds stopped being rejected in Charmcraft 3; platform support landed in PR #1554 (commit e3de0a46), and the maintainer closed the report as fixed. |