fix(package): use correct legacy bases architectures
Metadata
Current evaluation
PR #1792 fixing legacy bases architecture selection was closed unmerged on 2024-08-07, superseded by #1795, which was merged as commit 8b16cae4 and shipped in Charmcraft 3.1.2 to fix issue #1783.
Resolution: closed superseded
Reason: The author commented 'Superseded by #1795', which merged to main as commit 8b16cae4 ('fix(package): Limit the bases in manifest.yaml') and restricted manifest.yaml bases to the current build base instead of all run-on bases, resolving issue #1783 in Charmcraft 3.1.2.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Previous behaviour was attaching all run-on bases, where we want to only attach run-on bases that match the current build base.
Fixes #1783
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | PR #1792 fixing legacy bases architecture selection was closed unmerged on 2024-08-07, superseded by #1795, which was merged as commit 8b16cae4 and shipped in Charmcraft 3.1.2 to fix issue #1783. | |
| stealth/space-bunny-alpha | — | closed superseded | Superseded by charmcraft PR #1795, which merged the fix limiting manifest.yaml bases to the current build rather than attaching all run-on bases. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded by #1795. The original change addressed legacy base architecture handling by restricting attached run-on bases to match the current build base, but was replaced before merging. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by #1795. The changes corrected legacy base architecture attachment to only match the current build base, resolving issue #1783. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
charmcraft#1795
(confidence 99%)
Author's closing comment states it was superseded by #1795, which merged as commit 8b16cae4.
-
Related To:
charmcraft#1783
(confidence 97%)
#1792 was a fix for #1783, which was closed by the merged #1795 and released in Charmcraft 3.1.2.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1783 Charmcraft 3 no longer respects legacy bases architectures | charmcraft | closed | Fixed in Charmcraft 3.1.2 by merged PR #1795 (8b16cae4), which limits manifest.yaml bases to those in the current build, preserving arm64 metadata. | |
| #6494 fix: use correct base in architecture errors | snapcraft | merged | Fixed architecture error messages to display the correct base. Merged as #6494. |