← Back to issue list

remote-build: support for snap relative sources

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1968303
Type
issue
State
open
Author
~gbeuzeboc
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action: needs triage

Reason: The issue has zero comments, no labels, and no maintainer interaction in over 4 years (1606 days), and the matching Launchpad bug 1968303 is likewise still open with no response. It is a genuine bug report (clear reproduction and error output), not a support question, but it has never been assessed or categorised by a maintainer, so it needs triage rather than closure. I could not confirm via tools whether remote-build source handling has since changed, which limits confidence in any close action.

Impact: 40 Quick Win: 18.0 Staleness: 95 Complexity: 55 Confidence: 60 Support Request: 15

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
qwen/qwen3.8-27b
Impact: 40
Quick Win: 18.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 40
Confidence: 85
Support Request: 20
close stale Remote build fails to resolve $SNAPCRAFT_EXTENSIONS_DIR/ros2 as a source, working only locally. Issue is 4 years old with no maintainer comments or labels.

Update history

No update history recorded yet.

Related work

  • Duplicate Of: snapcraft#1968303 (confidence 70%)

    Launchpad bug 1968303 is the same 'remote-build: support for snap relative sources' report, still open with no maintainer response.

Related issues

Issue Project State Summary Similarity
#6287 remote-build: support build paths snapcraft open Enhancement to add --project-dir support for remote-build command, allowing users to specify build paths when multiple snapcraft.yaml files exist. Issue is triaged and assigned to a contributor after upstream dependency was resolved.
73%
#1860526 source-type breaks remote-build snapcraft (launchpad) open 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.
72%
#109 Failed to pull source: unable to determine source type of '/usr/share/snapcraft/extensions/ros2' snapcraft-rocks open Snapcraft 8 Docker image (ghcr.io/canonical/snapcraft:8_core22) fails to resolve ros2 extension: get_extensions_data_dir() returns /usr/share/snapcraft/extensions but extensions live in site-packages. Triaged, acknowledged by maintainer, workaround shared, still open.
71%
#1106 remote-build: support `build_path` for snaps craft-application closed Accepted and closed. The build_path enhancement for snaps is scoped to the remote-build subcommand for now, with plans to expand to other lifecycle commands later.
70%
#5721 Failed to pull source: unable to determine source type of '/usr/share/snapcraft/extensions/ros2'. snapcraft open Snapcraft 8 Docker image fails to resolve ros2 extension: get_extensions_data_dir() returns /usr/share/snapcraft/extensions but extensions are installed under site-packages/extensions. Untriaged, no maintainer activity in 374 days; same bug tracked in snapcraft-rocks#109.
70%