python311Packages.grpcio-status: 1.62.1 -> 1.62.2

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for python311Packages.grpcio-status is: GRPC Python status proto mapping

meta.homepage for python311Packages.grpcio-status is: https://github.com/grpc/grpc/tree/master/src/python/grpcio_status

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 1.62.2 with grep in /nix/store/x0g90bznx7h97dv3j2k027hiljqpqzaj-python3.11-grpcio-status-1.62.2
• found 1.62.2 in filename of file in /nix/store/x0g90bznx7h97dv3j2k027hiljqpqzaj-python3.11-grpcio-status-1.62.2

---

Rebuild report (if merged into master) (click to expand)

207 total rebuild path(s)

207 package rebuild(s)

First fifty rebuilds by attrpath

authentik
barman
baserow
browsr
dvc-with-remotes
gcp-scanner
home-assistant-component-tests.google_generative_ai_conversation
home-assistant-component-tests.google_pubsub
home-assistant-component-tests.nest
mycli
python311Packages.aiogithubapi
python311Packages.bpemb
python311Packages.cirq
python311Packages.cirq-google
python311Packages.cloudpathlib
python311Packages.dalle-mini
python311Packages.dbt-bigquery
python311Packages.django-storages
python311Packages.duckdb
python311Packages.duckdb-engine
python311Packages.dvc-gs
python311Packages.fastai
python311Packages.filedepot
python311Packages.fuzzytm
python311Packages.gcsfs
python311Packages.gensim
python311Packages.google-ai-generativelanguage
python311Packages.google-cloud-access-context-manager
python311Packages.google-cloud-appengine-logging
python311Packages.google-cloud-artifact-registry
python311Packages.google-cloud-asset
python311Packages.google-cloud-automl
python311Packages.google-cloud-bigquery
python311Packages.google-cloud-bigquery-datatransfer
python311Packages.google-cloud-bigquery-logging
python311Packages.google-cloud-bigquery-storage
python311Packages.google-cloud-bigtable
python311Packages.google-cloud-compute
python311Packages.google-cloud-container
python311Packages.google-cloud-datacatalog
python311Packages.google-cloud-dataproc
python311Packages.google-cloud-datastore
python311Packages.google-cloud-dlp
python311Packages.google-cloud-error-reporting
python311Packages.google-cloud-firestore
python311Packages.google-cloud-iam
python311Packages.google-cloud-iam-logging
python311Packages.google-cloud-iot
python311Packages.google-cloud-kms

Instructions to test this update (click to expand)

---

Either download from Cachix:

nix-store -r /nix/store/x0g90bznx7h97dv3j2k027hiljqpqzaj-python3.11-grpcio-status-1.62.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A python311Packages.grpcio-status https://github.com/r-ryantm/nixpkgs/archive/aef1ed3ab26f9b873cc05a6e093dad05aa13e17e.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/aef1ed3ab26f9b873cc05a6e093dad05aa13e17e#python311Packages.grpcio-status

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/x0g90bznx7h97dv3j2k027hiljqpqzaj-python3.11-grpcio-status-1.62.2
ls -la /nix/store/x0g90bznx7h97dv3j2k027hiljqpqzaj-python3.11-grpcio-status-1.62.2/bin

---

Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

nixpkgs-review took longer than 120m and timed out

---

Maintainer pings

cc @fabaff for testing.

[wegank]

Already on master.