Skip to content

[staging-next] python3Packages.home-assistant-chip-wheels: fix building with newer gn#432683

Merged
mweinelt merged 1 commit intoNixOS:staging-nextfrom
emilylange:home-assistant-chip-wheels
Aug 11, 2025
Merged

[staging-next] python3Packages.home-assistant-chip-wheels: fix building with newer gn#432683
mweinelt merged 1 commit intoNixOS:staging-nextfrom
emilylange:home-assistant-chip-wheels

Conversation

@emilylange
Copy link
Member

This fixes the following error caused by https://gn-review.googlesource.com/c/gn/+/18820 and the gn bump in b59bfde (#419337) by backporting https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/300272

Running phase: configurePhase
gn flags: chip_project_config_include_dirs=\[\"//..\"\] chip_crypto=\"openssl\" [...]
  generated_file("$target_name._includes") {
  ^-----------------------------------------
Two or more targets generate the same output:
  protocol_buffer/gen/third_party/pigweed/repo/pw_chrono/protos.proto_library/includes.txt

This is can often be fixed by changing one of the target names, or by setting an output_name on one of them.

Collisions:
  //third_party/pigweed/repo/pw_chrono:protos._includes(//build/toolchain/custom:custom)

#432489

Things done

  • Built on platform:
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • Tested, as applicable:
  • Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • Tested basic functionality of all binary files, usually in ./result/bin/.
  • Nixpkgs Release Notes
    • Package update: when the change is major or breaking.
  • NixOS Release Notes
    • Module addition: when adding a new NixOS module.
    • Module update: when the change is significant.
  • Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

This fixes the following error caused by https://gn-review.googlesource.com/c/gn/+/18820
and the gn bump in b59bfde by
backporting https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/300272

~~~
Running phase: configurePhase
gn flags: chip_project_config_include_dirs=\[\"//..\"\] chip_crypto=\"openssl\" [...]
  generated_file("$target_name._includes") {
  ^-----------------------------------------
Two or more targets generate the same output:
  protocol_buffer/gen/third_party/pigweed/repo/pw_chrono/protos.proto_library/includes.txt

This is can often be fixed by changing one of the target names, or by
setting an output_name on one of them.

Collisions:
  //third_party/pigweed/repo/pw_chrono:protos._includes(//build/toolchain/custom:custom)
~~~
@emilylange emilylange requested a review from mweinelt August 11, 2025 03:13
@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 501-1000 This PR causes many rebuilds on Linux and should normally target the staging branches. 6.topic: python Python is a high-level, general-purpose programming language. labels Aug 11, 2025
@nix-owners nix-owners bot requested review from dotlambda and fabaff August 11, 2025 03:19
@mweinelt
Copy link
Member

Thank you!

@mweinelt mweinelt merged commit b8e4777 into NixOS:staging-next Aug 11, 2025
29 of 31 checks passed
@emilylange emilylange deleted the home-assistant-chip-wheels branch August 11, 2025 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

6.topic: python Python is a high-level, general-purpose programming language. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 501-1000 This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants