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
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.
Resolution: closed resolved
Reason: The closing maintainer comment stated that devel-channel builds were fixed in Charmcraft 3. The relevant platform-building implementation was merged in PR #1554 as commit e3de0a46.
Evaluated by: mr-cal-bot
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | 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. | |
| stealth/space-bunny-alpha | — | closed resolved | A maintainer closed the report as fixed in Charmcraft 3, stating that development-channel builds should work and inviting a reopen otherwise. | |
| stealth/space-bunny-alpha | — | closed resolved | Closed as fixed in Charmcraft 3 after a maintainer stated development-channel builds were believed resolved; no resolving PR or commit is cited. | |
| stealth/space-bunny-alpha | — | closed resolved | Devel-channel build-on mismatch was reported fixed in Charmcraft 3; the issue was closed with a request to reopen if the failure still occurred. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in Charmcraft 3. Maintainer @lengau closed #1267 after confirming the devel build-on host validation was fixed in the Charmcraft 3 series. | |
| 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. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#1554
(confidence 78%)
Implemented platform-based charm building, replacing the legacy bases path that produced the devel-versus-host channel mismatch.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2507 Cannot build charm when base is Questing and build-base is devel | charmcraft | open | 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. | |
| #792 22.10 - Failed to build charm for bases index '0'. | charmcraft | closed | Reporter's reactive charm failed to build; maintainer facundobatista closed it as not a Charmcraft bug — the legacy `charm` tool rejects metadata.yaml without a `series` list. Author agreed and took it to the Juju team. | |
| #2259 Builds fail for 20.04 (in some common circumstances) | charmcraft | closed | Fixed in canonical/charmcraft#2275 (commit 65d01ed5): charm builds now apply a bundled setuptools-scm constraint, avoiding the Python 3.8/3.9 all-source dependency cycle. | |
| #1697 Charmcraft 3 breaks charms with multiple run-on architectures | charmcraft | closed | Closed as blocked by canonical/craft-application#394; no resolving Charmcraft PR, commit, or release was identified for the multi-architecture regression. |