← Back to issue list

using executable from core snap fails sanity check

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1751828
Type
issue
State
open
Author
~ondrak
Labels
—
Created
Updated
Closed
—

Current evaluation

App commands provided by the core/base snap fail the sanity check because snapcraft validates them against the host; unlabelled, no maintainer response in ~8.6 years, needs triage against current code.

Suggested action: needs triage

Reason: The issue is a plausible, well-argued build blocker with a concrete reproducer (the reporter links a snapcraft.yaml using 'ping' from core and states the workaround: 'install desired executable on building host'), but it carries no labels, zero comments, and no maintainer response, so it has never been triaged. My repository tooling failed for this project (grep/git_log_search returned "No pinned SHA available for project 'charmcraft'" and read_file failed with git exit status 128), so I could not confirm whether the host-based command validation still exists in the current snapcraft codebase, and the ~8.6-year age with a total rewrite of the meta/apps and linters code means its present validity is genuinely unknown — not something I can mark resolved on age alone.

Evaluated by: mr-cal-bot

Impact: 40 Quick Win: 8 Complexity: 60 Confidence: 35 Actionability: 50

Issue body

When using executable from core snap for application command, snapcraft will fail with sanity check. Example of using 'ping' is here: https://github.com/kubiko/avahi-client/blob/master/snap/snapcraft.yaml Workaround is to install desired executable on building host, then check passes. Suggesting snapcraft checks against host, which seems wrong. Surely check should be against core + content of the snap itself (ignoring confinement restriction for binaries in core)

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 40
Quick Win: 8
Complexity: 60
Confidence: 35
Actionability: 50
needs triage App commands provided by the core/base snap fail the sanity check because snapcraft validates them against the host; unlabelled, no maintainer response in ~8.6 years, needs triage against current code.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 9
Complexity: 50
Confidence: 60
Actionability: 60
needs triage Snapcraft fails sanity check when using executables from core snap; suggests checking against core + snap content instead of host only.
qwen/qwen3.8-27b
Impact: 35
Quick Win: 21
Staleness: 95
Complexity: 40
Confidence: 55
Support Request: 10
close stale Snapcraft's sanity check fails when an application command references an executable provided by the core snap (e.g., ping). Workaround: install the binary on the build host. Unanswered since 2017. Old host-based check likely obsolete in modern snapcraft.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 95
Support Request: 15
close stale Snapcraft fails a sanity check when referencing executables from the core snap. Reported over 8 years ago with no maintainer response or updates.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 40
Confidence: 90
Support Request: 10
close stale Snapcraft sanity check fails when using executables from core snaps. Reported over 8 years ago with zero maintainer interaction or updates.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 35
Confidence: 85
Support Request: 10
close stale Snapcraft fails sanity checks when using executables from the core snap. Unlabelled, unresponded to, and inactive for over 8 years.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.