| 16 Sep 2025 |
 laurents | well well, it looks like using a git+https://github.com/some/repo input does not work if said repo is a fork. If I clone the repo, and create a new one on github that is not a fork, say git+https://github.com/some/repo_that_is_not_a_fork, then lix is happy to use it as an input. | 12:27:03 |
 raitobezarius | absolutely unhinged bug | 12:57:28 |
| laurents | ok, apologies, ignore me, somehow the nix cache got into an invalid state. once I removed it, the fork version worked again. I'm not sure how it got into that broken state, but I think I will leave it at that for now. Sorry for the noise. | 13:27:00 |
| raitobezarius | don't worry, it's called flakes for a reason | 13:30:57 |
 aloisw | How are the fallback code owners decided? https://gerrit.lix.systems/c/lix/+/4135 has approval from someone in the core team but still doesn't have the code owner check satisfied. | 15:29:09 |
 jade_ | aloisw: it is a file in the refs/meta/config branch that has me, raito and pennae in it. that could of course get changed/fixed though. | 17:33:56 |
| jade_ | (the intent of it was to not have it apply to anything, but that has evidently been shown to be wrong sometimes) | 17:47:14 |
| jade_ | https://gerrit.lix.systems/c/lix/+/4164 let's fix those ones cuz they are definitely wrong | 17:50:44 |
| aloisw | perl also seems to have no owners. | 18:01:30 |
| jade_ | aloisw: fixed | 20:30:59 |
| 17 Sep 2025 |
 just1602 | I wish it was also supporting gerrit OWNER file: https://github.com/vim/vim/pull/18299/files | 00:11:28 |
 emily | put up a new version of the build-dir stuff with a fix for the regression (and a test that hopefully works) | 01:29:06 |
| emily | too tired to do the code owner requesting dance on it tonight though | 01:29:14 |
| raitobezarius | it's ok | 10:13:03 |
| emily | https://gerrit.lix.systems/c/lix/+/4179/2 and https://gerrit.lix.systems/c/lix/+/4172/3 are the only real changes fwiw | 13:32:29 |
|  @skiparoo:matrix.org left the room. | 17:26:02 |
 piegames | Can I pretty please get a merge queue? | 19:02:49 |
| piegames | I rebased today, waited for CI and now I need to rebase again | 19:02:59 |
| raitobezarius | I can help someone deploying one, I cannot take care of this until mid-October with the current load on my plate | 19:05:14 |
| piegames | waiting a month works for me tbh, I won't be doing much Lix in the meantime either | 20:26:04 |
| piegames | thank you for taking care of this | 20:26:41 |
 Winter | is flokli's still basically the best one? | 20:27:35 |
 lillecarl | Ive been looking into building a time based GC, I built a nix-touch command that updates regtime for a storepath and it's dependencies (and optionally build time deps). Next I'm building a nix-gctime (or something) which will just try to remove any storepaths older than $time regtime (using nix subprocess so I don't have to implement liveness checking).
I just wanted to check in and see if either of you guys have thought of this and why it's a bad idea, it feels so stupid redownloading sources and build-time deps from 10 minutes ago because I ran GC. | 20:37:40 |
| lillecarl | --delete-older-than from nix-collect-garbage only kills old gcroots if I understand correctly and doesn't care about regtime when it's time to collect garbage | 20:40:23 |
| lillecarl | (This came up when building a nix-snapshotter clone but on the CSI layer rather than CRI) | 20:41:58 |
| emily | https://github.com/risicle/nix-heuristic-gc but requires atime | 20:46:24 |
| emily | it sounds like you want keep-derivations and keep-outputs mainly thougj | 20:47:01 |
| lillecarl | In reply to @emilazy:matrix.org
it sounds like you want keep-derivations and keep-outputs mainly thougj That's good-enough to start, but it'd keep build deps for all gcroots right?
I'll continue the 3rd party GC impl, it's really just a couple of SQLite statements and some subprocessing :) | 20:56:02 |
| lillecarl | * That's good-enough to start, but it'd keep build deps for all gcroots right?
I'll continue the 3rd party GC impl, it's really just a couple of SQLite statements and some subprocessing :)
Edit: wouldn't wanna rely on atime though :p
| 20:57:07 |
| emily | yes, but I mean it beats losing stuff unless you're low on disk | 20:58:21 |
