Snapcraft reports an error if the executable for a command is provided by a content interface
Metadata
Current evaluation
Snapcraft #1666013 was closed as expired after 60 days of inactivity; no fix or superseding work was recorded.
Resolution: closed stale
Reason: Launchpad janitor closed the report on 2017-05-09 because it had seen no activity for 60 days. No resolving PR or commit was identified.
Evaluated by: mr-cal-bot
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Snapcraft #1666013 was closed as expired after 60 days of inactivity; no fix or superseding work was recorded. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as expired (auto-closed by ~janitor on 2017-05-09 after 60 days of no activity) with no fix; suggestions to allow command executables supplied via content interface mounts were never implemented. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a documented resolution; the request to accept command executables supplied through content-interface mounts received no implementation. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution due to inactivity. Snapcraft still rejects commands using executables provided via content interfaces. No fix or upstream change was implemented. | |
| 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
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1597711 snapcraft: self.run() is inconsistent in providing | snapcraft (launchpad) | closed | Closed as expired/stale on 20 February 2017 after 60 days without activity; no fix, documentation update, or superseding change was recorded. | |
| #1867052 Snapcraft crashes while creating snap for ssh-audit | snapcraft (launchpad) | closed | Closed as stale after prolonged inactivity; no Snapcraft PR or commit was cited as resolving the ssh-audit FileNotFoundError. | |
| #1884683 snapcraft fail app | snapcraft (launchpad) | open | Snapcraft 2.43.1 crashed on missing executable /bin/Sastreria; newer code added invalid-command handling, and the maintainer says the Snapcraft snap fixes it, but no retest was posted. | |
| #1988858 snapcraft trying to install extra package causing conflict | snapcraft (launchpad) | closed | Expired and closed without a fix after 60 days of inactivity; maintainers could not reproduce the conflict and suspected a transient archive state. | |
| #4300 snapcraft fails for python projects if there is no setup.py | snapcraft | closed | Closed as stale in April 2025 without a Snapcraft fix. The reproducer declared bin/cos-alerter, but its packaging metadata did not define a console script; no resolving PR or commit was linked. | |
| #1734231 SnapcraftEnvironmentError is too generic | snapcraft (launchpad) | closed | Closed as stale after 3,235 days without an implementation; maintainer ~mr-cal closed it on 2026-08-14 with no linked fix. | |
| #1602094 snapcraft upload error because of missing short namespace doesn't tell how to solve the problem | snapcraft (launchpad) | closed | Closed as obsolete after the store stopped causing the missing short-namespace error; no Snapcraft fix PR or commit was identified. | |
| #1750642 Snapcraft fails in LXD container on Debian 9 | snapcraft (launchpad) | closed | Closed as stale in September 2026 because Debian 9 and the reported Snapcraft version were outdated; no fixing PR or commit was identified. |