-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
RFC 0133 git hashing: hashes $NIX_BUILD_TOP/tmp
#12295
Comments
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/how-to-use-rfc0133-git-hashing-for-fods-correctly/59068/6 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2024-01-22-nix-team-meeting-minutes-210/59239/1 |
We were simply passing in the wrong path. This went uncaught because the TODO about deduplication hasn't happened yet.
#12335 OK so the bug was really trivial and a stupid typo on my part! And easy to fix :) |
We were simply passing in the wrong path. This went uncaught because the TODO about deduplication hasn't happened yet.
Thank you! |
Describe the bug
When trying to create a git-hashed derivation, the content is hashed correctly but in
$NIX_BUILD_TOP/tmp
not in$out
.Steps To Reproduce
Where
/tmp/a
is a git repository with some random stuff.Result: the first command complains about a hash mismatch for the correct tree hash, the second command complains about a hash mismatch for a empty-root-directory git hash. (Based on
./tmp/
content)Expected behavior
The hash mismatch complaints match
$out
content.Metadata
Additional context
Just making sure it is not missed in the stabilisation of #8919
Discussed https://discourse.nixos.org/t/how-to-use-rfc0133-git-hashing-for-fods-correctly/59068 with @Atemu
Checklist
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: