| 18 Aug 2025 |
raitobezarius | emily i think i will merge up to https://gerrit.lix.systems/c/lix/+/3850/7 today | 11:10:24 |
raitobezarius | fwiw | 11:10:24 |
raitobezarius | so that the stack becomes smaller | 11:10:30 |
helle (just a stray cat girl) | there are also some small devx things with f2 that may cause some annoyances with writing certain types of tests | 11:11:15 |
raitobezarius | gerrit merge noises | 13:08:57 |
jade_ | does anyone know why wrapPythonPrograms = true is on by default? it appears to be Totally Broken because it means that if you ever invoke a python program from a python program, it loses the calling environment | 13:21:31 |
Winter | fyi https://git.lix.systems/lix-project/lix/commit/858de5f47a1bfd33835ec97794ece339a88490f1 should probably be backported to a release, getting build errors on unstable bc lowdown bump | 13:47:52 |
emily | uh. I would have preferred not. I still did not finish checking whether the reproducibility issues in my Darwin system closure are solvable and I think I had unpushed changes. | 14:30:48 |
raitobezarius | argh, how problematic is it in practice? | 14:31:20 |
raitobezarius | i mean if the reproducibility issues are impossible to resolve, we can still revert things, it's more noise | 14:31:50 |
raitobezarius | but this is fine | 14:31:52 |
raitobezarius | for next time, please don't hesitate to put WIP or an unresolved comment to mark that the change is not ready | 14:32:14 |
raitobezarius | In reply to @winter:catgirl.cloud fyi https://git.lix.systems/lix-project/lix/commit/858de5f47a1bfd33835ec97794ece339a88490f1 should probably be backported to a release, getting build errors on unstable bc lowdown bump it's backported to all releases but i surmise that we didn't do any further release | 14:33:30 |
emily | I did, but it looks like I resolved the comment as all-looks-resolvable-in-principle. I did not get around to sending the most basic fixes off to Nixpkgs for review though. I was pipelining testing it with the LLVM 21 bump which has felt more time-critical; if I'd known there was a hurry I could have prioritized but with the author-submits model I was just planning to come back to it once I felt confident and you said you were looking into one of the patches in the stack so I was also waiting on that | 14:48:51 |
emily | I'm concerned about changing the format/prefix length twice | 14:49:01 |
raitobezarius | there's no hurry | 14:49:02 |
raitobezarius | it's HEAD | 14:49:05 |
raitobezarius | i want to keep stack size small because once people starts sending their own large stacks, frustration starts | 14:49:26 |
raitobezarius | yeah i'm still looking into one patch of the stack | 14:49:42 |
raitobezarius | it's not submitted | 14:49:44 |
raitobezarius | i submitted everything up to that specific point* | 14:49:50 |
raitobezarius | * i submitted everything up to that specific point | 14:49:53 |
raitobezarius | In reply to @emilazy:matrix.org I'm concerned about changing the format/prefix length twice the only change that went in afaik is the one that doesn't include derivation names in build directories | 14:50:42 |
raitobezarius | we can revert that one if you feel like this is not ready yet for prime time | 14:50:52 |
raitobezarius | and only few people would have seen it | 14:50:57 |
raitobezarius | i'm not sure if your concern pertains actually CLs that are still unmerged | 14:51:37 |
raitobezarius | or you are concerned about | 14:51:43 |
raitobezarius |  Download clipboard.png | 14:51:45 |
raitobezarius | being merged as well | 14:51:47 |
raitobezarius | which seems pretty safe to me | 14:51:57 |