lix-module.nixosModules.default seems to be dependent on the system nixpkgs #107
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
with lix-module 5e56f5a973e24 and lix faaa14a303dab (or even 2cea406121156):
others were unable to reproduce this. it seems this is happening because toml11 is still 3.7.1 in my system nixpkgs (i’m woefully out of date). how come the system nixpkgs matters here?
lix-module.nixosModules.default seems to be busted with lix mainto lix-module.nixosModules.default seems to be dependent on the system nixpkgsIf you set
lix.inputs.nixpkgs.follows = "nixpkgs", then your system nixpkgs matters. Withoutfollowsit would rely on the nixpkgs pinned in the lix module instead.hmm, even if i set
inputs.nixpkgs.followsto current nixos-25.11 where toml11 is indeed 4.4.0, it makes no difference (which i guess is consistent with the README saying it’s used for checks only). simplified:on the other hand, configuring an overlay that pulls in a stable release of lix from a newer nixpkgs seems to work: