remote parts can't have a custom plugin
Metadata
Current evaluation
Closed without resolution. Remote parts failing to load custom plugins in dependent projects was abandoned due to inactivity. No fix or follow-up was provided.
Suggested action: —
No scores available.
Issue body
If a remote part has a custom plugin in parts/plugins/x-plugin.py, when that part is used in another project it won't use the custom plugin.
Steps to reproduce:
$ snapcraft init
Add after: [erlang]
$ snapcraft
The build will fail because it tries to use snapcraft's autotools plugin, instead of the custom one that is defined in the erlang part.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Remote parts failing to load custom plugins in dependent projects was abandoned due to inactivity. No fix or follow-up was provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a fix. The report detailed that remote parts fail to load custom plugins across projects, causing build failures. With zero comments and no follow-up, the issue was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1645350 Parts depending on other remote parts aren't properly added | snapcraft (launchpad) | closed | Abandoned and closed without resolution. Remote part dependencies failed to parse correctly when referenced via the 'after' directive. The report received no follow-up comments over three years. |