-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
bundler: hash mismatch of source #6326
Comments
Hopefully fixes NixOS#6326 I worry that fetchgit's current implementation isn't quite fully deterministic when leaveDotGit is enabled. Change-Id: Ieece4b6305da759aff3f284f41c0959c5d6375cf
Hopefully fixes NixOS#6326 I worry that fetchgit's current implementation isn't quite fully deterministic when leaveDotGit is enabled. Change-Id: Ieece4b6305da759aff3f284f41c0959c5d6375cf (cherry picked from commit 37d8100)
An update on this issue, I just reproduced the bug on my machine. This time the output hash was different from the first time I tried:
|
@rzetterberg Are you on Linux or Darwin? EDIT: Oops! Just saw your "System specs" you posted earlier. I'll give this some thought... |
@rzetterberg Do you have chroot builds enabled? ( I forget just how impure non-chroot builds are... but a hunch is that custom git hooks could be polluting the checkout. (I think that |
@cstrahan I have not set I checked the bundler repo to see whether there are any git hooks used, and it seems there are no hooks (only samples) in the
|
Chrooting is irrelevant, as AFAIK fixed-output derivations are never chrooted, and they have network access, etc. Better discuss this just on #6409, as there are some more relevant discussions about leaveDotGit. |
That commit probably wasn't affecting this. Anyway, if it works now... |
I'm seeing this same issue today, on the latest unstable |
That's what |
When activating the gitlab service and rebuilding:
Fails with:
System specs
Misc
For convenience here is the link to the latest commit to ruby-bundler: 7d8b2f0#diff-7cde46455d84d468d1a1b9c57fc96287
I does not seem like that commit introduced the problem. The hash was changed from
1f0isjrn4rwak3q6sbs6v6gqhwln32gv2dbd98r902nkg9i7y5i0
to1l4r55n1wzr817l225l6pm97li1mxg9icd8s51cpfihh91nkdz68
, but the actual output on my machine was0l9ghs6xg0pv3ssik807jcvai3f0w83cskx7ymq6kr8f1h8lqbp0
.cc @cstrahan
I can provide more information on request. I'm still pretty new to NixOS so I'm not sure what kind of information is relevant for creating issues.
The text was updated successfully, but these errors were encountered: