← Back to issue list

snapcraft does not seem to call `snap pack --check-skeleton` to validate that snap has correct things

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1950465
Type
issue
State
closed
Author
~xnox
Labels
—
Created
Updated
Closed

Current evaluation

Snapcraft now runs snap pack --check-skeleton during packing, catching invalid plug and slot names before installation. Implemented by merged PR #3743 (commit 7c927032d).

Resolution: closed resolved

Reason: The validation was added as a temporary workaround in merged PR #3743, commit 7c927032d, so malformed plug or slot definitions are reported during packing instead of by snapd at install time.

Evaluated by: mr-cal-bot

No scores available.

Issue body

I built a snap with plug name that contains '.' snapcraft made the snap just fine. But when i installed it, snapd said that there is a new warning and that my snap has bad plugs or slots, listed them as invalid plug name. I would have hoped that snapcraft would show such a warnings; and/or fail to build the snap. After fixing that, i got a new warning that system-files plug cannot end with "/". Again I would have hoped that snapcraft would tell me that, not snapd.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Snapcraft now runs snap pack --check-skeleton during packing, catching invalid plug and slot names before installation. Implemented by merged PR #3743 (commit 7c927032d).
qwen/qwen3.8-27b — closed resolved Snapcraft was not running snap pack --check-skeleton, so invalid plug/slot names (e.g. dots, trailing /) only surfaced at install time via snapd. Resolved by PR #3743 (commit 7c927032d, 'pack: check skeleton'), which added --check-skeleton validation to the pack step.
stealth/space-bunny-alpha — closed stale Closed as abandoned after prolonged inactivity, without a resolving change, merge reference, or maintainer explanation.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The request to integrate snap pack --check-skeleton validation into snapcraft was abandoned due to prolonged inactivity. No code changes or merges were applied.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The request to add snap metadata validation during build was abandoned due to inactivity and lack of proposed fixes.
qwen/qwen3.6-35b-a3b — — Closed without action due to inactivity. The report highlights missing validation for invalid plug and slot names in snapcraft, suggesting integration of snap pack --check-skeleton to catch errors during build rather than at installation. No fix was implemented.
qwen3.6-35b-a3b-mtp-q6 — — Closed without resolution. The report requested snapcraft validate plug and slot names during build, warning or failing instead of deferring to snapd. No fix was implemented.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#3743 (confidence 100%)

    Merged PR added --check-skeleton validation to the Snapcraft pack step in commit 7c927032d.

Related issues

Issue Project State Summary Similarity
#3743 pack: check skeleton snapcraft merged Merged #3743, adding an explicit snap pack --check-skeleton validation step until snap pack performs skeleton checks natively.
79%
#1871109 snapcraft should check file creation permissions and warn/error out instead of generating a non-functional snap snapcraft (launchpad) closed Snapcraft now validates the snap skeleton and fails before producing an unusable artifact; merged in canonical/snapcraft#3743 (7c927032d).
74%
#1862242 license: field in meta/snap.yaml is not validated store-side snapcraft (launchpad) closed Fixed by merged snapcore/snapcraft#3137 (2515447f5), which changed skeleton validation to invoke an explicit snap executable with --check-skeleton.
71%
#1697468 snapcraft doesn't validate plugs: values snapcraft (launchpad) open Snapcraft accepts malformed plug entries such as plugs: [home x11] and fails later during publishing; maintainers acknowledged the diagnostic gap, but no implemented fix is evidenced.
70%