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
protonvpn-cli-ng: 2.2.2 -> 2.2.4 #91328
Conversation
So... It still worked without erroring about the hash. I guess it did not change the binary, which is what I assume would change the hash? |
You're right. In order to get the new hash, you can change a character in the hash and rebuild the package. Then you'll find the expected hash in the stack trace once the rebuild failed. |
I ran nixpkgs-review for it. |
No, if you didn't change the hash then it didn't build the new executable. Check its version with -v. |
Okay, I see what you mean. |
3161d9b
to
f8185a7
Compare
Okay, got it squashed. |
Great! Could you rename the commit message to conform to the guidelines? |
Changed version number and added Jinja2 to propagatedBuildInputs.
That look about right? |
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.
Perfect, thank you!
Result of 1 package built:- protonvpn-cli-ng |
ProtonVPN-cli-ng: 2.2.2 -> 2.2.4
Motivation for this change
Things done
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)