| 23 Jun 2026 |
Sergei Zimmerman (xokdvium) | Right yeah. I wonder how hard it would be to try this approach with lix | 19:58:14 |
Sergei Zimmerman (xokdvium) | Lemme try | 19:58:19 |
raitobezarius | horrors was planning to do it as an intermediate response | 19:59:17 |
| 24 Jun 2026 |
Ramses 🇵🇸 | I'm getting 429s while searching issues on git.lix.systems | 09:27:09 |
Ramses 🇵🇸 | Just normal browser activity, I didn't do anything unusual AFAIK | 09:27:32 |
raitobezarius | yeah, it's my bad | 09:32:14 |
raitobezarius | i will remove it | 09:32:20 |
raitobezarius | that is fixed | 12:14:36 |
Ramses 🇵🇸 | cool, thx! | 12:15:07 |
teutat3s | I came up with this overlay:
final: prev: {
lixPackageSets = prev.lixPackageSets // {
latest = prev.lixPackageSets.latest // {
lix = prev.lixPackageSets.latest.lix.override {
curl = prev.curl.overrideAttrs (oldAttrs: { patches = []; });
};
};
};
};
| 12:31:44 |
zoë (@blokyk) | you can use .makeLixScope to override a package no? | 12:34:56 |
teutat3s | What would that look like? I haven't used .makeLixScope yet. | 12:36:36 |
zoë (@blokyk) | Redacted or Malformed Event | 19:17:06 |
zoë (@blokyk) | sorry i was on my phone and should have looked it up before saying that. i actually meant .overrideScope, which will allow you to have the correct lix derivation used by other derivations in the lixPackageSets.latest set. for example, you'd do something like:
final: prev: {
lixPackageSets = prev.lixPackageSets // {
latest = prev.lixPackageSets.latest.overrideScope (finalSet: prevSet: {
lix = prevSet.override {
curl = prev.curl.overrideAttrs { patches = []; };
};
});
};
}
| 19:21:24 |
zoë (@blokyk) | ugh this is not amazing either way | 19:21:36 |
zoë (@blokyk) | but at least here you get proper overriding for lix in other things under lixPackageSets.latest.* (such as nix-init, nix-du, etc.) | 19:22:27 |
zoë (@blokyk) | * sorry i was on my phone and should have looked it up before saying that. i actually meant .overrideScope, which will allow you to have the correct lix derivation used by other derivations in the lixPackageSets.latest set. for example, you'd do something like:
finalPkgs: prevPkgs: {
lixPackageSets = prevPkgs.lixPackageSets // {
latest = prevPkgs.lixPackageSets.latest.overrideScope (finalSet: prevSet: {
lix = prevSet.lix.override {
curl = prevPkgs.curl.overrideAttrs { patches = []; };
};
});
};
}
| 19:23:08 |
zoë (@blokyk) | * sorry i was on my phone and should have looked it up before saying that. i actually meant .overrideScope, which will allow you to have the correct lix derivation used by other derivations in the lixPackageSets.latest set. for example, you'd do something like:
finalPkgs: prevPkgs: {
lixPackageSets = prevPkgs.lixPackageSets // {
latest = prevPkgs.lixPackageSets.latest.overrideScope (finalSet: prevSet: {
lix = prevSet.lix.override (prevArgs: {
curl = prevArgs.curl.overrideAttrs { patches = []; };
});
});
};
}
| 19:24:17 |
teutat3s | Luckily, after https://tracker.nixos.c3d2.de/?pr=534830 this won't be necessary anymore | 19:45:29 |
bl1nk | Hey! Is pkgs.lixPackageSets.stable.lix the recommended version of lix to choose for stability? For some reason my way too old t480s cannot compile 2.94.2 since some recent checkout of nixpkgs. Asking here because recompiling on different revisions takes hours every time on this old CPU. | 19:54:04 |
zoë (@blokyk) | do you know why it doesn't compile? where does the derivation stop (the configure, the build, the check, the install, etc.)? | 19:55:34 |
bl1nk | It fails the checks, I am currently in the middle of a recompile so I am waiting for the result, but it will likely fail soon'ish :D | 19:56:00 |
zoë (@blokyk) | hmm, if it's because of a timeout or smth, you can probably turn off the checks altogether (without doCheck = false and doInstallCheck = false, iirc) | 19:56:54 |
zoë (@blokyk) | * hmm, if it's because of a timeout or smth, you can probably turn off the checks altogether (with doCheck = false and doInstallCheck = false, iirc) | 19:57:04 |
zoë (@blokyk) | * hmm, if it's because of a timeout, you can probably turn off the checks altogether (with doCheck = false and doInstallCheck = false, iirc) | 19:57:18 |
zoë (@blokyk) | * hmm, if it's because of a timeout, you can probably safely turn off the checks altogether (with doCheck = false and doInstallCheck = false, iirc) | 19:57:27 |
raitobezarius | if it's not in the cache, it's due to the recent curl bug we are tracking | 19:57:39 |
raitobezarius | some fixes have been merged | 19:57:43 |
raitobezarius | i don't think those timeouts are innocent | 19:57:57 |
bl1nk | I'm tracking nixos-26.05 in my flake, currently on rev 34268251cf5547d39063f2c5ea9a196246f7f3a6 | 19:57:58 |