cannot use build snaps that are marked private in the store
Metadata
Current evaluation
Snapcraft cannot use a build-snap that is marked private in the store: it reports the snap as not available on the channel even though snap install succeeds. No maintainer activity for ~6 years; still open.
Suggested action: needs triage
Reason: The issue has zero comments, no labels beyond canonical-bootstack, and no maintainer interaction in ~6 years (last activity 2180 days ago), so it has never been triaged. It is a genuine bug (private build-snap reported as unavailable despite snap install working), not a support question, but I could not confirm via tools whether it was fixed in a newer snapcraft version, so I cannot justify closing it as stale/irrelevant without evidence.
Impact:
45
Quick Win:
18.0
Staleness:
92
Complexity:
60
Confidence:
55
Support Request:
10
Issue body
- have a build snap
- upload to store
- mark private
- try to use it as a build-snap in the snapcraft.yaml
snapcraft will claim the snap is not available even though it can be installed fine via snap install
```
Failed to install or refresh a snap: 'kde-frameworks-5-core18-sdk' does not exist or is not available on the desired channel 'latest/edge'. Use `snap info kde-frameworks-5-core18-sdk` to get a list of channels the snap is available on.
```
Being logged in with the same user in snapd and snapcraft makes no difference, it seems purely related to the snap being private.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
18.0
Staleness:
92
Complexity:
60
Confidence:
55
Support Request:
10
|
needs triage | Snapcraft cannot use a build-snap that is marked private in the store: it reports the snap as not available on the channel even though snap install succeeds. No maintainer activity for ~6 years; still open. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
45
Confidence:
80
Support Request:
10
|
needs triage | Snapcraft fails to access private build snaps during builds despite successful installation via snapd. No maintainer comments or activity for nearly 6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
85
Support Request:
5
|
close stale | snapcraft fails to resolve private build snaps despite successful snap install. Issue remains unlabelled and inactive for nearly six years with no maintainer engagement. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
40
Confidence:
75
Support Request:
10
|
needs triage | Snapcraft fails to resolve private build snaps in snapcraft.yaml despite successful installation via snap command. Issue remains unassessed after over seven years with zero maintainer comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
10
|
close stale | Snapcraft fails to resolve private build snaps in snapcraft.yaml despite successful snap install. Issue is over 7 years old with no maintainer interaction or updates. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2104274 Snapcraft has unclear behavior when providing same build-snap from different channels | snapcraft (launchpad) | open | Bug report: snapcraft resolves build-snap from wrong channel (stable vs candidate). Untriaged, no maintainer response in 527 days. |