source-type breaks remote-build
Metadata
Current evaluation
snapcraft remote-build fails when source-type is git because the source directory differs from the working directory, causing go dep to fail. The remote-build command has since been removed from snapcraft, making this issue obsolete.
Suggested action: close stale
Reason: The issue is 2413 days old with zero comments and no maintainer interaction. The snapcraft remote-build command was deprecated and removed in snapcraft 3.x, so the reported failure mode no longer applies to the current codebase. The underlying go dep workflow is also outdated.
Impact:
10
Quick Win:
7.0
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
Issue body
If I have a snapcraft.yaml with
juju:
source: .
source-type: git
then snapcraft remote-build fails because the source code directory is not the same as the working directory and running go dep from the working directory fails since the source is missing.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
10
Quick Win:
7.0
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | snapcraft remote-build fails when source-type is git because the source directory differs from the working directory, causing go dep to fail. The remote-build command has since been removed from snapcraft, making this issue obsolete. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | snapcraft remote-build fails when juju source-type is set to git due to working directory mismatches during dependency resolution. The issue has been inactive for over six years with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | Issue reports that using source-type git in snapcraft.yaml causes remote-build to fail due to a working directory mismatch. No maintainer response or activity for over six years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
35
Confidence:
85
Support Request:
5
|
close stale | Snapcraft remote-build fails with juju source-type git due to directory mismatch. Unlabeled, zero comments, inactive for over six years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
90
Support Request:
15
|
close stale | snapcraft remote-build fails when source-type git is used with the juju plugin. Directory mismatch breaks go dep. Open, unassigned, awaiting triage and fix. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
snapcraft (launchpad)#1860526
(confidence 90%)
Same bug reported on Launchpad (bugs.launchpad.net/bugs/1860526), also open and inactive for over six years with no maintainer response.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1968303 remote-build: support for snap relative sources | snapcraft (launchpad) | open | Remote build fails when a part uses a snapcraft extension path ($SNAPCRAFT_EXTENSIONS_DIR/ros2) as its source, because the remote builder cannot determine the source type. Open since ~2021 with no labels, comments, or maintainer response. | |
| #4883 Using (source-type: git; source: .) does not seem to ever realise files have changed, snap rebuild caches code changes | snapcraft | open | Snapcraft with source-type: git and source: . never detects local file changes, reusing cached source instead of re-pulling. Maintainer confirmed behavior is incorrect but suggested using source-type: local as workaround. Issue is 794 days old with no fix. | |
| #4478 bug: remote-build broke in snapcraft 8.0 | snapcraft | closed | Abandoned after investigation identified a libgit2 issue with large repositories causing SSL/broken pipe errors during remote builds. No fix was implemented. |