nixos-option build failure on lix 2.91.0 #580
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#580
Loading…
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?
Describe the bug
Now that 24.11 is in beta, I've tried to upgrade.
Only problem is that nixos-option seems to fail to build.
Steps To Reproduce
and host configuration(not relevant)nix.package = inputs.lix-module.packages.x86_64-linux.default;
Now nixos-option fails to build and produces the following output:
Expected behavior
all works.
nix --version
outputnix (Lix, like Nix) 2.91.0
this doesn't seem to happen with cppnix
Disabling nixos-option seems to fix it.
Credit for finding that option to nobbz@discord
Nope this is probably behaviour considered a bug, even if the proximate cause here is a minor case of misuse. Given I've heard this a couple of times, I would like to know the change that actually causes this (and it may still wind up not a bug). It sounds suspiciously like the NixOS option nix.package has possibly grown a very ham fisted overlay recently and I'm going to have a look at it later; we may in fact just find out that this is just old lix-module versions not correctly overriding it anymore though.
Granted, you are misusing the lix NixOS module which may be the cause of your immediate issue and perhaps other sadness. That package output exists entirely for testing and nix.package should not be set to begin with when using the module; the intended mode of operation is that it acts as an overlay to replace pkgs.nix such that nix.package will magically become lix alongside all the other uses of pkgs.nix.
As per the installation guide or the module README, the way the module should be used is either by setting nixpkgs.overlays (or otherwise using the overlay) or by putting the module into imports. The alternative instructions which are being mixed with these ones are the ones which say purely
nix.package = pkgs.lix
which works as far as we know.Another problem which you are having is that your module is old and needs to be updated to module 2.91.1-1 which contains a substantial module refactoring affecting nixos-option which may well fix your problem. The latest version is listed in the installation guide on the Lix website.
the manual setting of nix.package was a workaround for an old issue. it may not be present anymore so I will remove that line.
Though please don't be rude here. A nicer phrasing would have been nice. No need to make me feel dumb for a minor misconfiguration.
I will update the module later and check back.
Hi, thank you evysgarden for opening this issue and jade for the explanation - would not have realized my Lix install was out of date, nor that the issue was even Lix-related (spent a lot of time trying to determine if it was a nixpkgs or even a Meson issue).
Can confirm that
nixos-option build failureto nixos-option build failure on lix 2.91.0alright, just to confirm @jade the misconfiguration is not the issue. though thx for pointing that out. I have now removed the line.
It seems to have been fixed now on 2.91.1-1 so I'm not sure how relevant it is to keep this issue open.
Hit the same issue, I did not have
nix.package
set, upgrading my Lix pin from2.91.0
to2.91.1-1
also fixed the issue.