← Back to issue list

snapcraft doesn't tell me where to put the .py file for my custom plugin

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1606819
Type
issue
State
open
Author
~zyga
Labels
bitesize custom-plugin ui
Created
Updated
Closed
—

Current evaluation

Legacy custom-plugin diagnostics are obsolete: the 2018 answer required parts/plugins/x_foo.py with plugin: x-foo, and the legacy local-plugin loader was later removed.

Suggested action: close stale

Reason: The reporter's edit identifies the legacy layout as parts/plugins/x_foo.py with plugin: x-foo, and maintainer kyrofa answered the placement question in 2018. Commit ffb164b7a removed snapcraft_legacy, while current registration has no parts/plugins lookup, so the reported diagnostic belongs to a removed subsystem.

Evaluated by: mr-cal-bot

Impact: 24 Quick Win: 3 Complexity: 48 Confidence: 92 Actionability: 28

Issue body

I'm writing a new plugin and the error message I get when the Python file is not in the right location (which I still don't know at this stage) is not very useful: $ snapcraft Searching for local plugin for custom Issue while loading plugin: unknown plugin: custom EDIT: In the end the plugin has to be in "parts/plugins/x_foo.py" and the syntax in snapcraft yams has to bee "plugin: x-foo"

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 24
Quick Win: 3
Complexity: 48
Confidence: 92
Actionability: 28
close stale Legacy custom-plugin diagnostics are obsolete: the 2018 answer required parts/plugins/x_foo.py with plugin: x-foo, and the legacy local-plugin loader was later removed.
stealth/space-bunny-alpha
Impact: 20
Quick Win: 2
Complexity: 45
Confidence: 94
Actionability: 20
close stale Obsolete local custom-plugin error from the legacy snapcraft_legacy era; local plugin discovery has since been removed, and the reported workflow no longer exists in the current codebase.
qwen/qwen3.6-35b-a3b
Impact: 20
Quick Win: 14
Complexity: 10
Confidence: 85
Actionability: 80
close resolved Reporter self-resolved: custom plugin location was parts/plugins/x_foo.py with plugin: x-foo syntax. Note: location has since changed to build-aux per commit 7ca0398c5.
qwen/qwen3.8-27b
Impact: 15
Quick Win: 13
Staleness: 95
Complexity: 15
Confidence: 65
Support Request: 45
close stale Request for a clearer error when a custom plugin's .py file is in the wrong location; author self-resolved in an edit (file goes in parts/plugins/x_foo.py, 'plugin: x-foo'). No maintainer activity for ~8.6 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 90
Support Request: 70
close stale Request to improve snapcraft error messages when custom plugin files are misplaced. Author self-resolved the path/syntax in an edit. Issue is over 8 years inactive.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 75
close stale User reported confusing error messages when placing custom plugin files incorrectly, later self-resolved by documenting the correct path and syntax. No maintainer interaction.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 70
close stale Author reported confusing error messages for custom plugin file placement, but self-resolved the issue by documenting the correct path and syntax. The report is over nine years old with no maintainer engagement.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.