Installing snapcraft under a different name causes version mixup
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
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.
Suggested action: —
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 |
|---|---|---|---|---|
| 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
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.