!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

415 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.138 Servers

Load older messages


SenderMessageTime
1 Aug 2025
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)So this will cause a lot of manual churn18:38:17
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)Digging more is possible, but at this point, I don't see strong evidence of an easy win we could go for and one that wouldn't hamper the active team ability to authoring changes or reviewing changes18:40:25
@raitobezarius:matrix.orgraitobezarius (DECT: 7248) I'm interested in jade_ opinion on this 18:40:36
@charles:computer.surgeryCharles(might be good to keep it to the issue comments so things don't get lost)18:41:23
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)(this is done)18:50:24
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)
In reply to @raitobezarius:matrix.org
taking care of it
no problem on this end
23:39:02
2 Aug 2025
@saiko:knifepoint.netKatalin 🔪 changed their profile picture.00:28:02
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)

emily do you have news on https://gerrit.lix.systems/c/lix/+/3848/comments/69dc917c_8507f6a7 ?

In general, how would you like us to review the chain? I feel like there's some minor points but mostly good except for the last CL where I'm not sure yet what should we do for it

15:20:24
@emilazy:matrix.orgemily I was half-way through revising the stack and I need to fix stuff (the installCheckPhase bug was masking test failures and I broke the build rearranging things). I expect to get to finishing it off either today or tomorrow. it should be ok to review commit-by-commit and I don't think it will substantially change on my end other than fixes 15:23:08
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)If you need me for anything, please don't hesitate15:23:41
@raitobezarius:matrix.orgraitobezarius (DECT: 7248) Charles were you able to test the exp backoff for downloads CL? (no hurry) 15:24:08
@emilazy:matrix.orgemilythe bootstrap was successful and it seems to eliminate the majority of build directory references in built binaries. haven't yet got to testing Rust and there are things like Python and other parts of LLVM that hardcode random build directory paths regardless that will need fixing up. they are already non-reproducible in the presence of concurrency anyway though, I do not think further Nixpkgs fixes on that front need to block things15:24:29
@charles:computer.surgeryCharlesnot yet, sorry, i'll try to get to it today15:24:30
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)
In reply to @emilazy:matrix.org
the bootstrap was successful and it seems to eliminate the majority of build directory references in built binaries. haven't yet got to testing Rust and there are things like Python and other parts of LLVM that hardcode random build directory paths regardless that will need fixing up. they are already non-reproducible in the presence of concurrency anyway though, I do not think further Nixpkgs fixes on that front need to block things
So you confirm this doesn't suddenly explode nixpkgs though
15:24:54
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)which is great to hear15:24:56
@emilazy:matrix.orgemilyespecially since I don't know if they will get backported to 25.05, so just accepting that it will expose more reproducibility issues in Nixpkgs is part of the tradeoff regardless15:24:57
@emilazy:matrix.orgemilyyes, I'm running the stack and building lots of stuff15:25:13
@emilazy:matrix.orgemilyincluding https://gerrit.lix.systems/c/lix/+/3852/515:25:28
@raitobezarius:matrix.orgraitobezarius (DECT: 7248) sandbox = true in your case right? 15:25:36
@emilazy:matrix.orgemily I was a little nervous the ENOTSUP may not cover everything in practice but so far it seems to 15:25:40
@emilazy:matrix.orgemilyyeah15:25:44
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)very cool15:25:52
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)thank you so much for the chain!15:26:11
@emilazy:matrix.orgemilyI think the fixes will not substantially change the shape of the chain, so it's probably reviewable as-is, but I believe there are still one or two review comments I did not address anyway15:27:32
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)I rebased it and reran CI15:27:52
@emilazy:matrix.orgemilyI think a last-minute syntax error or something snuck in so CI results might not be that helpful past a certain point in the chain right now. I'll verify that it passes tests on Linux and Darwin and works on my machine before pushing out revisions though15:28:53
@emilazy:matrix.orgemilyI dropped it to fix CI once it became clear I had broken that15:29:12
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)Okie dokie15:29:18
@raitobezarius:matrix.orgraitobezarius (DECT: 7248) emily did a pass and +2ed everything I could reasonably do 15:45:51
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)I will leave the base32 helpers to other folks15:45:56

Show newer messages


Back to Room ListRoom Version: 10