python3Packages.cryptography: 3.4.2 -> 36.0.0#150320
Conversation
|
How well is this tested? Last time you noticed that this breaks a few packages and we had to revert it: #140024 (comment) Hopefully the situation improved in the meantime but I wouldn't be surprised if there are some breakages left. My plan was to run a full nixpkgs-review on Python packages but unfortunately I didn't get around to it yet as it requires a lot of disk space (and time). Or someone monitors Hydra for regressions. |
|
I only tested building Currently in the process of updating home-assistant, so both my attention and compute are exhausted. |
|
|
|
@veehaitch Would you mind looking into bumping sslyze and nassl? The latter fails because of known vulnerabilities. |
|
Have built a lot of depending packages (cherry-picked back to master) on 3 platforms (macos 10.15, nixos x86_64 & aarch64) and that's the only issue I've been able to find. Think it's probably good enough for staging. |
|
Oh, including |
Motivation for this change
https://github.com/pyca/cryptography/blob/36.0.0/CHANGELOG.rst#3600---2021-11-21
Things done
sandbox = trueset innix.conf? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)nixos/doc/manual/md-to-db.shto update generated release notes