Running nix develop now seems to fail on release-7 branch. #289

New Issue

shareef · 2024-04-23T01:04:26+08:00

shareef commented

2024-04-23 01:04:26 +08:00

I have previously managed to build artiq-zynq but having returned to it recently, I'm seeing the following errors. This is on a clean checkout of the release-7 branch and a brand new Nix installation. I thought I might have corrupted something in my nix env so tried a fresh installation.

shareefj@JALAPINO:~/git/artiq-zynq$ nix develop
error:
       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:9:12:
            8|
            9|   strict = derivationStrict drvAttrs;
             |            ^
           10|

       … while evaluating derivation 'artiq-zynq-dev-shell'
         whose name attribute is located at /nix/store/8drxi4s8n69hdv4mp4jiqsi71yaxv8i6-source/pkgs/stdenv/generic/make-derivation.nix:278:7

       … while evaluating attribute 'buildInputs' of derivation 'artiq-zynq-dev-shell'
         at /nix/store/8drxi4s8n69hdv4mp4jiqsi71yaxv8i6-source/pkgs/stdenv/generic/make-derivation.nix:322:7:
          321|       depsHostHost                = lib.elemAt (lib.elemAt dependencies 1) 0;
          322|       buildInputs                 = lib.elemAt (lib.elemAt dependencies 1) 1;
             |       ^
          323|       depsTargetTarget            = lib.elemAt (lib.elemAt dependencies 2) 0;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: NAR hash mismatch in input 'git+https://github.com/m-labs/misoc.git?ref=refs/heads/master&rev=6d48ce77b6746d3226a682790fbc95b90340986e&submodules=1', expected 'sha256-g4+yeSV+HtWjcllM5wk4vNBUVCXtDOzUSKhxXPT7Fyc=' but got 'sha256-NjicjkygVEciaUkxcpgAyHELiuqqSvbLH8w5sfJMpP0='

I have previously managed to build artiq-zynq but having returned to it recently, I'm seeing the following errors. This is on a clean checkout of the release-7 branch and a brand new Nix installation. I thought I might have corrupted something in my nix env so tried a fresh installation. ``` shareefj@JALAPINO:~/git/artiq-zynq$ nix develop error: … while calling the 'derivationStrict' builtin at <nix/derivation-internal.nix>:9:12: 8| 9| strict = derivationStrict drvAttrs; | ^ 10| … while evaluating derivation 'artiq-zynq-dev-shell' whose name attribute is located at /nix/store/8drxi4s8n69hdv4mp4jiqsi71yaxv8i6-source/pkgs/stdenv/generic/make-derivation.nix:278:7 … while evaluating attribute 'buildInputs' of derivation 'artiq-zynq-dev-shell' at /nix/store/8drxi4s8n69hdv4mp4jiqsi71yaxv8i6-source/pkgs/stdenv/generic/make-derivation.nix:322:7: 321| depsHostHost = lib.elemAt (lib.elemAt dependencies 1) 0; 322| buildInputs = lib.elemAt (lib.elemAt dependencies 1) 1; | ^ 323| depsTargetTarget = lib.elemAt (lib.elemAt dependencies 2) 0; (stack trace truncated; use '--show-trace' to show the full trace) error: NAR hash mismatch in input 'git+https://github.com/m-labs/misoc.git?ref=refs/heads/master&rev=6d48ce77b6746d3226a682790fbc95b90340986e&submodules=1', expected 'sha256-g4+yeSV+HtWjcllM5wk4vNBUVCXtDOzUSKhxXPT7Fyc=' but got 'sha256-NjicjkygVEciaUkxcpgAyHELiuqqSvbLH8w5sfJMpP0=' ```

shareef commented

2024-04-23 04:49:11 +08:00

Poster

This seems to be due to a difference in the flake.lock file for misoc. If I update the narHash field for misoc to the expected value, then it all Just Works.

My Nix knowledge is non-existent so I have no idea how that lock file is constructed. Deleting it and rebuilding didn't help.

This seems to be due to a difference in the `flake.lock` file for `misoc`. If I update the `narHash` field for `misoc` to the expected value, then it all Just Works. My Nix knowledge is non-existent so I have no idea how that lock file is constructed. Deleting it and rebuilding didn't help.

fsagbuya commented

2024-04-23 13:24:43 +08:00

I tried also a clean checkout of release-7 branch, but have not encountered the issue. Can you share the the contents of your flake.lock file before you update it?

I tried also a clean checkout of `release-7` branch, but have not encountered the issue. Can you share the the contents of your `flake.lock` file before you update it?

Sign in to join this conversation.