cannot use build snaps that are marked private in the store
Metadata
Current evaluation
Private or separate-store build snaps remain unavailable through build-snaps/stage-snaps despite working snap installs; the open issue remains valid with no identified fix.
Suggested action: keep open
Reason: The report provides a concrete sequence and exact failure while the equivalent snap install succeeds, and the canonical-bootstack label plus comments from BootStack users confirm real organizational impact. Build snaps are still passed into craft-parts' snap installation path, but no resolving commit was found; confidence is reduced slightly because the report predates the current implementation and lacks a recent-version reproduction.
Evaluated by: mr-cal-bot
Impact:
52
Quick Win:
18
Complexity:
58
Confidence:
86
Actionability:
82
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
52
Quick Win:
18
Complexity:
58
Confidence:
86
Actionability:
82
|
keep open | Private or separate-store build snaps remain unavailable through build-snaps/stage-snaps despite working snap installs; the open issue remains valid with no identified fix. | |
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
15
Complexity:
67
Confidence:
82
Actionability:
78
|
keep open | Private and alternate-store snaps remain unusable as build or stage dependencies despite authenticated snapd installation; long-standing and unresolved. | |
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
13
Complexity:
42
Confidence:
76
Actionability:
58
|
keep open | Snapcraft rejects private Store build snaps as unavailable despite successful snapd installation with the same login; build-snaps remain supported and no resolution is evident. | |
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
18
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. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.