!9IQChSjwSHXPPWTa:lix.systems

Lix

1105 Members
Lix user channel. Feel free to discuss on-topic issues here and give each other help. For matrix.to links to the rest of the Lix channels, see: https://wiki.lix.systems/books/lix-organisation/page/matrix-rooms295 Servers

Load older messages


SenderMessageTime
17 Oct 2025
@lillecarl:matrix.orglillecarl* (I've done it with SQLite already but it's a bit eeeeeh imho, the DB is owned by Lix) 18:00:44
@raitobezarius:matrix.orgraitobezariusThere's no other way than SQLite18:02:25
@raitobezarius:matrix.orgraitobezarius(short of deleting and reimporting the closure but that's not a solution)18:02:48
@lillecarl:matrix.orglillecarlThen I'll keep doing it like so, I will shell out to Nix commands for deletions in the "altgc", I banged that out successfully which was nice, I don't know how to check liveness properly, and I don't have to 😄18:04:59
@cyan/teeth:matrix.org@cyan/teeth:matrix.org left the room.21:28:53
@uep:matrix.orguep

yeah, there's two things..

  1. I have a test box in my fleet that doesn't use lix, partly just to catch cases where something diverges, mostly because I just forgot to add the lix module and discovered that when something broke (one of the experimental features) as a result and so decided to keep it.
  2. For all the other hosts, I don't want cppnix there at all, but it is pulled in somewhere and I just haven't bothered chasing down where
23:25:33
18 Oct 2025
@ekler:feel-co.orgeklerRedacted or Malformed Event00:58:50
@ekler:feel-co.orgekler
In reply to @sofiedotcafe:matrix.org
and make the original somehow not allowed

what I ended up doing, more or less:

{
  nixpkgs.overlays = [
    (f: p: {
      nix = f.lixPackageSets.lix_2_93.lix;

      nixVersions = {
        latest = f.nix;
        stable = f.nix;
      };
    })
  ];

  system.forbiddenDependenciesRegexes = [ "^/nix/store/[a-z0-9]+-nix-[0-9.]+.*" ];
}

of course this will break anything that relies on the c api :|

01:01:23
@winter:catgirl.cloudWinteryou just invented the Lix overlay ;P03:48:54
@winter:catgirl.cloudWinter * 03:49:04
@dawnofmidnight:catgirl.cloud@dawnofmidnight:catgirl.cloud changed their display name from dawnofmidnight to whispers.05:34:41
@neobrain:matrix.orgneobrain joined the room.10:29:48
@firefly:raccoon.collegeFireFly TIL about forbiddenDependenciesRegex, interesting 11:10:14
@firefly:raccoon.collegeFireFly * TIL about forbiddenDependenciesRegexes, interesting 11:10:20
@522_:catgirl.cloud522 it/its ⛯ΘΔ forbiddenDependenciesRegexes: .*
no more nix
11:13:30
@antifuchs:asf.computerantifuchsHyperindividualist software development like11:46:48
@gimmechocolate:bark.lgbtUnawarewolfJust wanna say: I really love the vibe here!! most cozy linux channel!!!!!!12:05:40
@quadradical:federated.nexusQuadRadical (Ping) @raitobezarius is there anything i can do to look into this myself, or circumvent it (can i turn on the nix sandbox on the vps?) 16:10:31
@antifuchs:asf.computerantifuchs so wait, if I wanted to see if a system targets a particular CPU (e.g. x86-64), what would I do? I tried lib.meta.platformMatch lib.systems.inspect.patterns.isAarch64 "aarch64-linux" which unfortunately indicates false. 17:19:16
@antifuchs:asf.computerantifuchsflakes insisting on purity and static platform selection but giving you zero tools to apply that... ):17:20:38
@saiko:knifepoint.netKatalin 🔪 (lib.systems.elaborate "aarch64-linux").isAarch64 17:30:03
@antifuchs:asf.computerantifuchsoh wow, I've never seen that one before. super useful, thanks!18:36:41
@abaris99f:matrix.org@abaris99f:matrix.org set a profile picture.21:30:39
@novedevo:matrix.orgDevon joined the room.22:58:01
19 Oct 2025
@wucke13:matrix.orgwucke13 joined the room.11:06:34
@wucke13:matrix.orgwucke13Is this a place where I may ask questions about using Lix?11:07:12
@marie:marie.cologneMarieyes11:07:57
@k900:0upti.meK900Yes11:13:38
@wucke13:matrix.orgwucke13

I'm trying to migrate from the dedicated Lix module to the nixpkgs built-in Lix. IIUC, the manual recommends this:

  nixpkgs.overlays = [
    (final: prev: {
      inherit (prev.lixPackageSets.stable)
        nixpkgs-review
        nix-eval-jobs
        nix-fast-build
        colmena
        ;
    })
  ];

  nix.package = pkgs.lixPackageSets.stable.lix;

However, that throws an infinite recursion for nixpkgs-review. I do have a couple more overlays, but they are not interacting with nixpkgs-review in any obvious way.

What could be the culprit, how to debug?

11:13:55
@wucke13:matrix.orgwucke13

So, a bit more tinkering revealed that most but not all of the overrides cause the issue:

  • nixpkgs-review: causes infinite recursion
  • nix-eval-jobs: No problem
  • nix-fast-build: causes infinite recursion
  • colmena: causes infinite recursion

Here is a minimal repro for playing:

{ pkgs, ... }:

{
  nixpkgs.hostPlatform = "x86_64-linux";

  # TODO debug why this yields infinite recursion
  nixpkgs.overlays = [
    (final: prev: {
      inherit (prev.lixPackageSets.stable)
        nixpkgs-review
        nix-eval-jobs
        nix-fast-build
        colmena
        ;
    })
  ];

  nix.package = pkgs.lixPackageSets.stable.lix;
  environment.systemPackages = with pkgs; [
    nixpkgs-review
    nix-eval-jobs
    nix-fast-build
    colmena
  ];

  boot.isContainer = true;
  fileSystems."/".fsType = "tmpfs";
}
11:41:27

Show newer messages


Back to Room ListRoom Version: 10