← Back to issue list

The `pack` command does not validate the entrypoint unless it's specified

View original Github issue

Metadata

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

Current evaluation

Fixed in canonical/charmcraft#767 (merge commit 4b64ec0f): pack now validates the default entrypoint when --entrypoint is omitted.

Resolution: closed resolved

Reason: PR #767 was merged as commit 4b64ec0f and changed validation to cover every entrypoint source, including the default src/charm.py.

Evaluated by: mr-cal-bot

No scores available.

Issue body

If `pack` is run without using the `--entrypoint` option, even if it defaults to `src/charm.py`, it's not running any validation on it (e.g. that is executable).

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Fixed in canonical/charmcraft#767 (merge commit 4b64ec0f): pack now validates the default entrypoint when --entrypoint is omitted.
stealth/space-bunny-alpha — closed resolved Fixed by merged PR #767 (merge commit 4b64ec0f), which validates every entrypoint source, including the default, instead of skipping validation when --entrypoint is omitted.
stealth/space-bunny-alpha — closed stale The report was closed with no comments or documented fix; no resolving PR or commit was identified.
qwen3.6-35b-a3b-mtp-q6 — — Closed without resolution. The pack command remains unvalidated when using default entrypoints. Issue appears abandoned due to inactivity.
qwen/qwen3.6-35b-a3b — — The missing entrypoint validation report was closed without resolution. Zero comments and no linked pull requests indicate the report was abandoned.
qwen3.6-35b-a3b-mtp-q6 — — The pack command lacks entrypoint validation when using defaults. The report was closed without resolution or comments, indicating it was abandoned.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/charmcraft#767 (confidence 99%)

    The merged PR applied entrypoint validation even when the CLI option was not explicitly supplied.

Related issues

Issue Project State Summary Similarity
#781 v1.7 regression: `pack` errors out prematurely with `Charm entry point was not found` charmcraft closed Fixed by merged PR canonical/charmcraft#782 (commit 63643466), moving entry-point validation after the build lifecycle so override-build can generate custom entry points.
76%
#782 Validate the entrypoint after build. charmcraft merged Merged PR #782 fixed the v1.7 packing regression by validating charm entry points after the build lifecycle, allowing build hooks to generate them dynamically.
72%