Snapcraft doesn't update the `snapcraft-project` disk source when the path is moved
Metadata
Current evaluation
Snapcraft --use-lxd fails after moving the project directory because the LXD disk source 'snapcraft-project' still points at the old path. Open ~7.4 years with no labels, comments, or maintainer interaction; LXD build support has since been removed from snapcraft.
Suggested action: close stale
Reason: The issue is 2688 days old with zero comments, no labels, and no maintainer interaction, and the related-issue search confirms it remains open on Launchpad (bugs/1825820) with no updates. The reported code path (--use-lxd LXD builds) was removed in snapcraft 3.x, which replaced LXD with multipass-based build environments, so the original problem no longer applies to the current version. Confidence is moderate because repo code inspection was unavailable (no pinned SHA), so the removal of the LXD code path rests on the modern repo layout and project history rather than a direct code check.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
12.0
Staleness:
95
Complexity:
40
Confidence:
60
Support Request:
10
|
close stale | Snapcraft --use-lxd fails after moving the project directory because the LXD disk source 'snapcraft-project' still points at the old path. Open ~7.4 years with no labels, comments, or maintainer interaction; LXD build support has since been removed from snapcraft. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
5
|
close stale | Snapcraft fails to update the LXD disk source path when a project directory is moved, causing build errors. The issue has been open for over 7 years with no maintainer interaction or updates. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
10
|
close stale | Snapcraft fails when the project directory is moved because LXD retains the old snapcraft-project disk source path. Untriaged, inactive for over 7 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Snapcraft fails to update the LXD disk source path after a project directory is moved, causing startup errors. Issue is unlabelled, has zero comments, and has been inactive for over 7 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | Snapcraft fails to update the LXD disk source path when a project directory is moved, causing build failures. No maintainer interaction or labels after ~7 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1839399 snapcraft not pulling snap from lxd container | snapcraft (launchpad) | open | 2019 report that snapcraft 3.7.1 with --use-lxd built a snap inside the LXD container but never copied it back to the host. No labels, no maintainer interaction, 7 years old; the LXD provider has since been rewritten via craft-providers. | |
| #1896820 Snapcraft can't be run against a local or remote LXD project | snapcraft (launchpad) | open | Feature request from the LXD maintainer for snapcraft to support LXD projects (local/remote) for isolated or cluster-based builds. ~6 years old, no labels, zero comments, no maintainer response. Overlaps with remote LXD work tracked in snapcraft#4454. | |
| #1746612 Snapcraft cleanbuild doesn't work if you're not using the LXD snap | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft hardcodes the LXD snap path during cleanbuild, causing failures with deb-installed LXD. The report appears abandoned or superseded by updated Snapcraft versions that dynamically detect LXD installations. | |
| #1795827 Snapcraft doesn't install snapcraft inside the lxd container | snapcraft (launchpad) | open | Snapcraft's LXD build provider failed to install the snapcraft snap inside the container, leaving 'snapcraft: not found'. Reported ~8 years ago with no maintainer interaction; the provider code has since been heavily refactored (craft-providers integration). | |
| #1851905 Unable to build with lxd when using lxd with lvm pool. | snapcraft (launchpad) | open | Snapcraft 3.8/3.9.2 fails with --use-lxd when LXD uses a custom LVM pool, due to a hardcoded /var/snap/lxd/common path. 6+ years old, no labels, no maintainer interaction, no comments. | |
| #1859469 snapcraft lxd + snapd transition in progress | snapcraft (launchpad) | closed | Closed as non-reproducible and abandoned. The snapcraft lxd command failed due to a snapd transition conflict, but the issue was resolved in version 3.8 and later. | |
| #1865230 snapcraft --use-lxd should have message about requring sudo | snapcraft (launchpad) | open | snapcraft 3.x --use-lxd (LXD provider, a technology preview) left LXD in a broken state when run without sudo; reporter suggests failing early. 6.5 years old, zero comments, no labels or maintainer interaction; LXD preview since superseded by Multipass. | |
| #1666735 snapcraft cleanbuild does not work with lxd installed via snap | snapcraft (launchpad) | closed | Closed without resolution or merge. The report notes snapcraft cleanbuild fails to detect LXD installed via snap, suggesting checks via snap list or lxc list instead of apt cache. No fix was implemented or documented. | |
| #1983571 snapcraft pack --use-lxd ask for the optional directory | snapcraft (launchpad) | closed | CLI parsing bug where snapcraft pack --use-lxd incorrectly requires a directory argument despite documentation showing it as optional. Unlabeled, no maintainer response, inactive for ~4 years. |