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
azure-cli: 2.15.1 -> 2.16.0 #106773
azure-cli: 2.15.1 -> 2.16.0 #106773
Conversation
cryptography = super.cryptography.overridePythonAttrs(oldAttrs: rec { | ||
version = "2.9.2"; | ||
version = "3.3.1"; | ||
|
||
src = super.fetchPypi { | ||
inherit (oldAttrs) pname; | ||
inherit version; | ||
sha256 = "0af25w5mkd6vwns3r6ai1w5ip9xp0ms9s261zzssbpadzdr05hx0"; | ||
sha256 = "1ribd1vxq9wwz564mg60dzcy699gng54admihjjkgs9dx95pw5vy"; |
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.
I would just remove the entire pinning to cryptography
Please follow CONTRIBUTING.md and manual#submitting-changes-making-patches and squash the fix-up commits.
|
@jonringer Thank you for the very informative video, I did what was requested. |
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.
congrats @anhdle14 on your first nixpkgs contribution. Thanks! :) |
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)One thing I am not sure about is whether patching
cryptography
to3.3.1
is the correct way or not. But for pyOpenSSL to compile,cryptography
must be at least3.2
. Source here: CHANGELOG