!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

You have reached the beginning of time (for this room).


SenderMessageTime
25 Aug 2025
@raitobezarius:matrix.orgraitobezarius (https://git.lix.systems/lix-project/nixos-module) 16:37:38
@emilazy:matrix.orgemilyI think someone should just do a manual bump on those branches for now… I just don't have the energy to finish the cherry-picks16:53:21
@emilazy:matrix.orgemily all we really need is something we can fetchpatch in Nixpkgs 16:53:32
@emilazy:matrix.orgemilythough if the intermediate versions are being dropped then it's at least less of a pain16:53:47
@emilazy:matrix.orgemilywell I guess that would only be 2.9216:54:03
@emilazy:matrix.orgemily I just want the toml11 thing to be over (but also not sure when Nix is going to re-land the changes now that Nixpkgs is fixed either; cc Sergei Zimmerman (xokdvium)?) 16:54:32
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)We had a backporting bananza for 25.05 with the nixpkgs test fix. Ran out of steam somewhere along manual backports for nixfmt/nix 2.3 removal e.t.c for 4 branches.17:16:49
@emilazy:matrix.orgemily4 branches? 🤔17:33:44
@raitobezarius:matrix.orgraitobezarius
In reply to @emilazy:matrix.org
I think someone should just do a manual bump on those branches for now… I just don't have the energy to finish the cherry-picks
i can but this will happen only when my burnout gauge is recharged
17:34:52
@raitobezarius:matrix.orgraitobezariusfor now, every little energy i have is spent on durable automation17:35:04
@raitobezarius:matrix.orgraitobezarius(because it makes me happier)17:35:11
26 Aug 2025
@jade_:matrix.orgjade_

I have given a bunch of people including emily, thubrecht , EsperLily [she/her] , just1602, Linux Hackerman Code-Review+2 access as it seemed silly that y'all didn't have it. in practice this just lets you stamp packaging or docs due to our CODEOWNERS configuration, but if you want to take responsibility for reviews on more of the tree feel free to send a CL to add yourself to CODEOWNERS in your areas.

the people in this list were selected basically arbitrarily based on a subset of people who I have noticed has a very consistent pattern of having good taste and who have some commits since May. most have commit access in our other repos as well already. if anyone else doesn't have and wants +2 access please let me know and i can raise it with the core team.

01:02:40

Show newer messages


Back to Room ListRoom Version: 10