Snapcraft reports an error if the executable for a command is provided by a content interface
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without resolution. Snapcraft continues to reject commands using executables provided via content interfaces. The request was abandoned due to inactivity, with no code changes or official workaround implemented.
Suggested action: —
No scores available.
Issue body
I tried to create a snap with the following definitions in my snapcraft.yaml
plugs:
python3:
interface: content
content: python3
target: python
default-provider: python36-jamesh
apps:
hello:
command: python/bin/python3 $SNAP/hello.py
plugs:
- python3
The idea being that the executable for the command would be provided by another snap via the content interface. Unfortunately, Snapcraft refuses to build my snap because the executable doesn't exist in the snap.
I can work around this by creating a shell script that exec's the program shared via the interface, but it would be nice if I didn't have to work around this check.
Perhaps it would make sense to suppress the error if the executable's path is below a directory that will act as a mount point for the content interface?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft continues to reject commands using executables provided via content interfaces. The request was abandoned due to inactivity, with no code changes or official workaround implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Snapcraft rejects builds when a command executable is provided via a content interface. No fix or implementation was added. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. Snapcraft validation fails when commands reference executables provided by content interfaces. No fix was implemented, and the report was closed due to prolonged inactivity. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1727425 same error for app command not existent and not executable | snapcraft (launchpad) | closed | Closed without resolution. The request to differentiate error messages for missing versus non-executable snapcraft app commands was abandoned due to prolonged inactivity. No fix or merge was implemented. | |
| #1550496 Error message when command can't be found/isn't executable is terrible | snapcraft (launchpad) | closed | Unhelpful error messages for missing or non-executable commands in Snapcraft YAML were not addressed. The report was closed without resolution or a fix, likely abandoned due to age and lack of activity. | |
| #1723965 snapcraft doesn't work | snapcraft (launchpad) | closed | Closed without resolution or comments, indicating abandonment. The reported snap command failure and GL driver errors remain unresolved. | |
| #1699 snapcraft <help> command | snapcraft | closed | Closed without implementation or discussion. No resolution or merge details were provided, indicating the snapcraft help command feature request was abandoned. |