-
Notifications
You must be signed in to change notification settings - Fork 81
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
Testing with Nix 2.2. #99
Comments
That looks like a problem with the installer itself expecting a different hash of the tarball for installation. I'd suggest to open an issue since it's important to fix this |
OK. You mean opening an issue in the Nix repository itself, right? |
Done. Note that I didn't have more luck when trying to install Nix 2.3 (or Nix 2.3.4) as it failed with a different error (later in the process):
And when trying to reproduce the problem using Travis, I got a different error (https://travis-ci.community/t/cannot-run-travis-with-nix-2-2-or-2-3/12203). With both GitHub Actions and Travis, it starts working fine with Nix 2.3.5, but I have no idea if the reasons it fails are related. |
You'd have to use an older version of the action, as the latest one uses features from Nix 2.3.11 (iirc) to speed up the installation. |
OK thanks for the clarification. I think it'd be worth adding this piece of info (minimal supported Nix version) in the documentation then. |
Hi!
The documentation seems to indicate that it should be possible to run this action with an older Nix version by using the
install_url
input. I've tried testing with Nix 2.2 by settinginstall_url: https://releases.nixos.org/nix/nix-2.2/install
but I've obtained the following error:Is testing with Nix 2.2 supported and if yes how? Otherwise, do you have any suggestion on how to test build a derivation with Nix 2.2? (I am trying to understand why a PR fails in nixpkgs's CI while the same derivation builds fine in GitHub Actions and I suspect that it might be due to the version of Nix since I don't see any other explanation for the inconsistency.)
The text was updated successfully, but these errors were encountered: