In reply to @hexa:lossy.network
cudaSupport should default to false, not sure why you need to set it

In reply to @hexa:lossy.network
feel free to send a PR to update the message!

In reply to @dpc:dpc.pw
I was getting evaluation errors that these two symbols don't exist, so I just set them to something and it worked.

In reply to @hexa:lossy.network
post the trace please

In reply to @dpc:dpc.pw
for allowAliases https://pastebin.com/fWShsnXB

I do have an overlay that adds stuff to the package set:

      overlay = { system, pkgs-unstable, pkgs-master }: (final: prev: {
        config.allowAliases = true;
        # config.cudaSupport = false;
        xremap = xremap.packages.${system}.default;
        helix = dpc-helix.packages.${system}.default;
        dpc-todo = todo.packages.${system}.default;
        rblake2sum = rblake2sum.packages.${system}.default;
        intel-one-mono = pkgs-x86_64.callPackage ./pkgs/intel-one-mono.nix { };
      });

In reply to @dpc:dpc.pw

I do have an overlay that adds stuff to the package set:

      overlay = { system, pkgs-unstable, pkgs-master }: (final: prev: {
        config.allowAliases = true;
        # config.cudaSupport = false;
        xremap = xremap.packages.${system}.default;
        helix = dpc-helix.packages.${system}.default;
        dpc-todo = todo.packages.${system}.default;
        rblake2sum = rblake2sum.packages.${system}.default;
        intel-one-mono = pkgs-x86_64.callPackage ./pkgs/intel-one-mono.nix { };
      });

In reply to @artturin:matrix.org
config = prev.config // { allowAliases = true; };

In reply to @hexa:lossy.network
are you maybe mixing packages between branches?

In reply to @dpc:dpc.pw
I do include bunch of modules from other places like nixos-hardware, home-manager, etc. I guess these might cause it then? I should probably force them to follow the 21.11 nixpkgs input and that's the explanation here?

In reply to @hexa:lossy.network
figsoda: can we get 23.11 on search?

In reply to @hexa:lossy.network
figsoda: can we get 23.11 on search?