Go plugin breaks with snapcraft.yaml in tree
Metadata
Current evaluation
Closed without comments, likely abandoned or superseded. Subsequent plugin updates fixed the infinite recursion by avoiding recursive symlinks and enforcing explicit build targets when snapcraft.yaml is in the project tree.
Suggested action: —
No scores available.
Issue body
The Go plugin breaks if snapcraft.yaml is inside the Go project tree itself.
Problem is this: $GOPATH is set to parts/myproject/go, source code is symlinked into parts/myproject/go/myproject pointing to the root of myproject. Root of myproject contains parts/myproject/go. That means there's an infinite recursion, and when the Go snapcraft plugin attempts to build go get -t -d ./myproject/... it explodes in all kinds of funny ways because it recursively finds the $GOPATH source code again as myproject/parts/myproject/go/src/myproject/parts/myproject/go/src/myproject/<ad infinitum>.
Possible solutions:
1. Don't recursively symlink
2. Don't blindly build recusively, but rather ask to explicitly state what to build
I would very much prefer 2, because otherwise we'll soon see other bugs being reported about people struggling with trying to build a small thing out of a big tree and being unable to because snapcraft blindly builds it all. Been there before in other contexts.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments, likely abandoned or superseded. Subsequent plugin updates fixed the infinite recursion by avoiding recursive symlinks and enforcing explicit build targets when snapcraft.yaml is in the project tree. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution, likely abandoned. The Go plugin broke due to infinite recursion when snapcraft.yaml resided in the project tree, causing symlinked source paths to loop during builds. No patch was applied. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1561546 Snapcraft clean removes local plugins | snapcraft (launchpad) | closed | Closed without a documented fix or resolution. The bug where snapcraft clean incorrectly removes local plugins remains unaddressed, likely abandoned due to prolonged inactivity. | |
| #1878498 [snapcraft 4.x] snapcraft fails when building parts with plugins that define custom config | snapcraft (launchpad) | closed | Reported snapcraft 4.x build failure with custom plugin configs was closed without a fix. Zero comments and labels indicate the report was abandoned or marked unactionable. | |
| #1614913 FAIL: test_dump_symlinks (snapcraft.tests.test_plugin_dump.DumpPluginTestCase) | snapcraft (launchpad) | closed | Reported a failing symlink test during snapcraft build. Closed without comments or resolution, likely abandoned or superseded by newer versions. |