← Back to issue list

`go-use` plugin doesn't respect `source-subdir`

View original Github issue

Metadata

Project
craft-parts
Number
#978
Type
issue
State
closed
Author
tigarmo
Labels
Created
Updated
Closed

Current evaluation

Closed without resolution. Only an automated Jira sync comment exists, with no developer response or code changes, indicating the bug was deferred or abandoned.

Suggested action:

No scores available.

Issue body

### Bug Description Some go modules are hosted in subdirs of a git repo; for example, https://github.com/elazarl/goproxy/tree/master/ext has the `github.com/elazarl/goproxy/ext` module but the repo itself is github.com/elazarl/goproxy. One can use `source-subdir` to specify the build subdir, but the `go-use` plugin doesn't respect it. ### To Reproduce . ### part yaml ```shell parts: elazarl/goproxy/ext: override-pull: craftctl default; git checkout a0805db90819 plugin: go-use source: https://github.com/elazarl/goproxy.git source-subdir: ext ``` ### Relevant log output ```shell . ```

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without resolution. Only an automated Jira sync comment exists, with no developer response or code changes, indicating the bug was deferred or abandoned.
qwen/qwen3.6-35b-a3b Closed without resolution. The go-use plugin continues to ignore the source-subdir attribute. No fix or workaround was implemented.
qwen/qwen3.6-35b-a3b The go-use plugin failure to respect source-subdir was closed without resolution. No fix or pull request was submitted, and the report was only synced to Jira before closure.
qwen3.6-35b-a3b-mtp-q6 Closed without resolution. The go-use plugin remains unable to respect the source-subdir parameter. Synced to Jira as CRAFT-3906 with no subsequent fix or update.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#980 fix: use source-subdir in go-use plugin craft-parts merged Merged fix updating the go-use plugin to respect source-subdir. Previously, the plugin ignored this setting, defaulting to the repository root and breaking Go modules in subdirectories. Resolves #978 after CI and approvals.
72%
#1858494 go module plugin assumes go files are in root of part source snapcraft (launchpad) closed Closed without resolution. The go plugin incorrectly assumes source files are in the project root, failing to build binaries from standard cmd/ directories. No comments or fixes were provided, leaving the issue abandoned.
71%