Change:
Build . Because this hash was updated not long ago by , I think the package may still need some refactor? We may also expect to get everything settled. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Huh, weird. When I wrote that hash worked fine. I wonder what changed?
Yes I was wondering about the same thing because I knew you updated that hash not long ago. Does that hash depend on any online resources that may change or on other packages? If not, then this package may have some obscure reproducibility issues. This package is so complex that I cannot see what it is doing there at glances.
Yes, but it is my understanding that its pulling resources that are hash-fixed in bazel-land, so iiuc they shouldn't change unless changes... but then again clearly i have some misunderstanding of the behavior here
builds fine for me on .
Is this issue still reproducible for you?
Yes. I just tested on master branch at commit . The exact same error.
Are you using any overlays? Have you set any nixpkgs flags?
I have a local clone of nixpkgs at , and I ran the command Does it depend on my nixos system config?
iirc it will depend on eg but i'm not sure about the nixos system config. What commit of nixpkgs are you on? Does it reproduce on the latest master?
I don't have . I said I was on , which is the latest.
Latest (at the time of writing) is does building on that commit work for you?
That commit does not build either.
Hi, I'm also having the same issue with same hash mismatch. I tested the build on two different systems. If you happen to have a system in which the build runs fine, would you mind sharing the output of the derivation: so I can diff it? I could also send you mine.
Should be fixed by
Fixed by
Hi everyone, sorry to reactivate this issue but if I check out the current master branch and run , I end up with the same error as above (just with different hashes). Can anyone reproduce this behaviour?
what hashes are you seeing now?
I can rebuild the package just fine...
! These are the hashes I get after running on the current master (). I am puzzled by the fact that this exact commands builds fine for . My expectation would have been that the behaviour should be the same if we are on the same platform (I am on x86_64-linux). Do you have an idea how we can dig deeper into this?
I also just stumbled upon this issue and I do get the exact same hash mismatch as :
Well, my only hypothesis is that the bazel dependencies derivation is nothing more than non-deterministic :'(
Does this still build for you? If it does I can offer to send you an archive of my jaxlib with the changed hash so you can run a diff to find out what is wrong. (Or the other way round ofc)
Yes, I have tried once again right now and it works fine... Sure, Send me what you have :)
Alright, I've updated today and will build against nixpkgs . My machine will probably take some time to completely build it though, so I'll post back once it's done.
I'm getting a similar problem when I'm trying to compile . The commit is from the branch. The commit was the only commit I found after going through multiple issues and threads which worked on my system. I have also observed this issue when compiling (), so the issue of build failures due to bazel hash mismatch isn't just limited to . So, I don't think that this issue has been properly resolved yet.
I'm not sure if this is helpful--or noise!--but I just hit a similar issue with (see below for output, repro, and system info).
Btw we're tracking the hash issues in .

Discussion:
sha256 = ( if cudaSupport then <del> { x86_64-linux = "sha256-VGNMf5/DgXbgsu1w5J1Pmrukw+7UO31BNU+crKVsX5k="; } </del> <ins> { x86_64-linux = "sha256-vUoAPkYKEnHkV4fw6BI0mCeuP2e8BMCJnVuZMm9LwSA="; } </ins> else { <del> x86_64-linux = "sha256-uOoAyMBLHPX6jzdN43b5wZV5eW0yI8sCDD7BSX2h4oQ="; aarch64-linux = "sha256-+SnGKY9LIT1Qhu/x6Uh7sHRaAEjlc//qyKj1m4t16PA="; </del> <ins> x86_64-linux = "sha256-R1TIIyyyLlDqAlUkuhJhtyTxZMra2q5S/jX0OCInsEQ="; aarch64-linux = "sha256-P5JEmJljN1DeRA0dNkzyosKzRnJH+5SD2aWdV5JsoiY="; </ins> } ).${effectiveStdenv.system} or (throw "jaxlib: unsupported system: ${effectiveStdenv.system}"); };