Failed to pull source: unable to determine source type of '/usr/share/snapcraft/extensions/ros2'
Metadata
Current evaluation
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.
Suggested action: keep open
Reason: Maintainer @lengau acknowledged on 2025-10-10 that 'we're not organizing the extension scripts to somewhere where they'd be expected' and created internal ticket SNAPCRAFT-1249, so the issue is triaged and valid. The code still hardcodes Path(sys.prefix)/'share'/'snapcraft'/'extensions' in extension.py, and a community workaround (symlink) was posted 2026-01-29, confirming the bug persists. The Dockerfile was removed in #5063 in favor of the snapcraft-rocks registry, so the fix likely belongs in snapcraft-rocks image packaging, but the underlying path mismatch remains unfixed.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
30.0
Staleness:
55
Complexity:
40
Confidence:
80
Support Request:
10
|
keep 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. | |
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
27.0
Staleness:
50
Complexity:
40
Confidence:
75
Support Request:
10
|
keep open | Snapcraft 8 Docker image (snapcraft-rocks) installs extensions under site-packages but code expects /usr/share/snapcraft/extensions, breaking all extension usage. Triaged, acknowledged by maintainer, workaround via symlink provided, no fix yet. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
55
Complexity:
20
Confidence:
85
Support Request:
0
|
keep open | Bug report for snapcraft Docker image where extension paths are misconfigured, causing build failures. Triaged and acknowledged by maintainers, with a community workaround provided but no official fix yet. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
60
Complexity:
30
Confidence:
85
Support Request:
10
|
keep open | Snapcraft fails to locate extensions in Docker due to a hardcoded path mismatch. Triaged and acknowledged by maintainers, with a community workaround provided but no official fix yet. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
45
Complexity:
25
Confidence:
90
Support Request:
0
|
keep open | Snapcraft fails to locate extensions in Docker due to a hardcoded path mismatch. Triaged and acknowledged. A symlink workaround exists, but a permanent fix remains pending. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
canonical/snapcraft#5721
(confidence 90%)
Same error message and root cause; this issue explicitly states it was initially opened as #5721 and moved here because the Docker image is built in this repo.
-
Related To:
canonical/snapcraft#5063
(confidence 75%)
Removed the in-repo Dockerfile in favor of the snapcraft-rocks registry, shifting where the image packaging (and thus the extensions directory layout) is controlled.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #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. |