Cannot build charm when base is Questing and build-base is devel
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: No labels, no comments, no maintainer acknowledgement in 266 days, so it has not been triaged. The error string 'Couldn't get EOL data for devel' does not appear in the charmcraft repo (grep found no matches), indicating it originates in a dependency (craft-providers/craft-application), and later commits (#2321, #2478, #2524) added/expanded devel and 25.10 base support, so a maintainer needs to confirm whether it is still reproducible on a current release before closing.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18.0
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
25
Confidence:
75
Support Request:
10
|
needs triage | charmcraft pack fails with an EOL data error when using ubuntu@devel as build-base with a Questing base. Open for over six months with zero comments, it requires triage and assignment to address the build failure. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#2321
(confidence 60%)
feat: add plucky and questing as devel bases — directly touches the devel build-base path involved in this failure.
-
Related To:
canonical/charmcraft#2478
(confidence 55%)
feat: enable Ubuntu 25.10 and 26.04 as development bases — same base/devel area as the reported failure.
-
Related To:
canonical/charmcraft#2524
(confidence 50%)
feat(bases): mark 25.10 as stable and remove 24.10 — changes base handling around the reported ubuntu@25.10 base.
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 | Building charms with channel devel failed due to a host channel mismatch. The issue was closed as fixed in Charmcraft 3. | |
| #1789 Unable to build multi-base subordinate charms on 24.04 | charmcraft | closed | Reported build failures for multi-base subordinate charms under charmcraft 3's new syntax. Closed after a user identified PR #2054 as the resolution for configuring multiple bases. | |
| #792 22.10 - Failed to build charm for bases index '0'. | charmcraft | closed | Rejected as not a Charmcraft bug. The build fails due to a missing series field in metadata.yaml when using the legacy charm tool. The author acknowledged the config change and will coordinate with the Juju team. | |
| #639 Can't build charm: Failed to build charm for bases index '0' | charmcraft | closed | Resolved as a jinja2 and setuptools version conflict. Provided a charmcraft.yaml workaround to install or pin setuptools. A later user confirmed charmcraft clean followed by pack also fixed it. Closed without code changes. |