nix: pin lix to 2.94 explicitly to avoid Devbox breakage

pkgs.lix tracks nixpkgs' stable alias, which could move to Lix 2.95+
and silently break Devbox (fetchClosure removal). Pin to lix_2_94
directly until jetify-com/devbox#2983 lands upstream.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
randogoth 2026-10-07 18:21:17 +03:00
parent eb9d7fb9b8
commit 89a22a0fa6

View file

@ -1,9 +1,13 @@
{ inputs }: { inputs }:
{ pkgs, ... }: { pkgs, ... }:
{ {
# Use Lix from nixpkgs (2.94.x on nixos-26.05). The lix-module's # Pin explicitly to lix_2_94 rather than pkgs.lix (= lixPackageSets.stable),
# lixFromNixpkgs still pins lix_2_93, which nixos-26.05 removed. # which nixpkgs could bump to 2.95+ in a point release. Lix 2.95 dropped
nix.package = pkgs.lix; # builtins.fetchClosure (a knock-on of removing ca-derivations), which
# breaks Devbox. Fix is known but unmerged upstream as of 2026-10:
# https://github.com/jetify-com/devbox/issues/2983
# Revisit once that lands, or Devbox is dropped in favor of Flox.
nix.package = pkgs.lixPackageSets.lix_2_94.lix;
imports = [ imports = [
inputs.nix-index-database.nixosModules.nix-index inputs.nix-index-database.nixosModules.nix-index