-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
swiProlog
with lsp in extraPacks
no longer builds
#336326
Comments
It seems adding This builds: (
with (import (builtins.fetchTarball https://github.com/NixOS/nixpkgs/archive/8cdbfd38e917317cb07e760c8efaf2d0db04b705.tar.gz) {}); let
prolog-language-server = fetchFromGitHub {
owner = "jamesnvc";
repo = "lsp_server";
rev = "v2.2.11";
hash = "sha256-6MYFulJsTTAKVtsFwLJy7Rn1d9ZlrD+EwpH93BA/GgQ=";
};
in
swiProlog.override {
extraPacks = [ "'file://${prolog-language-server}'" ];
}
).overrideAttrs (final: prev: { buildInputs = prev.buildInputs ++ [ git ];}) |
I can confirm that with 9.1.21, swi-prolog + lsp-server builds just fine, even with the latest packaging. Something must indeed have changed upstream. 9.1.22 is the first version that stops building for me. If git is now necessary for pack installation (even if we already pre-cloned everything) it should be a dependency. @JanWielemaker any idea why git became necessary here? |
We can resolve this with a patch to SWI-Prolog to respect I submitted a PR to SWI-Prolog (SWI-Prolog/swipl-devel#1307). If upstream merges this, we can just apply the same patch to stable. |
swi-prolog 9.2.7 backported the PR mentioned above. I've modified the package definition to supply the proper flag which suppresses git use during extraPacks install. |
Describe the bug
It seems that
swiProlog
errors withCould not find executable file "git" in $PATH
when attempting to have jamesnvc/lsp_server inextraPacks
. There has been no updates in the lsp_server. I came across this while trying to update my systems. Currently,swipl --version
saysSWI-Prolog version 9.1.21 for x86_64-linux
, so that was the last build I had with the lsp not causing a build failure.Steps To Reproduce
Steps to reproduce the behavior:
Build log
Additional Context
It seems this started happening in 9.2.5. Works fine on the parent commit.
Notify maintainers
@meditans @matko
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: