← Back to issue list

make charm take zips

View original Github issue

Metadata

Project
charmcraft
Number
#148
Type
issue
State
closed
Author
chipaca
Labels
—
Created
Updated
Closed

Current evaluation

Legacy-store support for uploading Charmcraft-built .charm files was implemented and released in charm, resolving the request.

Resolution: closed resolved

Reason: Repository metadata records that charm-tool support was implemented and released. Facundobatista's closing comment on 2020-10-14 confirmed that charm was releasing the capability.

Evaluated by: mr-cal-bot

No scores available.

Issue body

It should be possible to push the .charm that results from `charmcraft build` to the old charm store.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Legacy-store support for uploading Charmcraft-built .charm files was implemented and released in charm, resolving the request.
stealth/space-bunny-alpha — closed resolved Implemented and released charm-tool support for pushing charmcraft-built .charm files to the legacy charm store.
qwen3.6-35b-a3b-mtp-q6 — — Feature to push .charm files to the legacy charm store was implemented and released in the charm tool. The request was fulfilled and the issue closed.
qwen/qwen3.6-35b-a3b — — Support for pushing .charm files to the old charm store was implemented and released in the charm package. The issue was closed following confirmation of the release.
qwen/qwen3.6-35b-a3b — — The charm CLI now accepts zip files, resolving the request via an external release.
qwen3.6-35b-a3b-mtp-q6 — — Closed as superseded. The requested .charm file support is being released via the external charm package, per maintainer confirmation.

Update history

No update history recorded yet.

Related work

  • Related To: python-libjuju#434 (confidence 85%)

    The issue author identified this as the probable tracking issue for the legacy-store upload capability.

Related issues

Issue Project State Summary Similarity
#1263 `charmcraft upload` should be able to take several `*.charm` files at once charmcraft closed Closed by the reporter as expected behaviour: maintainers explained Charmhub supports charms of different bases per revision, so per-base .charm files are uploaded separately and Juju picks the right one. No code change.
70%