snapcraft should filter out 'adapter' when generating snap.yaml
Metadata
Current evaluation
Snapcraft no longer propagates apps.adapter into generated snap.yaml; fixed by merged PR #1955 in commit b93625a37.
Resolution: closed resolved
Reason: Merged Snapcraft PR #1955, commit b93625a37, changed snap.yaml generation to omit the Snapcraft-only apps.adapter field, resolving LP #1750658.
Evaluated by: mr-cal-bot
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Snapcraft no longer propagates apps.adapter into generated snap.yaml; fixed by merged PR #1955 in commit b93625a37. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #1955 (commit b93625a37), which prevents the snapcraft.yaml-only apps.adapter field from propagating into generated snap.yaml. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed: apps.adapter from snapcraft.yaml is now stripped from snap.yaml when generating metadata. Resolved by merged PR #1955 (Launchpad #1750658). | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #1955 (commit b93625a37), which filters the snapcraft-only apps.adapter field from generated snap.yaml. | |
| 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
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#1955
(confidence 100%)
The merged PR explicitly fixed this Launchpad issue.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1955 meta: make sure adapter does not propagate | snapcraft | merged | Merged PR #1955 fixed snap.yaml generation so the snapcraft.yaml-only apps.adapter field is not propagated, resolving LP #1750658. | |
| #2853 meta: do not set snapcraft-runner when adapter is "none" | snapcraft | merged | Merged PR #2853 fixed app metadata handling so adapter: none does not add snapcraft-runner to command-chain; full and legacy adapters still do (commit 9599497fb). | |
| #1860873 Regression: No difference between "legacy" and "full" app adapter | snapcraft (launchpad) | closed | Snapcraft's automatic wrapper/command-chain handling made adapter obsolete; merged PR #3741 (commit 46a3e90be) deprecated it. The legacy/full distinction was ultimately removed, not restored. |