It is not possible to install a build-snap with a closed risk
Metadata
Current evaluation
build-snaps with a closed channel (e.g. latest/candidate) crashes with KeyError instead of falling back to the next open risk level; filed by maintainer elopio 9 years ago, zero activity, old internal/repo code path no longer exists in current architecture
Suggested action: close stale
Reason: The issue is 9 years old with zero comments or labels, and the traceback references snapcraft/internal/repo/snaps.py which no longer exists in the current codebase (the internal/ directory has been replaced by snapcraft/parts/, snapcraft/store/, and snapcraft/models/ in a full architectural rewrite). The build-snaps feature still exists (83 hits) but the implementation is entirely different, making the original KeyError unlikely to reproduce in the same form. A maintainer should verify the new build-snaps channel resolution handles closed risks before closing.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
19.25
Staleness:
95
Complexity:
45
Confidence:
55
Support Request:
5
|
close stale | build-snaps with a closed channel (e.g. latest/candidate) crashes with KeyError instead of falling back to the next open risk level; filed by maintainer elopio 9 years ago, zero activity, old internal/repo code path no longer exists in current architecture | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
85
Support Request:
0
|
close stale | Bug report from 2017 where specifying a closed channel for a build-snap causes a KeyError. No maintainer interaction, references outdated Python 3.5 and legacy snapcraft internals. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
45
Confidence:
90
Support Request:
10
|
close stale | Snapcraft throws a KeyError when specifying a closed channel for a build-snap, unlike the snap CLI which falls back. Unaddressed for nearly 9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
5
|
close stale | Snapcraft fails with a KeyError when installing a build-snap from a closed channel. The report provides a traceback and reproduction steps but has received no maintainer response or labels in over eight years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
15
|
close stale | Snapcraft throws a traceback when installing a build-snap from a closed channel, unlike the snap CLI which falls back gracefully. The report has zero comments and no labels, remaining unaddressed and needing triage. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1716054 It is not possible to install a build-snap with the default track | snapcraft (launchpad) | open | Snapcraft build-snaps fails with KeyError when a channel is given without a track (e.g. snap/edge), because the code looks up store channels by the bare channel name instead of track/risk. Old bug, no maintainer response, no labels. |