Snapcraft has unclear behavior when providing same build-snap from different channels
Metadata
Current evaluation
Bug report: snapcraft resolves build-snap from wrong channel (stable vs candidate). Untriaged, no maintainer response in 527 days.
Suggested action: needs triage
Reason: This is a legitimate bug report with concrete evidence (build logs showing wrong revision path /23/ instead of expected candidate channel revision), but it has zero maintainer engagement, no labels, and no assignee after 527 days. The issue hasn't been triaged — a maintainer needs to assess whether the bug still exists in current snapcraft versions before deciding to keep it open or close it.
Impact:
60
Quick Win:
33.0
Staleness:
85
Complexity:
45
Confidence:
55
Support Request:
15
Issue body
Chromium beta has a dependency on llvm-chromium/candidate.[1]
Currently, these are its releases in the Snap Store:
--->
% snapcraft status llvm-chromium
Track Arch Channel Version Revision Progress
latest amd64 stable 20 22 -
candidate 21 27 -
beta ↑ ↑ -
edge ↑ ↑ -
arm64 stable 20 24 -
candidate 21 25 -
beta ↑ ↑ -
edge ↑ ↑ -
armhf stable 20 23 -
candidate 21 26 -
beta ↑ ↑ -
edge ↑ ↑ -
<---
The log of recently failed Chromium builds indicate that the Store was providing Llvm-chromium from the stable channel rather than from candidate. For example, for Armhf, the log[2][attached] contains this piece of debugging information:
--->
:: + find / -name '*libclang_rt*'
:: /snap/llvm-chromium/23/lib/clang/20/lib/armv7-unknown-linux-gnueabihf/libclang_rt.builtins.a
<---
The path element /23/ demonstrates the snap is coming from the stable channel, contrary to specified in snapcraft.yaml.
This failure was also affecting Amd64, which I wanted to unblock, so I tried
snapcraft release llvm-chromium 27 candidate
, which should be a no-op as that is already the revision in the candidate channel of Amd64, but then a retry on the failed Amd64 build completed successfully.
I decided to preserve the Armhf failed build as evidence of this behavior. Interestingly, the issue did not affect Arm64.
[1]https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=beta#n168
[2]https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta/+build/2759958
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
60
Quick Win:
33.0
Staleness:
85
Complexity:
45
Confidence:
55
Support Request:
15
|
needs triage | Bug report: snapcraft resolves build-snap from wrong channel (stable vs candidate). Untriaged, no maintainer response in 527 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
45
Confidence:
80
Support Request:
15
|
needs triage | Snapcraft fetches build-snap dependencies from the wrong channel when identical revisions exist across multiple channels. Currently unlabelled, awaiting maintainer triage, and inactive for over a year. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
92
Complexity:
55
Confidence:
78
Support Request:
20
|
close stale | Snapcraft incorrectly resolves build-snap dependencies to the stable channel instead of the specified candidate channel during builds. Untriaged, inactive for 16 months with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
40
Confidence:
70
Support Request:
10
|
needs triage | Snapcraft incorrectly resolves build-snap channels when revisions overlap, pulling stable instead of candidate. Unassessed after 15 months with zero maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
45
Confidence:
90
Support Request:
10
|
needs triage | Unlabeled issue reporting snapcraft incorrectly resolves build-snap dependencies to the stable channel instead of the specified candidate channel during builds. Currently untriaged with no maintainer interaction. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1889741 Snapcraft concurrent build | snapcraft (launchpad) | open | Race condition when running multiple snapcraft instances concurrently: both check for $HOME/.cache/snapcraft/download and stage-packages, both see missing, one creates, other fails. Reported ~6 years ago, 0 comments, no maintainer response, no labels. | |
| #2099923 Snapcraft builds are failing: install of snap "snapcraft" failed | snapcraft (launchpad) | open | Snapcraft builds failing due to outdated snapd (2.61) on build infrastructure unable to install core20 base. Issue is 556 days old with no maintainer response. | |
| #2158702 Snapcraft API not answering | snapcraft (launchpad) | open | User reports intermittent API failures from api.snapcraft.io causing build issues. No maintainer response after 67 days. | |
| #2014963 Snapcraft fails to build snap if Snapcraft itself is installed using `snap try` | snapcraft (launchpad) | open | Snapcraft fails when using snap try due to snapd not allowing file downloads for try-mode snaps. Issue is 1251 days old with no maintainer engagement. | |
| #5086 snapcraft status lists several time the same information | snapcraft | open | snapcraft status prints the same track/arch/channel rows multiple times in its table output. Reported against snapcraft 8.4.1 on Ubuntu Oracular; no maintainer response, no labels, no activity since filing ~2 years ago. | |
| #1865834 Snapcraft doesn't always copy the host's version into the VM | snapcraft (launchpad) | open | Snapcraft VM builds intermittently refresh snapcraft to stable channel instead of copying the host version, causing schema validation failures. 6.5 years old, 0 comments, no labels, no maintainer interaction. Related PRs #1364 and #1412 have been merged addressing host version injection and container refresh. | |
| #1983826 Snapcraft 7.1.1 gives vague error when it can't process package | snapcraft (launchpad) | open | Snapcraft 7.1.1 returns a vague 'Service unavailable' error when snap upload processing fails, making it hard for users to diagnose the root cause. No maintainer response or labels; issue is 4 years old. | |
| #1719946 Snapcraft has three unsynced bug lists | snapcraft (launchpad) | open | Snapcraft bug reports were split across Launchpad and GitHub, causing duplicates and unclear prioritization. No activity for ~9 years. The referenced #100 signpost is now closed and the repo uses GitHub issue templates, so tracking has consolidated on GitHub. | |
| #1802327 cannot use build snaps that are marked private in the store | snapcraft (launchpad) | open | 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. | |
| #1548225 Snapcraft/snappy should detect incompatible version mismatches | snapcraft (launchpad) | closed | Abandoned. The report detailed Snapcraft failing to detect version mismatches, causing large snaps to install incorrectly. With zero comments and over a decade of dormancy, it received no resolution and was closed. |