← Back to issue list

fix(lifecycle): allow building multi-arch charms

View original Github issue

Metadata

Project
charmcraft
Number
#1818
Type
pull request
State
merged
Author
lengau
Labels
—
Created
Updated
Closed

Current evaluation

Merged to main as commit c787ea23 (PR #1818), letting Charmcraft's lifecycle builds handle charms with multiple run-on architectures; landed alongside Ruff 0.6.0 fixes from #1825. Fixes #1697.

Resolution: closed resolved

Reason: PR #1818 was merged into main by maintainer lengau with 2 approvals and landed as commit c787ea23 ("fix(lifecycle): allow building multi-arch charms"), resolving issue #1697 where Charmcraft 3 broke charms with multiple run-on architectures.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Fixes #1697 Requires #1825

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged to main as commit c787ea23 (PR #1818), letting Charmcraft's lifecycle builds handle charms with multiple run-on architectures; landed alongside Ruff 0.6.0 fixes from #1825. Fixes #1697.
stealth/space-bunny-alpha — closed resolved Merged PR #1818 as commit c787ea23, fixing #1697 by allowing Charmcraft lifecycle builds of multi-architecture charms. The change required Ruff fixes from #1825.
stealth/space-bunny-alpha — closed resolved Merged charmcraft#1818 fixed #1697 by allowing lifecycle builds of multi-architecture charms. The required Ruff lint cleanup in charmcraft#1825 was also merged.
qwen/qwen3.6-35b-a3b — — Merged to resolve #1697, enabling multi-arch charm builds. Approved by two reviewers and passed CI. The update modifies 38 files (+298/-78 lines) and requires PR #1825.
qwen3.6-35b-a3b-mtp-q6 — — Merged to fix lifecycle module and enable multi-arch charm builds. Resolves issue #1697 and depends on PR #1825. Authored by maintainer lengau, the change was successfully integrated.

Update history

No update history recorded yet.

Related work

  • Duplicate Of: canonical/charmcraft#1697 (confidence 90%)

    PR body states 'Fixes #1697'; the original multi-run-on breakage report is the issue this work targets.

  • Related To: canonical/charmcraft#1825 (confidence 85%)

    PR #1818 explicitly required #1825 (Ruff 0.6.0 lint autofixes, merged as 7aa2965b) before it could be merged.

  • Related To: canonical/charmcraft#2133 (confidence 45%)

    Later report of a residual multiple run-on build failure, fixed separately in Charmcraft 3.4.3 via craft-providers #722.

Related issues

Issue Project State Summary Similarity
#215 fix(charm): accept redundant multi-base charms craft-platforms merged Merged PR #215 as commit 4879309, allowing redundant multi-base charms when they produce equivalent valid build plans and addressing canonical/charmcraft#2620.
76%
#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.
74%
#1400 fix: always include architectures in charm manifest charmcraft merged Merged canonical/charmcraft#1400 to always serialize architecture fields in generated charm manifests, including inferred defaults; rendering and tests were updated across nine files.
73%
#1698 build-for architecture 'all' for arch-independent charms not supported charmcraft closed Support for build-for: all landed in #1894 (f1755e8f), with architecture-independent charm tests merged in #1895 (f136def1).
72%
#2275 fix(charm): workaround to allow charmcraft-wide constraints charmcraft merged Merged #2275 as commit 65d01ed5, adding a Charmcraft-wide build-constraints workaround for Ubuntu 20.04 failures tracked in #2259 (CHARMCRAFT-614).
72%
#1895 tests: check that architecture "all" works charmcraft merged Merged as f136def1, adding tests for architecture-independent charms using build-for: all and fixing #1698; prerequisite #1894 was merged.
71%