22.10 - Failed to build charm for bases index '0'.
Metadata
Current evaluation
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.
Resolution: closed not a bug
Reason: Closed by maintainer facundobatista on 2022-06-27 with the diagnosis that the external `charm` build backend (used by reactive charms) errors with 'E: missing series: must be a list of series names', i.e. the upstream charm's metadata.yaml was the problem, not Charmcraft. The author confirmed on 2022-06-28 that the tested change dropped the series section and would follow up with the Juju team.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | 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. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as not a Charmcraft bug: the legacy `charm` reactive build backend rejected the charm because metadata.yaml dropped the `series` list. Reporter (freyes) agreed and took it to the Juju team. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as not a Charmcraft bug: the legacy charm tool required a series list in metadata.yaml; the author accepted this and deferred to the Juju team. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as not a charmcraft bug. The build failure resulted from a missing series field in the project's metadata.yaml. The author acknowledged the configuration issue and will coordinate with the Juju team regarding the transition from series to bases. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as not a Charmcraft bug. The reactive charm backend requires a series field in metadata.yaml, but the project removed it to use bases instead. Author acknowledged the issue and will coordinate with the Juju team to fix metadata. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#872
(confidence 60%)
Other reactive-plugin charm building gaps filed by the same era, but concerns missing build metadata rather than this series validation failure
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #639 Can't build charm: Failed to build charm for bases index '0' | charmcraft | closed | Closed as a dependency/configuration issue: adding setuptools fixed Jinja2 packing, while Tempita required setuptools <58. A later build recovered after charmcraft clean. | |
| #529 Charm deployment to OSM fails | charmcraft | closed | Maintainer facundobatista closed it as not charmcraft-related: bundle.yaml pointed at a build directory, not the generated powerdns.charm. Reporter confirmed deploying works after using the .charm file path. | |
| #904 Can't build/pack a charm with Focal | charmcraft | closed | Closed as an upstream charm-tools bug; the missing MarkupSafe failure was tracked in juju/charm-tools#646. | |
| #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. | |
| #632 Cant build charm with charmhelpers - missing markupsafe | charmcraft | closed | Charmhelpers-based charm build failed with missing markupsafe via Jinja2/setuptools 58+ vs Tempita 2to3 conflict. cmatsuoka diagnosed it and the reporter confirmed the workaround works; maintainer closed the issue as solved without a charmcraft code change. | |
| #249 `charmcraft build` will let you build a charm that won't deploy | charmcraft | closed | Closed by facundobatista as a duplicate, tracking all build-time sanity checks (incl. config.yaml/actions.yaml validity) in the umbrella issue charmcraft#27; later implemented by merged PR #556 (a585aec6). |