diff options
author | Vincent Ambo <mail@tazj.in> | 2023-03-07T23·10+0300 |
---|---|---|
committer | clbot <clbot@tvl.fyi> | 2023-03-08T10·28+0000 |
commit | 252d8b10dbb9bcda496afae1a420d8b115d58175 (patch) | |
tree | bfa4b78fe6f864e5c51885c44da8e937cee3cdc0 /nix/buildManPages | |
parent | 2696839770c1ccb62929ff2575a633c07f5c9593 (diff) |
fix: use `depsTargetTargetPropagated` for depot's gcroot r/5900
We've been seeing CI failures after a recent nixpkgs bump which only occur on canon *after* a CL has been merged. In these CI failures, the `ci.gcroot` attribute is built to "anchor" the latest canon build, but fails because it tries to execute random non-executable files (e.g. the sqlite database produced by //corp/russian/data-import). From what I can tell, there has been a recent change in nixpkgs where makeSetupHooks' arguments were restructured. What was previously `deps` is now `propagatedBuildInputs`, and `depsTargetTargetPropagated`. The latter is supposed to be used for non-executable targets, according to the docs. This commit changes the entire set to use that flag, as we don't actually want any executable setup hook - just a gcroot. Change-Id: Ib258c4f3b09d746c3d000d1c7480d2b4101ab75e Reviewed-on: https://cl.tvl.fyi/c/depot/+/8227 Autosubmit: tazjin <tazjin@tvl.su> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI
Diffstat (limited to 'nix/buildManPages')
0 files changed, 0 insertions, 0 deletions