Remote parts can't depend on other remote parts
Metadata
Current evaluation
Closed as abandoned due to inactivity. Snapcraft does not automatically pull in dependent remote parts, requiring manual specification in the snap.yaml.
Suggested action: —
No scores available.
Issue body
We have a remote part called alsa, which (up until recently) had two other parts it needed called alsa-libs and alsa-plugins. All three parts are in one remote github repo. https://github.com/diddledan/snapcraft-alsa
In a previous revision of that repo, alsa had an after: [alsa-plugins, alsa-lib] section.
In my own yaml, I reference the 'alsa' part only, expecting it to pull in the alsa-lib and alsa-plugins parts too. Unfortunately when building, it fails to pull the additional parts.
As a workaround I now have to specify all three (alsa, alsa-lib, alsa-plugins) in my own yaml.
Should snapcraft not do the right thing and pull each dependent part in?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed as abandoned due to inactivity. Snapcraft does not automatically pull in dependent remote parts, requiring manual specification in the snap.yaml. | |
| qwen/qwen3.6-35b-a3b | — | — | Remote snapcraft parts cannot automatically pull dependent remote parts. The request was closed without resolution and abandoned due to inactivity. Users must manually specify all remote dependencies in their configuration. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned without resolution. Snapcraft does not automatically resolve dependencies between remote parts, requiring manual specification of all required parts in the main YAML. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution or comments. Remote part dependency resolution was abandoned or superseded by updated Snapcraft behavior requiring explicit dependency declarations. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1800057 Remote parts don't seem to work in snapcraft 3.0 | snapcraft (launchpad) | closed | Closed without resolution. The report details a build failure with 'desktop-launch' when using remote parts in snapcraft 3.0, but received zero comments and no fix. | |
| #1531481 snapcraft should setup search paths/flags for parts built after parts | snapcraft (launchpad) | closed | Closed without resolution. The request to auto-configure search paths for dependent parts was abandoned. Later snapcraft updates added native environment propagation and part dependency handling, rendering the feature obsolete. | |
| #1816397 Modifying snapcraft.yaml with parts using local sources get dirty | snapcraft (launchpad) | closed | Closed without resolution or comments. Appears abandoned, with no fix or workaround implemented. | |
| #1804067 Remote part always considered 'pull step changed' after modifying files in local tree | snapcraft (launchpad) | closed | Closed without resolution, likely abandoned due to inactivity. The report described a snapcraft bug where local file modifications incorrectly triggered a ccache remote part rebuild, causing unnecessary dependent part cleanups. |