`remote-build` lacks support for selecting Snapcraft channel
Metadata
Current evaluation
Feature request to expose Launchpad's snapcraft channel selection API in remote-build, defaulting to the local channel. Untriaged, no maintainer engagement in 871 days.
Suggested action: needs triage
Reason: The issue has no labels, no maintainer response, and zero comments after 871 days. While it's a valid feature request (still relevant per open issue snapcraft#6384), it has never been triaged or acknowledged by a maintainer, so it needs initial assessment before any action can be taken.
Impact:
55
Quick Win:
30.25
Staleness:
75
Complexity:
45
Confidence:
70
Support Request:
15
Issue body
Launchpad has API to choose a channel for Snapcraft:
https://launchpad.net/+apidoc/devel.html#snap_build
> channels (writeable)
> Source snap channels to use for this build.
> A dictionary mapping snap names to channels to use for this build. Supported snap names: 'core', 'core18', 'core20', 'core22', 'core24', 'snapcraft', 'snapd'
Would be good to expose that on `remote-build`, and even better - default to whatever the local Snapcraft channel is, if possible.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
55
Quick Win:
30.25
Staleness:
75
Complexity:
45
Confidence:
70
Support Request:
15
|
needs triage | Feature request to expose Launchpad's snapcraft channel selection API in remote-build, defaulting to the local channel. Untriaged, no maintainer engagement in 871 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
20
Confidence:
80
Support Request:
10
|
needs triage | Feature request to expose Launchpad Snapcraft channel selection in remote-build. Unlabelled, zero maintainer comments, inactive for over two years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
92
Complexity:
20
Confidence:
75
Support Request:
10
|
needs triage | Feature request to expose Launchpad Snapcraft channel selection in remote-build and default to local channel. Unlabelled, zero maintainer interaction, inactive for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
10
|
needs triage | Feature request to expose Launchpad's Snapcraft channel selection in remote-build and default to the local channel. Unlabeled, no maintainer response, inactive for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
20
Confidence:
85
Support Request:
5
|
needs triage | Feature request to expose Launchpad's Snapcraft channel selection API in remote-build and default to the local channel. Unassessed, no comments, inactive for over two years. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft#6384
(confidence 85%)
Open enhancement to allow specifying Snapcraft channel in build recipes via environment variable, still awaiting implementation.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #6384 remote-build: set snapcraft's channel in the build recipe | snapcraft | open | Enhancement to set Snapcraft's channel in remote build recipes and expose an environment variable for channel selection. Triaged, from maintainer, 23 days old. | |
| #1706 Remote build: allow the user to specify a charmcraft channel and default to the charmcraft snap channel | charmcraft | open | Feature request to let users select the charmcraft snap channel for remote builds (CLI option) and default to the installed snap's tracking channel. Open since 2023, last activity July 2024; no channel option exists in remote-build yet. | |
| #3600 remote build: use channel defaults (CRAFT-568) | snapcraft | merged | Merged changes remove hardcoded channel forcing for snapcraft and core18 in remote builds, aligning with snapcraft's core20 transition. Approved and merged with a minimal diff. Launchpad now auto-selects the correct build-base. | |
| #344 remote build: provide a way to set application snap channel | craft-application | open | Enhancement to add an environment variable or option so remote builds can specify which snap channel (e.g. edge) to use for the application snap in Launchpad build recipes. Triaged by maintainer; not yet implemented. | |
| #2020683 snapcraft remote-build cannot use a custom version of snapcraft | snapcraft (launchpad) | closed | Request to enable custom snapcraft versions in remote-build was closed without implementation. No resolution or merge details were provided, indicating the feature was abandoned. |