From 8e5f5efc70680128545d26864263e5628fc74276 Mon Sep 17 00:00:00 2001 From: sommerfeld Date: Thu, 14 May 2026 12:29:15 +0100 Subject: fix(remote-dev): install basedpyright outside Mason Mason's pypi distribution of basedpyright pulls nodejs-wheel-binaries which only ships manylinux_2_28 Linux wheels. uv's python-build- standalone interpreter is tagged manylinux2014 (glibc 2.17 for max portability) and rejects those wheels; pip then falls back to building Node 24 from source, which fails on Ubuntu 20.04's gcc 9.4 (needs gcc >=10 for -std=gnu++20). Provide basedpyright via the system package manager instead: - pacman on Arch (added to meta/base.txt) - pkgs.basedpyright on the VM (added to remote-dev/home.nix) Drop it from mason-tool-installer's ensure_installed; lspconfig picks it up from PATH. Document the exception in remote-dev/README.md. --- remote-dev/README.md | 28 +++++++++++++++++----------- 1 file changed, 17 insertions(+), 11 deletions(-) (limited to 'remote-dev/README.md') diff --git a/remote-dev/README.md b/remote-dev/README.md index 00640b5..2e92509 100644 --- a/remote-dev/README.md +++ b/remote-dev/README.md @@ -135,18 +135,24 @@ git log --show-signature -1 from GitHub on first start. Mason will also fetch LSP servers using `nodejs`/`uv` from this profile. - **Mason pip installs need a managed `python3.11`**: a handful of Mason - packages (basedpyright, autotools-language-server, codespell, mdformat, + packages (autotools-language-server, codespell, mdformat, nginx-language-server, systemdlint, yamllint) install themselves into - per-pkg venvs via pip. Ubuntu 20.04's `/usr/bin/python3` is 3.8 (too - old; also `basedpyright` pulls `nodejs-wheel-binaries` whose only - Linux wheels are manylinux — rejected by Nix's python, which forces a - source build that needs gcc 12+). `bootstrap.sh` runs `uv python -install 3.11` (uv is in the nix profile) and symlinks the resulting - binary to `~/.local/bin/python3.11`. It's a portable manylinux-aware - CPython, and the versioned name leaves `/usr/bin/python3` untouched. - On an existing VM run `uv python install 3.11 && ln -sf "$(uv python -find 3.11)" ~/.local/bin/python3.11` once, then `:MasonToolsInstall` - (or `:MasonInstallAll`) in nvim. + per-pkg venvs via pip. Ubuntu 20.04's `/usr/bin/python3` is 3.8 — too + old. `bootstrap.sh` runs `uv python install 3.11` (uv is in the nix + profile) and symlinks the resulting binary to + `~/.local/bin/python3.11`. The versioned name leaves + `/usr/bin/python3` untouched. On an existing VM run + `uv python install 3.11 && ln -sf "$(uv python find 3.11)" ~/.local/bin/python3.11` + once, then `:MasonToolsInstall` (or `:MasonInstallAll`) in nvim. +- **`basedpyright` is provided by nix, not Mason**: its pypi distro + pulls `nodejs-wheel-binaries`, which ships only `manylinux_2_28` + Linux wheels. Neither Nix's python nor uv's standalone + (`manylinux2014`-tagged) accepts those, so pip falls back to + compiling Node 24 from source — which fails on Ubuntu 20.04's + gcc 9.4 (needs gcc ≥10 for `-std=gnu++20`). `home.nix` adds + `pkgs.basedpyright`; the matching AUR package (`basedpyright-bin`) + is in `meta/base.txt` for Arch. `mason-tool-installer` no longer tries + to install it (see `dot_config/nvim/lua/plugins/lsp.lua`). - **Ubuntu apt collisions**: Nix-installed binaries appear first in PATH. The leaf-tools policy above exists precisely to keep this shadowing contained to harmless tools. -- cgit v1.3.1