Charmcraft 3 including previously-built charms in new charm builds
Metadata
Current evaluation
Fixed in PR #1793 (commit affc209b): subsequent charmcraft pack runs no longer include previously built .charm artifacts in the new charm.
Resolution: closed resolved
Reason: PR #1793 was merged as commit affc209b, titled "fix(application): exclude files from charm", preventing prior build artifacts from being packaged during later builds.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
If you build a charm in a directory and then run `charmcraft pack` again, it'll re-build with that previous charm inside the directory.
### To Reproduce
1. Clone any charm (e.g. `git@github.com:canonical/postgresql-test-app.git`)
2. `charmcraft pack`
3. `charmcraft pack`
### Environment
n/a
### charmcraft.yaml
```shell
n/a
```
### Relevant log output
```shell
n/a
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed in PR #1793 (commit affc209b): subsequent charmcraft pack runs no longer include previously built .charm artifacts in the new charm. | |
| stealth/space-bunny-alpha | — | closed stale | Charmcraft #1791 was closed without a fix or maintainer explanation; the only comment recorded an internal sync to CRAFT-3181. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. A bot synced the report to an internal Jira ticket, but no developer response or pull request followed, indicating the bug report was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a fix. The report that charmcraft pack re-includes previously built charms on subsequent runs was tracked via an internal Jira ticket, but no resolution or merge was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The charmcraft pack bug involving previously-built charms in new builds received no developer response or fix, and was left abandoned after an automated Jira sync comment. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. An internal Jira ticket (CRAFT-3181) was created, but no fix or code changes were implemented. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#1793
(confidence 98%)
Merged fix explicitly excludes files generated by earlier charm builds.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #420 Missing Charmcraft artifact in Charm Build | fetch-service | closed | Fixed by merged PR #465 (commit 1309dc6), preventing rejected go-module-git inspection from overwriting approved Charmcraft artifact metadata. | |
| #2358 docs: release Charmraft 3.5.2 | charmcraft | merged | Released Charmcraft 3.5.2 in merged PR #2358 (commit bcbd08c0), updating release notes; the release branch was later merged into main by #2359. | |
| #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. | |
| #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). | |
| #2496 docs: add Charmcraft 4.1 release notes | charmcraft | closed | Closed as a duplicate after the Charmcraft 4.1 release notes were merged through canonical/charmcraft#2483 in commit b742f96c. | |
| #2483 docs: add Charmcraft 4.1 release notes | charmcraft | merged | Merged PR #2483 in commit b742f96c, adding Charmcraft 4.1 release notes; the page was initially left unindexed pending the interim bases policy. | |
| #1845 Building multiple charms simultaneously can cause caching errors | charmcraft | closed | Parallel charm builds were fixed by merged PR #1888 (commit 4cce11b0), which locks the shared cache to prevent concurrent builds from reusing incomplete files. | |
| #249 `charmcraft build` will let you build a charm that won't deploy | charmcraft | closed | Closed by facundobatista as a duplicate, tracking all build-time sanity checks (incl. config.yaml/actions.yaml validity) in the umbrella issue charmcraft#27; later implemented by merged PR #556 (a585aec6). | |
| #324 Provide the building charms functionality through the pack command. | charmcraft | merged | Merged into main: charm building is now available through the pack command, in merge commit ebc0d75b. | |
| #148 feat(charm): add a build planner for bases charms | craft-platforms | merged | Merged PR #148 added a Charm build planner for legacy charms using the bases key, addressing CHARMCRAFT-630 in commit 16ff218. |