I am curious, are you actually using boxx/bpycv for anything?

As you've probably noticed, these packages aren't currently in a good place and AFAIK, neither upstream nor the current nixpkgs maintainer @lucasew are interested in supporting them.

I was originally planning to fix the build and tests in #380403 just like you did (and I did "kind of" fix the tests for boxx), but bpycv (the "main" package among this set of packages) is still fundamentally broken, because it is unsupported on modern versions of blender.

Following the discussion with the current nixpkgs maintainer in #379872, we decided that we might as well just remove these packages (#380443). I think that unless you are actively using boxx and/or bpycv, then removing these packages might still be preferable.

Thoughts?

I think that unless you are actively using boxx and/or bpycv, then removing these packages might still be preferable.

Thoughts?

I am not using them. I guess we can remove them if nobody use them.

Interesting! https://hydra.nixos.org/eval/1811921?filter=bpycv&compare=1811844&full=

Interesting! https://hydra.nixos.org/eval/1811921?filter=bpycv&compare=1811844&full=

what exactly is interesting? this pr fixed the build of boxx and also bpycv because boxx is its dependency

AFAIK, the build for bpycv itself currently succeeds only because its tests are performed in a separate derivation (instead of checkPhase). While the package itself technically "builds" after boxx tests were removed, it is still fundamentally broken due to some changes in the python API in Blender v4.