!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

Load older messages


SenderMessageTime
18 Aug 2025
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)either way, just please let me know what you prefer14:52:08
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)we can revert the entire series if you prefer it that way as well14:52:15
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)it's indeed "author-submits-the-thing" but with large stacks which receives a lot of attention and due to fast forward only, i take care of playing the merge queue until we have one14:52:52
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)(if we had a merge queue, your changes would have been sent too probably because they would have been ready to submit)14:53:28
@winter:catgirl.cloudWinter ah, okay. maybe consider doing one, or adding the patch to the module? i imagine more ppl on unstable will start complaining 😉 15:05:36
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)yep, we should do that, thanks15:05:58
@emilazy:matrix.orgemilythis stack includes the changes that make build directories always nondeterministic on Darwin, to be clear15:31:39
@emilazy:matrix.orgemilyit looks like the diff I had locally for that part of the stack was only cosmetic. I have been running the entire stack for a long while now and it has not caused me problems, though I have not tested the prefix you merged very extensively and it still produces rather long build directories. I was hoping to resolve the remaining questions soon and waiting on your review for the nested directory stuff15:32:50
@emilazy:matrix.orgemilybut it should be harmless given I didn't have significant unpushed changes and the code is good15:33:02
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)got it, still, I have to ask: is there any action you want to take regarding the merge?15:33:15
@emilazy:matrix.orgemilystill some more communication would have been nice if it was urgently wanted, I was asleep for the two hours between ping and merge15:33:24
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)i.e. a revert or X or Y where X or Y can be 'let's do nothing for now' :P15:33:26
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)I apologize for the communication and from now on, I will communicate for your stacks15:33:39
@emilazy:matrix.orgemilyI think let's do nothing and I will try to come back to the rest of the stack soon. but if you could finish reviewing the CL you have +1 on that would help15:33:48
@emilazy:matrix.orgemilysince I assumed the work was blocked on that15:33:53
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)(again: it was not urgently wanted but this was my Morning routineâ„¢ of merging things that are lingering)15:34:22
@emilazy:matrix.orgemilyI expect to get back to building my system closure ~today-ish15:34:25
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)alright, thanks!15:34:45
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)will prioritize the last pieces15:34:51
@emilazy:matrix.orgemily(FWIW I think "committers always merge" or "authors always merge" is probably a better norm than it depending, for the usual Gerrit reasons of "it's obvious whose turn it is" + knowing expectations for how you should communicate if some work is pending on some testing to obtain full confidence or such)15:35:59
@emilazy:matrix.orgemily(though for stuff like urgent fixes or security stuff the latter can be a pain I guess)15:36:14
@emilazy:matrix.orgemilyNixpkgs has some problems with this too. (where two parties in a PR will deadlock waiting for the other to hit the button)15:36:33
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)(I'd also prefer that but the merge queue situation means that I have more people demanding why something is not merged than anything and teaching everyone about Gerrit's etiquette takes a lot of energy)15:36:39
@raitobezarius:matrix.orgraitobezarius (DECT: 7248) (so I have a more complicated hybrid strategy where I do take care of things and do merge things) 15:36:50
@emilazy:matrix.orgemilymerge queues would be very nice15:36:55
@emilazy:matrix.orgemilyhaving two stacks that you have to babysit the rebase ordering of to get the tests happy to merge is tedious15:37:10
@emilazy:matrix.orgemilydoes the Snix thing for that not work well?15:37:16
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)It has bugs and it would take much more energy to take care of these bugs or cleanup after a massive disaster in production15:37:36
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)So until I have a window of opportunity for removing this painpoint, manual and tedious is fine as I have a bird view of everything and I know my way through all the ecosystem easily15:38:27
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)The only problem are well, these situations :)15:38:32

Show newer messages


Back to Room ListRoom Version: 10