login, names and register should not fail with "The field 'bases' is mandatory when type=charm"
Metadata
Current evaluation
Fixed by merged PR #1035 (commit 91a5f553): login, register, and names no longer fail when run in charm source directories without a bases field.
Resolution: closed resolved
Reason: Merged PR #1035 resolved the report by preventing these commands from requiring project metadata such as bases; commit 91a5f553 contains the fix.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Using charmcraft 2.2.0 on Ubuntu 22.04.2, most commands I'm running are failing with:
`The field 'bases' is mandatory when type=charm`
Maybe some commands should, but `login`, `register` and `names` should not. Appears to be caused by running the commands from a directory with charm source code.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #1035 (commit 91a5f553): login, register, and names no longer fail when run in charm source directories without a bases field. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #1035 (commit 91a5f553), so login, register, and names no longer require a bases field when run in charm source directories. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved via commit 91a5f5530df933210d6e88d8a44997a559b6910c by @syu-w. The login, register, and names commands no longer require a bases field when executed in charm source directories. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved via commit 91a5f55 by @syu-w. The login, names, and register commands now bypass mandatory bases validation when run in charm source directories, preventing the previous failure. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed login, register, and names commands incorrectly failing with a mandatory bases field error when run in charm source directories. Resolved via commit 91a5f5530df933210d6e88d8a44997a559b6910c by @syu-w. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed login, register, and names commands failing with a mandatory bases error in charm directories. Resolved via commit 91a5f5530df933210d6e88d8a44997a559b6910c by @syu-w, skipping charm manifest validation. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#1035
(confidence 99%)
The merged PR implemented the fix in commit 91a5f553.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #383 commands/build: charm file name format support for bases (CRAFT-66) | charmcraft | merged | Merged PR #383 (commit 951f6aaa; merge 1c839909) added bases-aware charm filename formatting and tests, retaining the legacy runtime path pending default-bases configuration. | |
| #791 Enforced DN03: the 'bases' is now mandatory for charms in the config (CRAFT-785). | charmcraft | merged | Merged PR canonical/charmcraft#791 (9c52a73a), enforcing DN03 so charm configs require bases and updating affected tests; fixes #655. |