See 1e71cad6e4/maintainers/scripts/pluginupdate-py/pluginupdate.py (L487).
This line checks the plugin's name and normalizes it before checking with `to_update`.
`to_update` is a raw list of packages you want to update.
Thus, calling `vim-plugins-updater update "package-name"` filters `current_plugin_specs`, removing all `PluginDesc` with *normalized* names that do not match `to_update`
Hence, updating something like "mini.nvim" does not work as the filter expects normalized names. Using "mini-nvim" instead works as intended
GDC 11 was the last version that could bootstrap without a D compiler,
and GDC don’t offer their own binaries any more. GCC 11 is now
end‐of‐life and being removed (as is GCC 12, even).
It’s possible that we could use another distribution’s binary
packages to bootstrap this, or go via our DMD package (it’s
apparently not possible to bootstrap GDC with LDC, but I’m not sure
about DMD), but as nobody has worked on it in the three years since
GCC 12 came out, it seems like interest is limited, and it’s more
of a yak shave than I’m up for right now.
A full from‐source bootstrap chain would of course be nice, but is
more the realm of the minimal bootstrap work than something we’d
want to keep GCC 11 around in the main package set indefinitely for.
Explicitly provide a default value for the argument `enabledTestPaths`
as the current working directory (`enabledTestPaths = [ "." ]`)
to simplify overriding (making `enabledTestPaths` always specified as a
non-empty list) while preserving `pytest`'s default behaviour of
discovering tests in the current working directory.
Assert the specified `enabledTestPaths` value to be a non-empty list.
GHC 9.10.2 seems to be unaffected by the i686 issue, so we can use 9.10
almost everywhere, c.f. https://gitlab.haskell.org/ghc/ghc/-/issues/25904.
haskellPackages: stackage LTS 23.27 -> LTS 24.2
all-cabal-hashes: 2025-07-07T21:33:55Z -> 2025-07-28T06:22:26Z
Make sure to retain Cabal and Cabal-syntax == 3.14.* which is currently
used by cabal2nix-unstable.
