sudo nixos-rebuild gives an error when using lix #407

Closed
opened 2024-06-20 05:51:31 +00:00 by computerscience-person · 1 comment

Describe the bug

When rebuilding NixOS, evaluating lix seems to give an error.

error: evaluation aborted with the following error message: 'lib.customisation.callPackageWith: Function called without required argument "build-release-notes" at /nix/store/path-to-lix-source/package.nix:16'

On line 16, an input for build-release-notes seems to be needed, but it can't find it for some reason.

Steps To Reproduce

  1. Build NixOS with lix. (I just followed the flake-based configuration outlined here.)

Expected behavior

Successful NixOS rebuild

nix --version output

nix (Lix, like Nix) 2.90.0-beta.1-lixpre20240506-b6799ab

Additional context

I have also noticed that nix/lix doesn't seem to use the substituters in my nix.settings.substituters option when building Lix, and so it rebuilds lix locally instead of pulling it from a cache. Maybe I've done something wrong with my setup?

Configuration file

## Describe the bug When rebuilding NixOS, evaluating `lix` seems to give an error. `error: evaluation aborted with the following error message: 'lib.customisation.callPackageWith: Function called without required argument "build-release-notes" at /nix/store/path-to-lix-source/package.nix:16'` On line 16, an input for `build-release-notes` seems to be needed, but it can't find it for some reason. ## Steps To Reproduce 1. Build NixOS with lix. (I just followed the flake-based configuration outlined [here](https://lix.systems/add-to-config/#flake-based-configurations).) ## Expected behavior Successful NixOS rebuild ## `nix --version` output `nix (Lix, like Nix) 2.90.0-beta.1-lixpre20240506-b6799ab` ## Additional context I have also noticed that nix/lix doesn't seem to use the substituters in my `nix.settings.substituters` option when building Lix, and so it rebuilds lix locally instead of pulling it from a cache. Maybe I've done something wrong with my setup? [Configuration file](https://github.com/computerscience-person/nix-configuration/tree/lix-error)
computerscience-person added the
bug
label 2024-06-20 05:51:31 +00:00
Owner

hi! This is caused by using Lix 2.90-beta.1 and is fixed by changing your reference for the lix-nixos-module to 2.90.0-rc1 and removing the inputs.lix.follows piece. We have rewritten the website guide to match this.

As for why the cache was busted, it's because we don't build lix against each new version of nixpkgs, due to not having automatic CI pushing to the cache. If a local build is problematic for you and you don't care about stuff like nix-eval-jobs and so on, you can set nix.package = pkgs.lix, which will get working caching since it is simply in nixpkgs.

Our website fell out of date because the module was not pinned to a version appropriate to build tagged versions of lix and consequently you got that build error with beta 1 plus main on the module. Thanks to @drupol and I, we have ... after an embarrassingly long time of it being wrong ... rewritten the incorrect parts of the website guide: lix-project/lix-website#29

hi! This is caused by using Lix 2.90-beta.1 and is fixed by changing your reference for the lix-nixos-module to `2.90.0-rc1` and removing the `inputs.lix.follows` piece. We have rewritten the website guide to match this. As for why the cache was busted, it's because we don't build lix against each new version of nixpkgs, due to not having automatic CI pushing to the cache. If a local build is problematic for you and you don't care about stuff like nix-eval-jobs and so on, you can set `nix.package = pkgs.lix`, which will get working caching since it is simply in nixpkgs. Our website fell out of date because the module was not pinned to a version appropriate to build tagged versions of lix and consequently you got that build error with beta 1 plus `main` on the module. Thanks to @drupol and I, we have ... after an embarrassingly long time of it being wrong ... rewritten the incorrect parts of the website guide: https://git.lix.systems/lix-project/lix-website/pulls/29
jade closed this issue 2024-06-20 06:58:58 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#407
No description provided.