Can't build charm targeted at the current development release: `Skipping 'bases[8].build-on[0]': channel 'devel' does not match host '23.10'.`
Metadata
Current evaluation
Building charms with channel devel failed due to a host channel mismatch. The issue was closed as fixed in Charmcraft 3.
Suggested action: —
No scores available.
Issue body
### Bug Description
Slightly, but not quite, related to #1104 and #1203.
As proponents and developers of model driven operations, trying to release machine charms for new versions of, ehh, machines, it would be great to be able to know ahead of time whether your charmed machine operator would work with the next Ubuntu release.
The references above and this bug report serves as proof that this is not currently possible.
### To Reproduce
Attempt to pack a charm with a bases config like:
```yaml
- build-on:
- name: ubuntu
channel: devel
architectures: [amd64]
run-on:
- name: ubuntu
channel: "23.10"
architectures: [amd64]
```
### Environment
N/A
### charmcraft.yaml
```shell
N/A
```
### Relevant log output
```shell
See above.
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Building charms with channel devel failed due to a host channel mismatch. The issue was closed as fixed in Charmcraft 3. | |
| qwen/qwen3.6-35b-a3b | — | — | Charmcraft rejected charms targeting the development release due to a channel validation mismatch. The issue was closed after a maintainer confirmed the build process is fixed in Charmcraft 3. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as fixed in Charmcraft 3. A maintainer confirmed the devel channel mismatch error no longer occurs after updated validation logic, making the contributor's suggested patch unnecessary. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The devel channel validation error was fixed in Charmcraft 3. A maintainer closed the issue, confirming the resolution is included in the newer release and requesting users reopen if the problem persists. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as fixed in Charmcraft 3. The maintainer confirmed the devel channel build mismatch error is resolved in the newer version, superseding the proposed patch. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #938 No suitable 'build-on' environment found in any 'bases' configuration -- channel '20.04' does not match host '22.04' | charmcraft | closed | Closed as not a bug. The author confirmed that charmcraft's destructive mode requires the host OS to match the configured build base. No code changes were made. | |
| #2507 Cannot build charm when base is Questing and build-base is devel | charmcraft | open | 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. | |
| #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. | |
| #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. | |
| #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. |