Skip to content
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.

Sign up for GitHub

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

Jump to bottom

output path ‘/nix/store/xyz...’ has r:sha256 hash X when Y was expected #15675

Closed
abbradar opened this issue May 24, 2016 · 5 comments
Closed

output path ‘/nix/store/xyz...’ has r:sha256 hash X when Y was expected #15675

abbradar opened this issue May 24, 2016 · 5 comments
Labels
0.kind: question Requests for a specific question to be answered

Comments

@abbradar
Copy link
Member

Issue description

output path ‘/nix/store/yssgbm6zf3gzngpc7fidz7w3ckzzr3fb-linear-8da21dc’ has r:sha256 hash ‘0f4r7ww8aygxv0mqdsn9d7fjvrvr66f04v004kh2v5d01dp8d7f9’ when ‘08l0z6zrlbals2bwc2abbh31j9gf90vgp8sy3dcrp0knc98bgaa1’ was expected

Steps to reproduce

 nix-build -A haskell.packages.ghc801.linear

Technical details

  • Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion) "16.09.git.429463d"

cc @peti

I'm not sure how could this happen -- any ideas?
@peti
Copy link
Member

peti commented May 24, 2016

Maybe you use multiple binary caches that don't agree on the hash of that store path?

@peti peti added the 0.kind: question Requests for a specific question to be answered label May 24, 2016
@peti peti changed the title haskellPackages.linear checksum is invalid output path ‘/nix/store/xyz...’ has r:sha256 hash X when Y was expected May 24, 2016
@abbradar
Copy link
Member Author

abbradar commented May 24, 2016 •
edited
Loading

Hm, strange. Notice that this happens only with linear.....
Oh, I noticed now that linear is pulled from git. I'm not sure however how would this hash change, too. Do you successed building this package?

EDIT: my title was invalid -- this happens with ghc801, not with current default GHC.

@abbradar
Copy link
Member Author

I think I've found the problem: commit 64a072e has likely caused hashes to change. I'll push a fix for linear. This would actually likely change hash of many sources.

@vcunat
Copy link
Member

vcunat commented May 25, 2016

There's a thread about this fetchgit change #15469

@abbradar
Copy link
Member Author

Closed by be5b596

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0.kind: question Requests for a specific question to be answered
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@peti @abbradar @vcunat