snapcraft fail to find built executable under prime $SNAP
Metadata
Current evaluation
Launchpad #1795171: crash was user error — app command used literal $SNAP/bin/ags. Maintainer @ogra gave the correct YAML (command: bin/ags), reporter confirmed; report later expired for 60 days inactivity.
Resolution: closed not a bug
Reason: No code change was made: maintainer @ogra explained that apps command paths are relative to $SNAP and supplied the corrected snippet ('command: bin/ags'), which the reporter confirmed worked. The bug was then auto-closed by ~janitor on 2018-12-02 with '[Expired for Snapcraft because there has been no activity for 60 days.]'.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Launchpad #1795171: crash was user error — app command used literal $SNAP/bin/ags. Maintainer @ogra gave the correct YAML (command: bin/ags), reporter confirmed; report later expired for 60 days inactivity. | |
| stealth/space-bunny-alpha | — | closed not a bug | Snapcraft 2.43.1 crashed priming because an app command of "$SNAP/bin/ags" is not expanded and is looked up literally. Maintainer @ogra supplied the correct snippet (command: bin/ags); reporter confirmed, then the report expired in Dec 2018. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a recorded fix or explanation after Snapcraft 2.43.1 failed to resolve prime/$SNAP/bin/ags while priming the app executable. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution, likely abandoned. Snapcraft failed to resolve the $SNAP environment variable in the prime directory path, causing a FileNotFoundError during packaging. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments, likely abandoned. The issue reported a FileNotFoundError when Snapcraft failed to expand the $SNAP variable in the prime directory path during build. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution, likely abandoned due to inactivity. Snapcraft incorrectly treated the literal string $SNAP as a directory during the prime step, causing a FileNotFoundError when locating the built executable. No fixes or workarounds were submitted. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. Snapcraft incorrectly used the literal $SNAP string in the prime directory path when wrapping executables, triggering a FileNotFoundError. No fix or discussion was recorded. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1812435
(confidence 45%)
Later Launchpad report of the same class of 'missing prime/bin executable' symptom in Snapcraft 2.43.1, likewise resolved by correcting the apps command path rather than a snapcraft fix.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #1812435 python snap fails to build no such file or directory in prime/bin | snapcraft (launchpad) | open | Snapcraft 2.43.1 fails while priming because apps.command references a missing prime/bin/mockpyairpulse; the supplied YAML lacks evidence about the source package's entry point. | |
| #1794636 Error when building snap package in priming stage | snapcraft (launchpad) | closed | User error: the app's `command:` binary was never installed into prime/, causing FileNotFoundError in _wrap_exe. Reporter copied the built folder/file into prime/ themselves; no Snapcraft fix. | |
| #1875872 snapcraft crashes whenever I try to run it | snapcraft (launchpad) | closed | Closed after the apt-installed Snapcraft package failed; the reporter was directed to remove it and use `snap install snapcraft` instead. | |
| #1797378 Built executable is not copied to prime/bin/ | snapcraft (launchpad) | open | Snapcraft 2.43.1 fails on missing prime/bin/prettier although build/bin contains only prettier.js. The report suggests a command/config mismatch, but lacks project files or maintainer triage. |