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
wofi: fixes bad patch hash #83535
wofi: fixes bad patch hash #83535
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rebuilt with this change and it works for me. I'm pretty surprised about sourcehut, but I wonder if paste is like snippets or pastebin and things can be edited afterward.
Also thanks for your original fix. Wofi works first time now, where I was previously just launching some GTK application to initialize something before it would work in sway.
I'm pretty surprised too, I thought it was a diff generated from a specific commit, and it seems that's not the case. Glad to read ! 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again. Would you be interested in taking maintainership of this package? I don't use it anymore.
Yes, no problem for me, I'm using Sway as my daily driver for work ;). |
Fixes #83627 |
Is it possible that you copied the hash over from the fetchurl? fetchpatch normalizes the patch and hashes it afterwards, so using fetchpatch will result in a different result than using fetchurl. The hash in the old derivation matches the one from In other words: Are you sure the fetchpatch hash was correct at some point? |
I have to say that I'm not sure. I believe I could have done the mistake, indeed. If you check the previous PR i switched from |
@petabyteboy : I've pushed an update |
Yes you are correct about the cache. The whole nix store is a giant cache. And both fetchurl and fetchpatch are based on fixed-output derivations. This is a special type of derivation where Nix will allow network access, but require the output hash to be known in advance, and after that it will use the hash to address the output in the store. About how to prevent such problems: It's a bit difficult. If you change an expression (for example the version), you should probably try to replace the hashes that could depend on it with 00000... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Builds fine for me now 🎉
Thanks, I understand why I've made the mistake and how to not reproduce it:
Sorry about that ! |
Things done
Fixes hash inconsistency reported by @wkral : I'm really surprised that files on
paste.sr.ht
have changed, if anybody knows how works SouceHut, I would be glad to be enlighten :).Related to changes in #83283.
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)