← Back to issue list

`charmcraft pack` does not recognize updated `charmcraft.yaml` file

View original Github issue

Metadata

Project
charmcraft
Number
#1160
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: needs triage

Reason: The issue has no labels, no comments, and no maintainer response, so it lacks any sign of triage. It is a real bug (build-snaps channel changes in charmcraft.yaml don't take effect without a clean) that was moved to craft-parts#496, which is still open, so it should be kept open pending a craft-parts fix. Staleness is high (last activity 381 days ago, no engagement) but the underlying dependency issue remains unresolved, so closing would be premature.

Impact: 50 Quick Win: 22.5 Staleness: 70 Complexity: 55 Confidence: 65 Support Request: 10

Issue body

### Bug Description Originally reported by @jugmac00, moved to craft-parts: https://github.com/canonical/craft-parts/issues/496 Once there's a craft-parts patch release we should be able to bring it into charmcraft. ### To Reproduce See https://github.com/canonical/craft-parts/issues/496 ### Environment See https://github.com/canonical/craft-parts/issues/496 ### charmcraft.yaml ```shell See https://github.com/canonical/craft-parts/issues/496 ``` ### Relevant log output ```shell See https://github.com/canonical/craft-parts/issues/496 ```

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 50
Quick Win: 22.5
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 5
Confidence: 90
Support Request: 0
close stale charmcraft pack fails to detect changes in charmcraft.yaml. The upstream fix is tracked in craft-parts issue #496. This issue is currently blocked, awaiting a craft-parts patch release before integration.

Update history

No update history recorded yet.

Related work

  • Blocked By: canonical/craft-parts#496 (confidence 95%)

    Issue body explicitly states the bug was moved to craft-parts#496 and that a craft-parts patch release is needed before it can be brought into charmcraft; that issue is still open.

Related issues

Issue Project State Summary Similarity
#1530 Changing charmcraft.yaml doesn't update the resulting charm's metadata.yaml charmcraft open Bug: editing charmcraft.yaml then re-running `charmcraft pack` does not update the resulting charm's metadata.yaml. Filed by a maintainer (lengau); last comment (2024-09-09) says it's unclear if still reproducible. Related open craft-application#821 describes the same 'Already packed' skip behavior.
80%
#496 part `build-snaps` channel change doesn't work without a `clean` craft-parts open Changing the build-snaps channel in charmcraft.yaml is ignored on subsequent charmcraft pack runs unless a clean is performed first. Triaged as a craft-parts bug (snap not refreshed when channel changes); transferred to craft-parts with a related charmcraft hotfix bug.
79%
#710 `charmcraft pack` retains no longer existing files from previous packs charmcraft open charmcraft pack includes files deleted from the working directory in the charm archive; clean fixes it. Triaged as a known bug, re-confirmed present in Oct 2024, upstream craft-parts bug filed, per-part clean workaround documented.
78%
#907 `charmcraft pack` does not handle updating a file's execution permissions without a `charmcraft clean` charmcraft open charmcraft pack ignores local file permission changes (e.g., chmod +x on src/charm.py) until a full charmcraft clean, causing confusing lint errors. Maintainer reproduced and filed upstream craft-parts#311; still unfixed.
75%
#552 `charmcraft pack` runs indefinitely when using parts charmcraft closed The charmcraft pack hang was caused by a duplicate ignore patterns bug. This was fixed in Charmcraft 1.3.0. The author confirmed they would upgrade and close the issue pending recurrence.
74%
#821 5.5.0 changes pack semantics if the project file has different metadata craft-application open Charmcraft pack skips repacking when only charmcraft.yaml metadata (e.g. summary, config, platforms) changes, leaving a stale .charm. Triaged and moved to craft-application; workaround is clean. Conditional repacking support added in #1111.
72%
#501 charmcraft pack fails trying to include a non-existing charm/src/.tox/ charmcraft closed charmcraft pack failed when copying non-existent build directories or files. Users worked around it with charmcraft clean. The issue was closed as fixed upstream in the underlying parts lifecycle code.
72%
#287 `charmcraft build` failing if charm has manifest.yaml charmcraft closed charmcraft build crashed when a pre-existing manifest.yaml conflicted with machine-generated builds introduced in PR #281. Fixed in master by validating manifest.yaml and using clean build directories to prevent conflicts and crashes.
72%
#514 `charmcraft build` silently omits files called out in `charmcraft.yaml` if executed from an external directory charmcraft closed Fixed in PR #525. Resolved a bug where charmcraft build and pack silently omitted glob-patterned files when run externally. The fix corrects path misalignment between Charmcraft and the parts processor, ensuring proper glob expansion.
72%
#2273 charmcraft.yaml deleted while packing (working tree not clean) charmcraft open charmcraft pack deletes charmcraft.yaml from the working tree, making git describe --dirty report -dirty on clean release builds. Reported with charmcraft 3.4.3, no maintainer response or labels in ~13 months.
72%