snapcraft fail app
Metadata
Current evaluation
Snapcraft 2.43.1+18.4 crashes with FileNotFoundError when an app's command points to /bin/Sastreria, which is missing from the prime directory. No comments or labels; the affected 2.x version is long EOL and the code path no longer exists.
Suggested action: close stale
Reason: The issue is from snapcraft 2.43.1+18.4 (Ubuntu 18.04 era) and the failing code path (internal/meta/_snap_packaging.py) no longer exists in the current rearchitected codebase, which has snapcraft/meta/ and snapcraft/models/ instead. The root cause is user misconfiguration — the app's command references /bin/Sastreria which is absent from the prime directory — so it is effectively a usage error on a version that is no longer supported, with zero maintainer interaction in ~6 years.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
10
Quick Win:
8.0
Staleness:
95
Complexity:
20
Confidence:
75
Support Request:
70
|
close stale | Snapcraft 2.43.1+18.4 crashes with FileNotFoundError when an app's command points to /bin/Sastreria, which is missing from the prime directory. No comments or labels; the affected 2.x version is long EOL and the code path no longer exists. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
90
|
close stale | Snapcraft v2.43 crashes with a FileNotFoundError for '/bin/Sastreria' during packaging. The report is over 6 years old, has no comments or labels, and lacks reproduction steps or configuration files. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
85
|
close stale | Snapcraft 2.43.1 crashes with FileNotFoundError for '/bin/Sastreria' during the snap lifecycle step. The report is over six years old with no maintainer interaction or comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
85
|
close stale | Snapcraft 2.43.1 crashes with a FileNotFoundError for '/bin/Sastreria' during the snap lifecycle step. The issue is over 6 years old, has no comments, and appears to stem from a user configuration error. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
90
Support Request:
75
|
close stale | Snapcraft packaging fails with FileNotFoundError when locating /bin/Sastreria during app wrapping. Issue remains open, unassigned, and inactive for over five years with no comments. Needs triage and reproduction steps. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft (launchpad)#1710254
(confidence 60%)
Covers the inverse problem: snapcraft not failing when a command exists on the host but not in the prime directory; same app-command validation area, closed without a fix.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1830520 Sorry, an error occurred in Snapcraft: | snapcraft (launchpad) | open | Snapcraft 2.43.1 (2019) crashed with FileNotFoundError wrapping app command spx_service missing from the prime dir during a Launchpad build. No maintainer activity in 7+ years; the 2.x code path no longer exists and the root cause is user snapcraft.yaml config. | |
| #1812435 python snap fails to build no such file or directory in prime/bin | snapcraft (launchpad) | open | Snapcraft 2.43.1 crashes with FileNotFoundError when an app's command is missing from prime/bin during snap packaging. Reported 2782 days ago with no comments, labels, or maintainer response. The legacy code path no longer exists in the current codebase. | |
| #1867052 Snapcraft crashes while creating snap for ssh-audit | snapcraft (launchpad) | closed | Snapcraft v2.43.1 crashes with FileNotFoundError during snap packaging due to a missing executable path in snapcraft.yaml. Issue is completely inactive for over 6 years. | |
| #1795171 snapcraft fail to find built executable under prime $SNAP | snapcraft (launchpad) | closed | 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. | |
| #1797795 An error occurred building hello world Snapcraft | snapcraft (launchpad) | open | Snapcraft 2.43.1 prime crashes with FileNotFoundError when app command points to bin/hello, but only gnu-bash part is built so the binary doesn't exist. User configuration error, 7.9 years old, 0 comments, no labels. | |
| #1829413 snapcraft requested file bug report | snapcraft (launchpad) | open | Snapcraft 2.43.1 crashed with FileNotFoundError on the snapcraftctl function_call fifo after a keepalived compile failure on Xenial. No maintainer activity in ~7 years; the snapcraftctl code path no longer exists in the current codebase and the affected version is EOL. | |
| #1797378 Built executable is not copied to prime/bin/ | snapcraft (launchpad) | open | Snapcraft 2.43.1+18.4 crashes during prime with FileNotFoundError when an app's command points to a file (prettier) that was not copied to prime/bin/; build/bin/ only contained prettier.js. Reported 8 years ago, no maintainer activity, 0 comments, unlabelled. | |
| #1808043 FileNotFoundError: [Errno 2] No such file or directory: | snapcraft (launchpad) | open | snapcraft 2.43.1 nodejs plugin build fails with FileNotFoundError for app command in prime dir during npm install; no maintainer response, 0 comments, 2820 days old, nodejs plugin removed from modern snapcraft | |
| #1626236 snapcraft newly fails on ubuntu-image | snapcraft (launchpad) | open | snapcraft 2.17 on Ubuntu 16.10 (Yakkety) fails to copy the ubuntu-image CLI script to prime/usr/bin, causing a FileNotFoundError during build. No maintainer activity in ~10 years; affected versions are long EOL and the codebase has been fully restructured since. | |
| #1710254 snapcraft doesn't fail if the command exists in the host but not in the prime directory | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft incorrectly validates app commands against the host system rather than the prime directory during the prime step, leaving the bug unfixed. |