Closed flokli closed 3 years ago
Thanks for the report! Yes, https://github.com/NixOS/nixpkgs/commit/780fa5556a686076196e66aea0df62be0254f44d should've caused this as libva 2.11.0 added the "LibVA Protected Content API" (DRM :o). Not sure how this slipped through staging-next (don't we have the tested
jobset there as well?).
Anyway, I see the following options:
I've opened #119003 to hopefully fix the build. I've also looked into overriding libva but that turned out to be pretty complex/dirty and likely cannot safe us from a Chromium rebuild so the patch is probably the better option.
I think using the patch from archlinux, or using a downgraded version only defined in the chromium derivation for now, and dropping this once M90 is released both work.
We shouldn't keep chromium broken for people building master.
To Reproduce Steps to reproduce the behavior:
nix-build -A chromium
possibly caused by https://github.com/NixOS/nixpkgs/commit/780fa5556a686076196e66aea0df62be0254f44d, which did land in master via https://github.com/NixOS/nixpkgs/pull/118312. Not caused by https://github.com/NixOS/nixpkgs/pull/118133.
Expected behavior Maintainer information: