Snapcraft doesn't inject itself into build VM if host rev doesn't change
Metadata
Current evaluation
snapcraft skips injecting itself into the build VM when the host snap revision is unchanged after sideloading; reporter suggests using hashes instead of revisions for x-revisions. Unlabelled, zero comments, inactive ~6 years.
Suggested action: needs triage
Reason: Filed by maintainer kyrofa with a clear scenario (sideloaded snapcraft snap keeps revision x1, so the VM gets the stale copy), but has no labels, no comments, and no maintainer acknowledgement in ~6 years. The related issue snapcraft (launchpad)#1865834 ('doesn't always copy the host's version into the VM') suggests a known sibling bug, but no fix commit referencing 1893850 was found, so it hasn't been triaged or resolved.
Impact:
45
Quick Win:
27.0
Staleness:
95
Complexity:
40
Confidence:
70
Support Request:
0
Issue body
I'm developing new snapcraft features. These features require that a snapcraft snap be built (using the stable release of snapcraft). Then that new snapcraft snap needs to be installed (which changes the snapcraft revision to x1). Then I actually run it, a build VM is created, and snapcraft injects itself and continues on its merry way. Then of course I hit a bug, and go through those steps again:
1. Uninstall snapcraft
2. Install snapcraft from stable
3. Build snapcraft with bug hopefully fixed
4. Install new snapcraft (back to revision x1 again)
5. Run snapcraft on test project.
6. Notice bug is still there, as if nothing changed!
That's because it didn't-- snapcraft noticed that it was still on revision x1, and didn't inject the new version, thereby continuing to use the old, buggy version in the build VM. Snapcraft should be checking hashes, not revisions (at least, when the revisions start with "x").
Now, one could point out that (1) should be `snap revert snapcraft`, but that doesn't change the fact that this is still a bug. Besides, actually removing/reinstalling snapcraft after sideloading over the top of it is the only sure-fired way to make sure I'm using the right thing.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
27.0
Staleness:
95
Complexity:
40
Confidence:
70
Support Request:
0
|
needs triage | snapcraft skips injecting itself into the build VM when the host snap revision is unchanged after sideloading; reporter suggests using hashes instead of revisions for x-revisions. Unlabelled, zero comments, inactive ~6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
75
Support Request:
10
|
needs triage | Snapcraft fails to inject itself into build VMs when the host revision remains unchanged after sideloading. The report is unlabelled, has zero comments, and has been inactive for nearly six years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
90
Support Request:
10
|
close stale | Snapcraft fails to inject itself into build VMs when the host revision remains unchanged after reinstalling. Unlabelled, no maintainer response, inactive for nearly 6 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
85
Support Request:
10
|
close stale | Snapcraft fails to inject itself into build VMs if the host revision hasn't changed, despite code updates. Unlabelled, zero comments, and inactive for nearly six years with no maintainer engagement. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
35
Confidence:
80
Support Request:
5
|
close stale | Snapcraft skips injecting itself into build VMs when the revision stays the same after reinstalling, causing it to run stale code. It should check hashes instead. Open, zero comments, inactive for 10 days, awaiting triage and assignment. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft (launchpad)#1865834
(confidence 80%)
Same area: snapcraft not always copying its host version into the VM; likely shares the revision-vs-hash root cause.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #1664704 snapcraft release gives misleading error when revision does not exist | snapcraft (launchpad) | open | snapcraft release shows misleading error suggesting 'snapcraft register' when the real problem is a non-existent revision. Filed 2016, 0 comments, no maintainer interaction; legacy CLI since replaced by craft-based rewrite. |