snapcraft should filter out 'adapter' when generating snap.yaml
Metadata
Current evaluation
Closed without resolution. Snapcraft continues to pass the adapter field to snap.yaml, where snapd ignores it. No fix was applied.
Suggested action: —
No scores available.
Issue body
As of https://github.com/snapcore/snapcraft/pull/1420, snapcraft supports:
apps:
foo:
adapter: none
It unfortunately passes this along into the snap.yaml, but snapd doesn't do anything with 'adapter'. Snapcraft should instead filter out 'adpater' when generating snap.yaml. Please see https://forum.snapcraft.io/t/telling-snapcraft-to-skip-generating-wrapper-scripts/1635/5 for details.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft continues to pass the adapter field to snap.yaml, where snapd ignores it. No fix was applied. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The request to filter out the adapter field from snapcraft's snap.yaml generation was abandoned due to inactivity. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1955 meta: make sure adapter does not propagate | snapcraft | merged | Merged to prevent the adapter property from propagating from snapcraft.yaml to snap.yaml, resolving Launchpad bug #1750658. Approved by two reviewers, passed CI, and applied with 26 additions and 2 deletions across two files. |