← Back to issue list

Support charm libraries renaming

View original Github issue

Metadata

Project
charmcraft
Number
#214
Type
issue
State
closed
Author
facundobatista
Labels
—
Created
Updated
Closed

Current evaluation

Closed as stale without implementation; library-fetch logic still contains a rename-handling TODO tied to #214.

Resolution: closed stale

Reason: No linked fix, PR, commit, or closing explanation was recorded. The current fetch implementation still marks renamed-library handling as a TODO and explicitly references issue #214.

Evaluated by: mr-cal-bot

No scores available.

Issue body

The user may rename the file used to hold the library. This impacts in two commands: - **Publish**: needs to detect that the library was renamed locally and rename it in the store, properly notifying the user. **Note that Charmhub needs to implement support for this.**: $ mv charms/mysql/v1/super.py charms/mysql/v1/superduper.py $ charmcraft publish-lib charms.mysql.v1.superduper Renamed the library in the store from 'super' to 'superduper'. Library charms.mysql.v1.superduper was already updated in the store. - **Fetch**: needs to detect that the library was renamed in Charmhub (the local file still reflects the old name), do the change locally, and properly inform the user: The library <full name> has been renamed to <new full name>, please fix the corresponding import sentences in the Python code and rename the file to acknowledge that the system is updated.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed stale Closed as stale without implementation; library-fetch logic still contains a rename-handling TODO tied to #214.
stealth/space-bunny-alpha — closed stale Closed as stale with no linked fix; rename handling for publish-lib and library fetch was not implemented or documented.
qwen3.6-35b-a3b-mtp-q6 — — Closed without implementation or discussion, likely abandoned or superseded. The feature request for automating library renaming in publish and fetch commands remains unaddressed.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The feature request to handle charm library renaming in publish and fetch commands was abandoned. No code changes or related pull requests were merged, and Charmhub integration remains unaddressed.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The feature request for handling charm library renaming in publish-lib and fetch commands was abandoned due to prolonged inactivity and unresolved Charmhub dependencies.
qwen3.6-35b-a3b-mtp-q6 — — Closed without implementation. The feature request for handling charm library renaming in publish-lib and fetch-lib commands was abandoned due to inactivity and upstream Charmhub dependencies. No resolution or merge occurred.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#284 Running `charmcraft fetch-lib` on a charm with dashes should fetch to a path with underscores charmcraft closed Closed as stale with no recorded fix or maintainer rationale. A later unlinked change, #1701 (3af2c248), implemented underscore support for fetch-libs.
73%