Build failure: pkgsCross.riscv64.buildPackages.bcrypt

[RossComputerGuy]

Nixpkgs version

• Unstable (26.05)

Steps to reproduce

1. Build pkgsCross.riscv64.buildPackages.bcrypt (or cross compile cosmic-settings-daemon)

Can Hydra reproduce this build failure?

Hydra doesn’t try to build the package.

Link to Hydra build job

No response

Relevant log output

error: failed to run custom build command for `pyo3-ffi v0.26.0`

Caused by:
  process didn't exit successfully: `/build/source/src/_bcrypt/target/release/build/pyo3-ffi-a52b6e2ac95ee5f3/build-script-build` (exit status: 1)
  --- stdout
  cargo:rustc-check-cfg=cfg(Py_LIMITED_API)
  cargo:rustc-check-cfg=cfg(Py_GIL_DISABLED)
  cargo:rustc-check-cfg=cfg(PyPy)
  cargo:rustc-check-cfg=cfg(GraalPy)
  cargo:rustc-check-cfg=cfg(py_sys_config, values("Py_DEBUG", "Py_REF_DEBUG", "Py_TRACE_REFS", "COUNT_ALLOCS"))
  cargo:rustc-check-cfg=cfg(pyo3_disable_reference_pool)
  cargo:rustc-check-cfg=cfg(pyo3_leak_on_drop_without_reference_pool)
  cargo:rustc-check-cfg=cfg(Py_3_7)
  cargo:rustc-check-cfg=cfg(Py_3_8)
  cargo:rustc-check-cfg=cfg(Py_3_9)
  cargo:rustc-check-cfg=cfg(Py_3_10)
  cargo:rustc-check-cfg=cfg(Py_3_11)
  cargo:rustc-check-cfg=cfg(Py_3_12)
  cargo:rustc-check-cfg=cfg(Py_3_13)
  cargo:rustc-check-cfg=cfg(Py_3_14)
  cargo:rustc-check-cfg=cfg(Py_3_15)
  cargo:rerun-if-env-changed=PYO3_CROSS
  cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR
  cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION
  cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_IMPLEMENTATION
  cargo:rerun-if-env-changed=PYO3_NO_PYTHON
  cargo:rerun-if-env-changed=_PYTHON_SYSCONFIGDATA_NAME

  --- stderr
  error: Could not find _sysconfigdata*.py in /nix/store/jnida3h1d1xgdkr1cjj2irxbia8p95ih-python3-riscv64-unknown-linux-gnu-3.13.11/lib/python3.13
warning: build failed, waiting for other jobs to finish...
error: `cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/_bcrypt/Cargo.toml --target aarch64-unknown-linux-gnu --release -v --features pyo3/extension-module --crate-type cdylib --` failed with code 101

ERROR Backend subprocess exited when trying to invoke build_wheel

Additional context

No response

System metadata

• system: "aarch64-linux"
• host os: Linux 6.12.64, NixOS, 26.05 (Yarara), 26.05.20260109.9abe805
• multi-user?: yes
• sandbox: yes
• version: nix-env (Determinate Nix 3.15.1) 2.33.0
• nixpkgs: /nix/store/rcmh3pyadyy2rrv2xalgw9pcbfnw06j7-source

Notify maintainers

@dotlambda

---

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.

[ElvishJerricco]

Bisected to a48f11c, and it seems to be fixed by #480005

(In particular for my use case, cross-compiled image.repart images rely on buildPackages.black at build time, which exhibits the bug)

[ElvishJerricco]

Please reopen if I'm wrong about #480005 fixing this.

[doronbehar]

@RossComputerGuy FYI you can avoid waiting for #480005 to reach branch master and instead, cherry-pick this into branch master the following PR:

• python3: let lib.makeScopeWithSplicing' do its job #482863

This PR is the proper fix. And #480005 should be reverted, see:

• python3.pkgs.setuptools-rust: Revert "adjust setupHook inclusion condition" #482866