`charmcraft pack` does not recognize updated `charmcraft.yaml` file
Metadata
Current evaluation
Tracked upstream: charmcraft pack ignores build-snaps channel changes in charmcraft.yaml unless clean is run. Root cause is craft-parts#496 (build-snaps missing from properties_of_interest), still unfixed; charmcraft only needs a craft-parts bump once patched.
Suggested action: keep open
Reason: Authored by maintainer lengau with an explicit plan ("Once there's a craft-parts patch release we should be able to bring it into charmcraft"), so this is a deliberately tracked mirror, not an unreviewed report. I verified the root cause is still live: craft-parts HEAD (aa26742f) build_state.properties_of_interest lists after/build-attributes/build-environment/build-packages/disable-parallel/organize/override-build but not build-snaps, and craft-parts#496 remains open — charmcraft pins craft-parts~=2.35. The narrow, stale-artifact-only scope (fix is a one-line upstream addition plus a dependency bump) keeps impact and complexity low, while the completely empty repro/log sections (every field just links upstream) hold actionability down.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
12
Complexity:
25
Confidence:
82
Actionability:
45
|
keep open | Tracked upstream: charmcraft pack ignores build-snaps channel changes in charmcraft.yaml unless clean is run. Root cause is craft-parts#496 (build-snaps missing from properties_of_interest), still unfixed; charmcraft only needs a craft-parts bump once patched. | |
| ~deepseek/deepseek-pro-latest |
Impact:
40
Quick Win:
16
Complexity:
35
Confidence:
80
Actionability:
60
|
keep open | Tracking issue for a craft-parts bug where build-snaps channel changes don't trigger a rebuild without clean; upstream craft-parts#496 remains open. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
9
Complexity:
50
Confidence:
70
Actionability:
60
|
keep open | charmcraft pack ignores updated charmcraft.yaml (build-snaps channel changes) without running clean first; blocked by craft-parts#496 which remains open. | |
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
22
Staleness:
70
Complexity:
55
Confidence:
65
Support Request:
10
|
needs triage | charmcraft pack ignores updated build-snaps channel in charmcraft.yaml without a clean; tracked as a craft-parts bug (canonical/craft-parts#496, still open) awaiting a dependency patch release to pull into charmcraft. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
10
Confidence:
85
Support Request:
5
|
close stale | charmcraft pack fails to recognize updated charmcraft.yaml. This is a 3-year-old tracking ticket for an external craft-parts patch. Currently inactive and likely resolved or obsolete. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
10
Confidence:
80
Support Request:
0
|
close stale | charmcraft pack fails to recognize updated charmcraft.yaml. Currently blocked on upstream craft-parts fix (#496). No maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
10
Confidence:
85
Support Request:
0
|
close stale | Tracking ticket for backporting a charmcraft.yaml parsing fix from craft-parts. Blocked on an external dependency patch with no activity in over a year. Unlabelled and untriaged. |
Update history
No update history recorded yet.
Related work
-
Blocked By:
craft-parts#496
(confidence 95%)
Explicitly cited in the body as the origin of the bug and the prerequisite fix; still open and confirmed unfixed in craft-parts HEAD.
-
Related To:
craft-application#821
(confidence 70%)
Same stale-build-after-project-file-change family, but about project metadata rather than part properties.
-
Related To:
charmcraft#1530
(confidence 65%)
Title is nearly identical — 'Changing charmcraft.yaml doesn't update the resulting charm's metadata.yaml' — though that one was fixed by PR #2874.
-
Related To:
charmcraft#907
(confidence 60%)
Same pattern: pack ignores a real change until clean, via a different upstream craft-parts dirty-check gap.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1530 Changing charmcraft.yaml doesn't update the resulting charm's metadata.yaml | charmcraft | open | The original stale metadata.yaml bug was fixed by merged PR #2874; a later Charmcraft 5.5.0 stale-repack variant remains tracked in craft-application#821. | |
| #907 `charmcraft pack` does not handle updating a file's execution permissions without a `charmcraft clean` | charmcraft | open | charmcraft pack keeps stale file permissions in the build container unless `charmcraft clean` is run; root cause is craft-parts' outdated check only comparing mtime. Reproduced upstream, workaround `touch` documented, still open. | |
| #710 `charmcraft pack` retains no longer existing files from previous packs | charmcraft | open | Repacking reuses the part's build container, so files deleted from the working tree linger in the resulting charm until `charmcraft clean <part>`. Maintainers confirmed it still reproduces; root cause tracked upstream in craft-parts#851. | |
| #501 charmcraft pack fails trying to include a non-existing charm/src/.tox/ | charmcraft | closed | The missing-file packing failure was fixed upstream in craft-parts; maintainer lengau closed charmcraft#501 on 2024-02-22 as resolved. | |
| #552 `charmcraft pack` runs indefinitely when using parts | charmcraft | closed | The hang was caused by duplicated local-source ignore patterns in Charmcraft 1.2.1 and fixed in 1.3.0 via canonical/craft-parts#120 (commit 280e1592). | |
| #287 `charmcraft build` failing if charm has manifest.yaml | charmcraft | closed | Builds stopped crashing on an existing manifest.yaml after Charmcraft added manifest validation and switched charm builds to clean directories. | |
| #746 `charmcraft pack` for existing environment does not remove files that have been deleted | charmcraft | closed | Closed as a duplicate of charmcraft#710 by maintainer facundobatativa (facundobatista) on 2022-04-13. #710 remains open, with the root cause tracked upstream in craft-parts#851. | |
| #821 5.5.0 changes pack semantics if the project file has different metadata | craft-application | open | Metadata-only charmcraft.yaml edits were skipped as "Already packed," leaving stale .charm artifacts; Charmcraft PR #2890 is reported to fix repacking after the edit. | |
| #2273 charmcraft.yaml deleted while packing (working tree not clean) | charmcraft | open | Packing a Charmcraft 3.4.3 reproducer deletes tracked charmcraft.yaml before a dump part, making git describe --dirty tag release builds incompatible; untriaged and apparently unresolved | |
| #701 `charmcraft pack` doesn't include all error output | charmcraft | closed | Missing charmcraft pack error output was fixed in Charmcraft 1.5 through improved managed-instance log retrieval; the reporter was using 1.4.0, so the issue was closed. |