"snapcraft help <plugin>" fails with SC7 and core22 in project directory
Metadata
Current evaluation
snapcraft help <plugin> validates snapcraft.yaml unnecessarily, failing when core22 extensions are used. Untriaged, 1445 days old, no maintainer engagement.
Suggested action: needs triage
Reason: The issue has no labels, no maintainer comments, and no assignee after 1445 days. While the reported bug (help command validating snapcraft.yaml when it shouldn't need to) appears legitimate and the fix likely involves skipping validation for help-only commands, no maintainer has assessed it yet. The issue remains potentially relevant as core22 extensions may still be in use.
Impact:
50
Quick Win:
35.0
Staleness:
95
Complexity:
30
Confidence:
65
Support Request:
10
Issue body
In a 22.04 LXD container running SC7, running:
# snapcraft help <plugin>
fails if you are in the context of a snapcraft build directory whose snapcraft.yaml file refers to a core22 extension.
As an example, if I am in an arbitrary directory in my container (say home), then this works:
# snapcraft help catkin
Displaying help for the 'catkin' plugin for 'core20'.
The catkin plugin for ROS 1 parts.
.. and so on ...
However, if I happen to be in my ROS2/Humble project directory, where the snapcraft.yaml file incorporates the ros2-humble extension, then:
# snapcraft help catkin
Issues while validating snapcraft.yaml: The 'apps/ros2-talker-listener/extensions[0]' property does not match the required schema: 'ros2-humble' is not one of ['flutter-stable', 'flutter-beta', 'flutter-dev', 'flutter-master', 'gnome-3-28', 'gnome-3-34', 'gnome-3-38', 'kde-neon', 'ros1-noetic', 'ros2-foxy']
It seems clear(?) that, even though I am simply asking for some help, snapcraft insists on validating my snapcraft.yaml file and chokes on a core22 extension (this is already a known bug). This seems unnecessary -- simply asking for help should not dictate doing anything other than displaying that help.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
50
Quick Win:
35.0
Staleness:
95
Complexity:
30
Confidence:
65
Support Request:
10
|
needs triage | snapcraft help <plugin> validates snapcraft.yaml unnecessarily, failing when core22 extensions are used. Untriaged, 1445 days old, no maintainer engagement. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
0
|
needs triage | snapcraft help <plugin> incorrectly validates snapcraft.yaml when displaying help, failing with core22 extensions. Unlabelled, zero maintainer comments, inactive for ~3.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Bug report: 'snapcraft help <plugin>' fails with SC7/core22 in project directory due to snapcraft.yaml validation. No maintainer response yet. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | snapcraft help <plugin> incorrectly validates snapcraft.yaml in the current directory, failing on unsupported core22 extensions. Issue is unlabelled, has zero comments, and has been inactive for over 3 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
85
Support Request:
5
|
needs triage | snapcraft help <plugin> incorrectly validates snapcraft.yaml in the current directory, failing on core22 extensions. Unlabelled, unresponded to, and inactive for over 3 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1986634 "snapcraft extension" does not recognize core22 extensions | snapcraft (launchpad) | closed | The snapcraft extension command failed to recognize core22 extensions despite listing them. It was closed without resolution or comments, indicating abandonment or stale status due to prolonged inactivity. | |
| #4339 "snapcraft extension" does not recognize core22 extensions | snapcraft | closed | The snapcraft extension command was removed from the tool, closing this report. Core22 extension recognition is no longer applicable as the feature was deprecated and deleted. | |
| #6336 Snapcraft 9: snapcraftctl errors in core22 snaps | snapcraft | open | Regression in snapcraft 9: core22 snaps using snapcraftctl in override-build fail validation. Maintainer confirmed as a regression. | |
| #1982761 Meson plugin fails in snapcraft version 7.1.0 | snapcraft (launchpad) | closed | Closed without comments or resolution, the report was likely abandoned or marked stale. The meson plugin environment validation failure in snapcraft 7.1.0 on core22 remains unfixed. | |
| #4285 Snapcraft v7 fails to build core18 snap with local plugins | snapcraft | closed | Snapcraft v7 failed to build core18 snaps with local plugins due to an unredirected snapcraft.sources import. Snapcraft v7.5.3 resolved this by implementing the required legacy import redirection, enabling successful builds. | |
| #2099923 Snapcraft builds are failing: install of snap "snapcraft" failed | snapcraft (launchpad) | open | Snapcraft builds failing due to outdated snapd (2.61) on build infrastructure unable to install core20 base. Issue is 556 days old with no maintainer response. |