snapcraft remote-build cannot use a custom version of snapcraft
Metadata
Current evaluation
Closed as stale without a fix. A maintainer said Snapcraft developers could tap channel branches; later channel-selection work remains open in canonical/snapcraft#6384.
Resolution: closed stale
Reason: No PR, commit, or release resolved the request. The sole maintainer comment on 2023-08-17 directed developers to tap channel branches, and the issue then saw no activity for years.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Snapcraft remote-build is running in launchpad behind a proxy and probably with other specificities.
Some behaviour might be specific to remote-build.
When fixing a bug in snapcraft that only happens in remote-build, it cannot be tested since remote-build is going to use its own version of snapcraft.
snapcraft remote-build should have a way to transfer/use a local/custom version of snapcraft.
This would allow:
- Debug remote-build specific behaviour
- Add remote-build integration tests in the CI of snapcraft
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed as stale without a fix. A maintainer said Snapcraft developers could tap channel branches; later channel-selection work remains open in canonical/snapcraft#6384. | |
| stealth/space-bunny-alpha | — | closed stale | No custom-build transfer was implemented; the only response said Snapcraft developers could use channel branches, and the issue later closed without a code fix. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a fix after prolonged inactivity. Launchpad bug 2020683 records "Closed without resolution"; no implementing PR or commit was identified. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The request to allow snapcraft remote-build to use a custom snapcraft version for debugging and CI testing was abandoned after no further discussion or implementation. | |
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Request to allow custom snapcraft versions in remote-build for debugging and testing was closed without resolution. Zero comments and no follow-up activity indicate the feature request was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Feature request to allow custom snapcraft versions in remote-build was closed without implementation. Zero comments and no activity indicate the proposal was abandoned. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/snapcraft#6384
(confidence 98%)
Later open enhancement requests a Snapcraft channel setting and environment override in the Launchpad build recipe, matching the original need.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2061517 `remote-build` lacks support for selecting Snapcraft channel | snapcraft (launchpad) | open | remote-build still cannot select or mirror the local Snapcraft channel; valid upstream-dependent feature work remains open, with a GitHub implementation issue tracking it. | |
| #4300 snapcraft fails for python projects if there is no setup.py | snapcraft | closed | Closed as stale in April 2025 without a Snapcraft fix. The reproducer declared bin/cos-alerter, but its packaging metadata did not define a console script; no resolving PR or commit was linked. | |
| #1867052 Snapcraft crashes while creating snap for ssh-audit | snapcraft (launchpad) | closed | Closed as stale after prolonged inactivity; no Snapcraft PR or commit was cited as resolving the ssh-audit FileNotFoundError. | |
| #2104274 Snapcraft has unclear behavior when providing same build-snap from different channels | snapcraft (launchpad) | open | Conflicting build-snap channels can install stable instead of an explicitly requested candidate; maintainers acknowledged the ambiguity, but no fix or conflict-resolution policy is recorded. | |
| #6384 remote-build: set snapcraft's channel in the build recipe | snapcraft | open | Remote-builder should pin Snapcraft's own channel in the Launchpad recipe (e.g. 8.x/stable) and expose an env var override; triaged as enhancement with internal ticket SNAPCRAFT-1397, pending upstream craft-application support. | |
| #1947968 snapcraft missing 22.04 branch | snapcraft (launchpad) | closed | Resolved by opening stable/ubuntu-22.04 and releasing snapcraft revisions 7010 (amd64) and 7013 (s390x), restoring the branch required by the 22.04 package. | |
| #2099923 Snapcraft builds are failing: install of snap "snapcraft" failed | snapcraft (launchpad) | open | Reported Launchpad Bionic non-i386 builds cannot install Snapcraft 7.x/stable because core20 needs snapd 2.61; the issue remains open, untriaged, and unanswered. | |
| #1527036 snapcraft does not take the software source mirror site setting | snapcraft (launchpad) | closed | Closed as stale without a code fix; Snapcraft 0.6~trusty~ppa1 did not honor the Software Center mirror setting. The reporter later identified SNAPCRAFT_LOCAL_SOURCES as a workaround. |