!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

Load older messages


SenderMessageTime
13 Sep 2025
@emilazy:matrix.orgemilyhmm I think that wasn't there when I was looking at 2.93 :)05:24:18
@emilazy:matrix.orgemilywe could just patch that in Nixpkgs, though?05:24:45
@emilazy:matrix.orgemilyoh I guess it's breaking-ish05:24:53
@emilazy:matrix.orgemilysure then05:24:57
@k900:0upti.meK900Uhh is Lix on unstable also broken now15:33:45
@emilazy:matrix.orgemilyare you running into the CMake 4 thing15:45:57
@k900:0upti.meK900No15:48:59
@k900:0upti.meK900toml1115:49:02
@k900:0upti.meK900Wait no15:49:05
@k900:0upti.meK900Lowdown15:49:07
@k900:0upti.meK900I think15:49:08
@ghpzin:envs.netghpzin https://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.lix.x86_64-linux
https://hydra.nixos.org/build/307566238
lix/libcmd/liblixcmd.so.p/markdown.cc.o -c ../lix/libcmd/markdown.cc
../lix/libcmd/markdown.cc:18:10: error: field designator 'cols' does not refer to any field in type 'struct lowdown_opts'
   18 |         .cols = (size_t) std::max(windowWidth - 5, 60),
      |         ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lix/libcmd/markdown.cc:19:10: error: field designator 'hmargin' does not refer to any field in type 'struct lowdown_opts'
   19 |         .hmargin = 0,
      |         ~^~~~~~~~~~~
../lix/libcmd/markdown.cc:20:10: error: field designator 'vmargin' does not refer to any field in type 'struct lowdown_opts'
   20 |         .vmargin = 0,
      |         ~^~~~~~~~~~~
3 errors generated.
15:49:49
@raitobezarius:matrix.orgraitobezariushttps://github.com/NixOS/nixpkgs/pull/442624/files16:18:40
@raitobezarius:matrix.orgraitobezarius* https://github.com/NixOS/nixpkgs/pull/442624 FYI16:18:43
@marie:marie.cologneMarieAm I supposed to do the gerrit suggest owners thing and add reviewers? Or just be patient and wait for someone to look at it?17:34:18
@raitobezarius:matrix.orgraitobezariusYes, you need to use code owners19:52:27
@marie:marie.cologneMarieoh, okay It lists 3 people as code owners for my CL on release-2.93, but it doesn't list anyone on the one for main20:28:10
@raitobezarius:matrix.orgraitobezariusHm surprising 21:44:01
14 Sep 2025
@aloisw:julia0815.dealoisw Hm maybe the * in the code owners file doesn't work, and on 2.93 where there are no owners it falls back to the core team? 06:55:38
@aloisw:julia0815.dealoisw https://github.com/NixOS/nixpkgs/pull/435108#issuecomment-3289131700 did they fix the Ubuntu sandbox breakage on the other side of the fork? 07:03:46
@federicodschonborn:matrix.orgFederico Damián Schonborn (he/they) changed their profile picture.07:26:43
@raitobezarius:matrix.orgraitobezariusby sandbox breakage, are you thinking of the apparmor shaped things?12:15:25
@aloisw:julia0815.dealoisw Yes, precisely. The nix builds succeed per that comment so they must be doing something differently. 12:37:13
@emilazy:matrix.orgemilyhttps://github.com/NixOS/nixpkgs/pull/443012 would be good if someone could check my work (haven't verified the build)22:08:00
15 Sep 2025
@jade_:matrix.orgjade_yup. i think we might want to just throw a * into the codeowners of maintenance branches06:45:34
@aloisw:julia0815.dealoiswWell that doesn't seem to work at all per the behaviour observed by Marie.07:02:24
@jade_:matrix.orgjade_right, the codeowners plugin is set up in our configuration to fail closed07:49:58
@jade_:matrix.orgjade_we need to introduce an OWNERS file on the maintenance branches that just allows anyone with +2 to +2 anything because they're just maintenance branches07:50:28
@jade_:matrix.orgjade_i didn't see a CL to put an OWNERS file on release-*, which is probably why it is jacked07:51:06
@jade_:matrix.orgjade_or we could also add an exclusion in the config of release-* from codeowners entirely07:51:18

Show newer messages


Back to Room ListRoom Version: 10