maturin: 0.13.0 -> 0.14.5

[luizirber]

Description of changes

Upstream changelog: https://github.com/PyO3/maturin/blob/main/Changelog.md#0140---2022-11-19

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • seeing ~15 failures during testing (not compiling), most from tensorflow/JAX related packages.
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.05 Release Notes (or backporting 22.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[luizirber]

This is technically a major version bump, should I document it in the 23.05 release notes?

[risicle]

Found no new failures building all affected python310Packages.* on aarch64-linux.

This will need to be re-targeted at staging though using the method described in https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#rebasing-between-branches-ie-from-master-to-staging

[luizirber]

This will need to be re-targeted at staging though using the method described in https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#rebasing-between-branches-ie-from-master-to-staging

Just did that! (sorry if I'm making a mess in this PR, my first time contributing to nixpkgs...)

[risicle]

Found no new failures building all affected python310Packages.* on macos 10.15.

[luizirber]

Sorry for spamming here, but is the etiquette to keep the branch updated with staging while it is not approved/merged, or that would just cause CI churn?

[risicle]

Let's circumvent that issue entirely.

[risicle]

(answer - usually only if there's a merge conflict)