Don't assume lxd from dpkg
Metadata
Current evaluation
Linked PR canonical/snapcraft#904 was closed unmerged as stale in Feb 2017; dpkg-only LXD detection was later fixed by merged #1199 (417989880).
Resolution: closed stale
Reason: canonical/snapcraft#904 was closed unmerged as stale on 6 February 2017 after prolonged inactivity, so it did not resolve the reported behavior. A later duplicate, snapcraft#1666735, was fixed by canonical/snapcraft#1199 at commit 417989880.
Evaluated by: mr-cal-bot
No scores available.
Issue body
The “snapcraft cleanbuild” command checks the dpkg status database to see if the lxd package is installed. I don't have the lxd package installed; instead, I've got the lxd snap installed.
“snapcraft cleanbuild” would work fine if it tried, but it errors out before trying.
https://github.com/snapcore/snapcraft/pull/904
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Linked PR canonical/snapcraft#904 was closed unmerged as stale in Feb 2017; dpkg-only LXD detection was later fixed by merged #1199 (417989880). | |
| stealth/space-bunny-alpha | — | closed stale | The linked pylxd proposal #904 was closed unmerged as stale on 6 February 2017 after prolonged inactivity, so it did not resolve cleanbuild’s dpkg-based LXD detection. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed by merging PR #904, which updated the cleanbuild command to detect LXD installed via snap instead of relying solely on the dpkg database. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved via merged pull request #904, updating snapcraft cleanbuild to detect LXD installed via snap rather than only checking dpkg. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed by merging PR #904, which updated snapcraft cleanbuild to detect LXD installed via snap instead of relying solely on the dpkg status database. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed via PR #904. Snapcraft cleanbuild now detects LXD installed via snap rather than assuming dpkg, resolving the pre-flight check failure for snap-based LXD environments. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/snapcraft#904
(confidence 100%)
Directly linked proposal; it was closed unmerged as stale.
-
Likely Fixed By:
canonical/snapcraft#1199
(confidence 100%)
Merged packaging-independent LXD detection in commit 417989880.
-
Related To:
snapcraft (launchpad)#1666735
(confidence 99%)
Later report of the same cleanbuild failure with LXD installed via snap; closed by the #1199 fix.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1912 lxd: unset SNAP to work-around LXD deb thinking it's a snap | snapcraft | closed | The SNAP-unset workaround for LP #1746612 was rejected and PR #1912 was closed unmerged; no Snapcraft fix landed. | |
| #1666735 snapcraft cleanbuild does not work with lxd installed via snap | snapcraft (launchpad) | closed | Fixed by merged canonical/snapcraft#1199 (commit 417989880), making cleanbuild LXD detection packaging-independent instead of relying on apt package metadata. | |
| #1199 cleanbuild: packaging independent detection. | snapcraft | merged | Merged in canonical/snapcraft#1199 (commit 417989880), replacing repo-based LXD checks with packaging-independent detection and moving the logic into the LXD module. | |
| #1550381 lxd should be a suggestion, not a direct dependency | snapcraft (launchpad) | closed | LXD was changed from a direct dependency to a suggestion in canonical/snapcraft PR #343 (commit 7147a43ba), resolving Launchpad #1550381. |