snapcraft remote-build snapcraft.yaml validation too strict
Metadata
Current evaluation
snapcraft remote-build validation rejects empty LD_LIBRARY_PATH in environment, blocking some classic snaps. Issue is 4 years old with no maintainer engagement.
Suggested action: close stale
Reason: This issue has been inactive for over 3 years with no maintainer engagement, labels, or comments. The validation schema and snapcraft behavior have likely changed significantly since this was filed, and the reported error may no longer be reproducible with current versions. The related issue #5017 about 'more strict linting unexpectedly' was fixed via PR #5051, suggesting validation behavior has evolved.
Impact:
40
Quick Win:
28.0
Staleness:
95
Complexity:
30
Confidence:
55
Support Request:
20
Issue body
When attempting to use `snapcraft remote-build` I get this error:
$ snapcraft remote-build --build-on arm64
snapcraft remote-build is experimental and is subject to change - use with caution.
Issues while validating snapcraft.yaml: The 'environment/LD_LIBRARY_PATH' property does not match the required schema: '' is not of type 'number' or '' is too short
Using an empty LD_LIBRARY_PATH is an requirement for some classic snaps [0][1] and building the snap locally or indeed through the Launchpad snap package infrastructure causes no issue.
Why does the `snapcraft remote-build` command impose this restriction, and can it be lifted?
0: https://github.com/juju/charm-tools/blob/977ec1ff795f5a8692f8061fc16aa01adf9478cf/snap/snapcraft.yaml#L14-L23
1: https://github.com/openstack-charmers/octavia-diskimage-retrofit/blob/6de2a47491df9e983b458bc7d24f0e035c55c9c3/snap/snapcraft.yaml#L32-L44
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
40
Quick Win:
28.0
Staleness:
95
Complexity:
30
Confidence:
55
Support Request:
20
|
close stale | snapcraft remote-build validation rejects empty LD_LIBRARY_PATH in environment, blocking some classic snaps. Issue is 4 years old with no maintainer engagement. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
75
Support Request:
10
|
needs triage | snapcraft remote-build rejects empty LD_LIBRARY_PATH in snapcraft.yaml despite local builds accepting it. Unlabelled, zero maintainer comments, inactive for over three years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
needs triage | Reports strict validation in snapcraft remote-build rejecting empty LD_LIBRARY_PATH in snapcraft.yaml, breaking classic snaps. Unlabelled, zero maintainer comments, inactive for over three years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
60
Confidence:
80
Support Request:
10
|
close stale | Reports strict validation in snapcraft remote-build rejecting empty LD_LIBRARY_PATH, which works locally and on Launchpad. Unlabeled, no maintainer comments, inactive for over 3 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
75
Support Request:
10
|
needs triage | Reports strict validation in snapcraft remote-build rejecting empty LD_LIBRARY_PATH in snapcraft.yaml, which is valid for classic snaps. Unlabelled, no maintainer comments, inactive for over 3 years. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
snapcraft#5017
(confidence 60%)
Issue #5017 addressed unexpected validation errors from pydantic 2 migration and was fixed in PR #5051. This issue's validation problem may have been resolved as part of the same effort, though direct evidence is unavailable.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2049617 ubuntu-desktop-installer LD_LIBRARY_PATH not defined anymore | snapcraft (launchpad) | open | Classic snap shell environment no longer sets LD_LIBRARY_PATH, possibly a snapcraft 8.0.1 regression. Untriaged, no maintainer engagement in 961 days. | |
| #2099923 Snapcraft builds are failing: install of snap "snapcraft" failed | snapcraft (launchpad) | open | Snapcraft builds failing due to outdated snapd (2.61) on build infrastructure unable to install core20 base. Issue is 556 days old with no maintainer response. | |
| #1635 snap: remove leaking LD_LIBRARY_PATH | snapcraft | merged | Removed leaking LD_LIBRARY_PATH from the snapcraft-classic wrapper, resolving Launchpad bug #1723208. The variable leaked into the environment, breaking snaps on distros like Trusty, and was redundant given existing rpaths. Approved and merged. | |
| #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. | |
| #1919397 snapcraft doesn't run store checks locally, causing disappointment at upload time | snapcraft (launchpad) | open | Snapcraft should run store validation checks locally (e.g. external symlinks) before upload. Issue is 5+ years old with no comments; a snapcraft lint command was later added, but no evidence it covers this specific check. | |
| #2014963 Snapcraft fails to build snap if Snapcraft itself is installed using `snap try` | snapcraft (launchpad) | open | Snapcraft fails when using snap try due to snapd not allowing file downloads for try-mode snaps. Issue is 1251 days old with no maintainer engagement. | |
| #1583236 snapcraft APT sources checking too strict | snapcraft (launchpad) | open | snapcraft fails builds when APT exits nonzero for non-critical warnings (e.g., outdated hash functions, unsupported PPAs). Unlabelled, zero comments, no maintainer interaction; references obsolete 2015-era sources. |