I think we can put this directly in staging-next? Not sure what the process is, but the breakage happens on both staging-next and staging. /cc @FRidh

Let's not, as it will cause a large rebuild again.

Let's not, as it will cause a large rebuild again.

Perhaps, but it might be necessary to make sure dependencies of lz4 aren't broken for other reasons.

We could maybe make the change only cause the rebuilds on Darwin, = if !stdenv.hostPlatform.isDarwin then null else fetchpatch... with a note to simplify on next rebuild?

If it is currently broken, for Darwin these aren't rebuilds.. just "builds" :)

Yes. Note there is more Darwin stuff broken:
#60491 (comment)

@FRidh This one is holding up nixpkgs-unstable:

https://hydra.nixos.org/job/nixpkgs/trunk/unstable#tabs-constituents

Could we cherry pick it?

This should be in staging-next by now. If it's a mass-rebuild we shouldn't cherry-pick to master.