Snapcraft doesn't always copy the host's version into the VM
Metadata
Current evaluation
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.
Suggested action: close stale
Reason: The issue is 6.5 years old with zero comments and no maintainer interaction. The specific error (gnome-3-34 schema mismatch) and snapcraft version (3.10, 2020-03-03) are from a very old codebase. Related PRs #1364 (inject host snapcraft into container) and #1412 (snapcraft refresh in containers) have been merged, addressing the core concern of version consistency between host and VM. The LXD provider has since been substantially reworked via craft-providers, making the original reproduction steps and error messages no longer applicable.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18.0
Staleness:
95
Complexity:
40
Confidence:
60
Support Request:
10
|
close stale | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
20
|
close stale | Snapcraft VM version sync fails to copy host version during builds. Issue remains open after 6+ years with zero maintainer interaction or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
20
|
close stale | Snapcraft VM version mismatch causing build failures. Unaddressed for over 6 years with no maintainer interaction or comments. Likely outdated given current snapcraft versions. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Reports periodic build failures when the snapcraft VM version refreshes to stable instead of copying from the host. Unlabeled, zero comments, and inactive for over 6 years since March 2020. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
45
Confidence:
90
Support Request:
10
|
close stale | Unresolved report that snapcraft VM synchronization fails to copy host version, causing build failures. No maintainer response or activity in over 6 years. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/snapcraft#1364
(confidence 70%)
Merged PR that injects the host's snapcraft and core snaps into LXD containers to ensure build version consistency, directly addressing the issue's complaint about not copying the host version.
-
Related To:
canonical/snapcraft#1412
(confidence 60%)
Merged PR implementing snapcraft refresh for LXD containers, related to the refresh behavior described in the issue.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1893850 Snapcraft doesn't inject itself into build VM if host rev doesn't change | snapcraft (launchpad) | open | 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. | |
| #1869542 snapcraft unable to find snap/snapcraft.yaml file | snapcraft (launchpad) | open | snapcraft 3.11 (2019) loses snap/snapcraft.yaml after a few builds and drops to the VM shell; workaround is snapcraft clean. 6+ years old, no labels, no maintainer comments, tied to a long-superseded build environment. | |
| #2104274 Snapcraft has unclear behavior when providing same build-snap from different channels | snapcraft (launchpad) | open | Bug report: snapcraft resolves build-snap from wrong channel (stable vs candidate). Untriaged, no maintainer response in 527 days. | |
| #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. | |
| #1638840 snapcraft copies /etc/apt/sources but ignores /etc/apt/preferences | snapcraft (launchpad) | open | Snapcraft copies /etc/apt/sources but ignores /etc/apt/preferences, causing wrong package selection in complex setups. 9.8 years old, zero comments, no labels, no maintainer interaction. Current codebase uses craft-archives with AptPreferencesManager, a completely different architecture. |