Installing snapcraft under a different name causes version mixup
Metadata
Current evaluation
Fixed in Snapcraft 7.4.0: PRs #4084 and #4090 added parallel-install support and ensured builds use the active Snapcraft instance.
Resolution: closed resolved
Reason: PR #4090 was merged as commit d680b8437 and injected the current Snapcraft snap into build instances. The maintainer confirmed both #4084 and #4090 shipped in Snapcraft 7.4.0.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Using snap parallel installs feature on snapcraft causes snapcraft to mix versions.
In the case you do
sudo snap install snapcraft --channel=latest/stable
and
sudo snap install snapcraft --name snapcraft_edge --channel=latest/edge
When calling snapcraft_edge to build a snap, the injected snap for snapcraft is always "snapcraft" and the parallel install used is not considered.
https://github.com/snapcore/snapcraft/blob/main/snapcraft_legacy/internal/build_providers/_base_provider.py#L508
Then in the container, the wrong version of snapcraft is used.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed in Snapcraft 7.4.0: PRs #4084 and #4090 added parallel-install support and ensured builds use the active Snapcraft instance. | |
| qwen/qwen3.8-27b | — | closed resolved | Fixed by PRs #4084 and #4090, which inject the current snapcraft snap into build instances to support parallel installs. Released in snapcraft 7.4.0. | |
| stealth/space-bunny-alpha | — | closed resolved | Parallel-install handling was fixed by merged PR #4088 (commit cb6f3857e), honoring the invoking snap instance instead of always injecting the base snapcraft name. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The parallel install name mismatch in the container provider was not addressed. No fix, merge, or follow-up discussion occurred. | |
| qwen/qwen3.6-35b-a3b | — | — | The snapcraft parallel install version mixup was closed without resolution. With zero comments and over three years of inactivity, the bug was abandoned and remains unfixed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Parallel snapcraft installations caused version conflicts in build containers, as the injected snap defaulted to the base name instead of respecting the custom alias. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. Parallel installation of snapcraft under an alias caused container version mismatches, but the report received no comments or fixes before closure. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#4090
(confidence 100%)
Merged as d680b8437 to inject the current Snapcraft instance into build providers.
-
Related To:
snapcore/snapcraft#4084
(confidence 95%)
Added support for running parallel Snapcraft installations and was released with the fix.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5087 fix: allow parallel installations of signed snapcraft snaps (7.5) | snapcraft | merged | Merged into hotfix/7.5 and released in 7.5.7, fixing parallel installs of signed or store-installed Snapcraft; resolves #4683 and #4927. | |
| #5085 fix: allow parallel installations of signed snapcraft snaps | snapcraft | merged | Merged PR #5085 fixed parallel installation of signed Snapcraft snaps, resolving #4683 and #4927; #5087 backported the fix to hotfix/7.5. | |
| #4683 Cannot use parallel installations of snapcraft if a non-aliased version is not installed | snapcraft | closed | Fixed by merged PR #5085 (main) and backported via #5087 to hotfix/7.5 (7.5.7); craft-providers now inject the aliased snapcraft snap correctly. Upstream bug tracked in craft-application#411. | |
| #1980536 snapcraft unusable on systems not using apt | snapcraft (launchpad) | closed | Snapcraft 7.1.1 fixed startup failures on non-APT systems; the 7.0.8 regression was linked to snapcore/snapcraft#3804. |