Update hash for python bootstrap build

[cotrone]

Description of changes

Updates the hash for the new version of pypa/build. Looks like it was missed in #294305.

Things done

Ran nix-prefetch-git https://github.com/pypa/build.git refs/tags/1.1.1 and replaced the hash with the new hash

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• 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
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.05 Release Notes (or backporting 23.05 and 23.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
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[mweinelt]

Thanks for noticing. This is too big a rebuild for master, and also for staging-next at this time. It also needs validation, since build sits at the core of python packages, so I'm not sure if we should update, if it wasn't integration tested properly.

[tpwrules]

Can the version number be reverted so the hash is not wrong?

[mweinelt]

The src FOD is cached since the hash wasn't invalidated. We require another staging cycle to update it. The currently ongoing #305152 bumps build to 1.2.1.

[cotrone]

Looks like this was fixed in #305152. Thanks!

[davean]

Thanks for noticing. This is too big a rebuild for master, and also for staging-next at this time. It also needs validation, since build sits at the core of python packages, so I'm not sure if we should update, if it wasn't integration tested properly.

This was a fairly big deal, is there any plans to protect from it happening again?

[jonringer]

NixOS/rfcs#171 would have made this into a build failure

[jonringer]

Be the FOD change you want to be