lxd should be a suggestion, not a direct dependency
Metadata
Current evaluation
LXD was changed from a direct dependency to a suggestion in canonical/snapcraft PR #343 (commit 7147a43ba), resolving Launchpad #1550381.
Resolution: closed resolved
Reason: PR #343 was merged through commit 29d86041b and implemented the change in 7147a43ba, moving LXD from a direct dependency to a suggestion.
Evaluated by: mr-cal-bot
No scores available.
Issue body
As the summary
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | LXD was changed from a direct dependency to a suggestion in canonical/snapcraft PR #343 (commit 7147a43ba), resolving Launchpad #1550381. | |
| stealth/space-bunny-alpha | — | closed resolved | LXD was changed from a direct dependency to a suggestion by merged canonical/snapcraft PR #343 (commit 7147a43ba), resolving the Launchpad item. | |
| stealth/space-bunny-alpha | — | closed resolved | LXD was changed from a direct dependency to a suggestion by merged PR canonical/snapcraft#343 in commit 7147a43ba, resolving Launchpad #1550381. | |
| stealth/space-bunny-alpha | — | closed resolved | LXD was changed from a direct dependency to a suggestion in merged PR canonical/snapcraft#343 (commit 7147a43ba), resolving Launchpad #1550381. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without action; the proposal to change lxd from a direct dependency to a suggested package was abandoned. No implementation or discussion occurred. | |
| qwen/qwen3.6-35b-a3b | — | — | Proposal to reclassify lxd as a suggested dependency rather than a direct one was closed without discussion or implementation. The request was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Request to change lxd from a direct dependency to a suggested one was closed without implementation. Lacking comments or activity for over a decade, the proposal was abandoned and the dependency configuration remains unchanged. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Requesting lxd be converted from a direct dependency to an optional suggestion was closed without comments or resolution. No dependency changes were implemented. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#343
(confidence 100%)
Merged PR that changed LXD dependency classification and resolved this Launchpad issue.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #343 lxd should be a suggestion, not a direct dep | snapcraft | merged | Merged in snapcraft PR #343 as 7147a43ba, changing LXD from a direct dependency to a suggestion and resolving LP #1550381. | |
| #1930 lxd: friendly errror with suggestions if network is broken | snapcraft | merged | Merged in snapcraft#1930 (cdbac658d), replacing raw LXD network-probe failures with friendly errors that include the checked URL and guidance. | |
| #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. | |
| #1728649 LXD not running error message is vague | snapcraft (launchpad) | closed | Enhancement request to improve the vague "Connection refused; is LXD running?" error from `snapcraft cleanbuild`. Discussion stalled over whether to recommend purging the apt lxd package; closed incomplete and later expired by Launchpad janitor with no code change. | |
| #1639641 Don't assume lxd from dpkg | snapcraft (launchpad) | closed | Linked PR canonical/snapcraft#904 was closed unmerged as stale in Feb 2017; dpkg-only LXD detection was later fixed by merged #1199 (417989880). |