`charmcraft analyze` - check for library modifications
Metadata
Current evaluation
Closed as superseded by the charm-libs key; PR #2473 documented the related library behavior, so the proposed analyze-time modification check was not implemented.
Resolution: closed superseded
Reason: The maintainer explicitly closed the issue as superseded by the charm-libs key in the closing comment. Commit 179d2553, from PR #2473, documents the related Charmhub-hosted-library behavior and replacement path.
Evaluated by: mr-cal-bot
No scores available.
Issue body
The way charm libraries generally function means that charm authors end up with local versions of third party libraries, which is by design.
Some people have recently struggled with the contribution/feedback method and made changes to third-party library files *locally*, then had issues that the original library author has struggled to debug/replicate due to disceprancies.
Charmcraft could help solve this by warning in the lint stage if a library has been changed from the original file that was downloaded as part of `charmcraft fetch-lib`.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Closed as superseded by the charm-libs key; PR #2473 documented the related library behavior, so the proposed analyze-time modification check was not implemented. | |
| stealth/space-bunny-alpha | — | closed superseded | Local-library modification detection was superseded by managed charm-libs/fetch-libs declarations; #2473 later documented the replacement model. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed as superseded by the `charm-libs` project key; the replacement library workflow was documented in charmcraft#2473 via commit 179d2553. | |
| stealth/space-bunny-alpha | — | closed superseded | Proposed library-modification linting was superseded by the charm-libs key, documented in #2473. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed as superseded by the `charm-libs` key, which replaced lint-based detection of locally modified libraries. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded by the charm-libs key. The lint feature for detecting local library modifications was replaced with this configuration approach. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
85
Support Request:
10
|
needs triage | Feature request to add library modification detection to charmcraft analyze. Untriaged, no labels, last activity over 10 months ago, linked to an internal Jira ticket. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
88
Complexity:
35
Confidence:
75
Support Request:
10
|
needs triage | Feature request to add library modification checks to charmcraft analyze. Open for nearly five years with only a bot comment linking to an internal ticket. Awaiting maintainer assessment and prioritization. |
Update history
| Date | Change |
|---|---|
| closed |
Related work
-
Superseded By:
canonical/charmcraft#2473
(confidence 95%)
The issue was superseded by the charm-libs approach, with related library behavior clarified in PR #2473 and commit 179d2553.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #509 `charmcraft analyze` - check for new version of library | charmcraft | closed | Closed as a duplicate of canonical/charmcraft#417, which was abandoned after concerns that remote library checks would add network calls and slow packing. |