remote-build: support for snap relative sources
Metadata
Current evaluation
ROS 2 parts sourcing files from SNAPCRAFT_EXTENSIONS_DIR build locally but fail remote-build because the variable path is treated as an unknown source type; the report remains unconfirmed.
Suggested action: needs triage
Reason: The report is open, unlabeled, and has no maintainer response, so it has not been assessed. The exact error and part definition make a valid remote-build limitation plausible, but no Snapcraft version, current reproduction, or confirmed expected handling of SNAPCRAFT_EXTENSIONS_DIR is provided.
Evaluated by: mr-cal-bot
Impact:
35
Quick Win:
7
Complexity:
65
Confidence:
76
Actionability:
55
Issue body
My part is:
```
parts:
ros2-galactic-extension:
build-packages: [ros-galactic-ros-core]
override-build: install -D -m 0755 launch ${SNAPCRAFT_PART_INSTALL}/snap/command-chain/ros2-launch
plugin: nil
source: $SNAPCRAFT_EXTENSIONS_DIR/ros2
```
It uses source from snapcraft. This works fine locally but When I try remote-build, I get:
```
Failed to pull source: unable to determine source type of '$SNAPCRAFT_EXTENSIONS_DIR/ros2'.
Check that the URL is correct, or consider specifying `source-type` for this part. See `snapcraft help sources` for more information.
```
I couldn't find `source-type` that would work for my case.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
7
Complexity:
65
Confidence:
76
Actionability:
55
|
needs triage | ROS 2 parts sourcing files from SNAPCRAFT_EXTENSIONS_DIR build locally but fail remote-build because the variable path is treated as an unknown source type; the report remains unconfirmed. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
13
Complexity:
58
Confidence:
91
Actionability:
76
|
needs triage | ROS 2 parts using $SNAPCRAFT_EXTENSIONS_DIR/ros2 fail only in remote-build with an unknown-source-type error; the report remains open, unlabeled, and without maintainer feedback. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18
Staleness:
95
Complexity:
55
Confidence:
60
Support Request:
15
|
needs triage | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
80
Support Request:
20
|
close stale | Remote build fails when using snapcraft extension paths as sources. No maintainer response or labels after over four years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
20
|
close stale | Request to support snapcraft extension relative sources in remote-build. Open 4+ years with zero maintainer interaction. Likely obsolete due to significant changes in snapcraft's remote build and extension systems. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
60
Confidence:
80
Support Request:
20
|
close stale | Remote-build fails to resolve snapcraft extension directories as relative sources. Unlabelled and inactive for over four years with no maintainer response. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #6287 remote-build: support build paths | snapcraft | open | Triaged enhancement to let remote-build select a nested snapcraft.yaml via --project-dir; upstream support is complete, but Snapcraft implementation and spread coverage remain. | |
| #1106 remote-build: support `build_path` for snaps | craft-application | closed | Closed as triaged after narrowing support to remote-build --project-dir; Snapcraft-side implementation remains in canonical/snapcraft#6287. |