useless "no such file or directory" message
Metadata
Current evaluation
A confusing snapcraft error message report was closed without comments or resolution, likely abandoned due to prolonged inactivity. No fix or workaround was implemented.
Suggested action: —
No scores available.
Issue body
while running snapcraft I get the following output
Preparing to pull caddy
Pulling caddy
Cloning into '/home/hduran/Develop/snappy/caddy/parts/caddy/src'...
remote: Counting objects: 8769, done.
remote: Compressing objects: 100% (40/40), done.
remote: Total 8769 (delta 17), reused 0 (delta 0), pack-reused 8729
Receiving objects: 100% (8769/8769), 2.18 MiB | 71.00 KiB/s, done.
Resolving deltas: 100% (5775/5775), done.
Checking connectivity... done.
go get -t -d ./github.com/mholt/caddy/...
Preparing to build caddy
Building caddy
go install ./github.com/mholt/caddy/...
Staging caddy
Priming caddy
[Errno 2] No such file or directory: '/home/hduran/Develop/snappy/caddy/prime/bin/caddy'
What am I supposed to do with this information?
I am attaching the snapcraft.yaml which I am aware is wrong but the information provided by the tool is beyond useless.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | A confusing snapcraft error message report was closed without comments or resolution, likely abandoned due to prolonged inactivity. No fix or workaround was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned without resolution after over a year of inactivity. The report of a cryptic missing file error during snapcraft execution received no follow-up or fix. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The report regarding a cryptic snapcraft error message was abandoned, with no fix or follow-up implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution or comments. The vague error message report appears abandoned, with no fix implemented or further discussion. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1628671 Assertion error message with no useful end user information | snapcraft (launchpad) | closed | Abandoned and closed without resolution due to inactivity. The unhelpful snapcraft sign-build error message was never improved. | |
| #1663625 No script named 'snapcraft' | snapcraft (launchpad) | closed | A report of snapcraft failing after apt installation was closed without resolution or comments, indicating the matter was abandoned. | |
| #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. | |
| #1719968 Misleading error messages | snapcraft (launchpad) | closed | Closed without resolution. The report notes that missing dependencies cause snapcraft to output verbose Python tracebacks instead of clear error messages. No fix or follow-up was provided. | |
| #1951910 Refreshing snapd while running snapcraft fails with empty response from server | snapcraft (launchpad) | closed | Closed without comments or resolution after ~78 days. Likely abandoned or marked stale. No fix or workaround was implemented. | |
| #1973146 snapcraftctl build fails with message "expected string or bytes-like object" | snapcraft (launchpad) | closed | Closed without comments or resolution details. Likely abandoned due to inactivity. No fix was implemented or documented for the snapcraftctl build TypeError. | |
| #1615764 Support snapcraft close | snapcraft (launchpad) | closed | The requested snapcraft close command was closed without implementation. It appears abandoned due to prolonged inactivity, with zero comments or development activity after opening. | |
| #1499424 snapcraft throws FileExistsError: with very simple Python snap | snapcraft (launchpad) | closed | Closed without comments or explicit resolution. The FileExistsError during snapcraft stage was likely resolved in a subsequent snapcraft release or abandoned due to inactivity. | |
| #1611541 Bad error when trying to run snapcraft-parser without bzr installed | snapcraft (launchpad) | closed | Closed without resolution. No fix was implemented for the missing bzr error message, and the report appears abandoned due to prolonged inactivity. | |
| #1623279 [Errno 2] No such file or directory: '/home/robru/src/bileto.snap/stage/debian/source' | snapcraft (launchpad) | closed | Closed without resolution. The report details a snapcraft crash during the snap stage caused by a missing debian/source directory. No fix or discussion occurred, leaving the issue abandoned. |