New troubles building simple standalone home-manager config #364
Answered
by
vic
raplonu
asked this question in
Help - Issues / Problem Solving / How To
-
|
Hey ! I'm trying to use home-manager with the default template on my ubuntu machine. I did the following: nix flake init -t github:vic/den#default
nix flake update denThen I uncommented this line: den.homes.x86_64-linux.tux = { };And finally ran: home-manager switch --flake .#tuxwhich returned the following error: error:
… while calling the 'head' builtin
at «https://releases.nixos.org/nixpkgs/nixpkgs-26.05pre948338.bcc4a9d9533c/nixexprs.tar.xz?narHash=sha256-V/p5M4cAMbu/MJBDn5YABy5QJgCFpsgrnXVVc2Uo5%2Bk%3D»/lib/attrsets.nix:1713:13:
1712| if length values == 1 || pred here (elemAt values 1) (head values) then
1713| head values
| ^
1714| else
… while evaluating the attribute 'value'
at «https://releases.nixos.org/nixpkgs/nixpkgs-26.05pre948338.bcc4a9d9533c/nixexprs.tar.xz?narHash=sha256-V/p5M4cAMbu/MJBDn5YABy5QJgCFpsgrnXVVc2Uo5%2Bk%3D»/lib/modules.nix:1160:7:
1159| // {
1160| value = addErrorContext "while evaluating the option `${showOption loc}':" value;
| ^
1161| inherit (res.defsFinal') highestPrio;
… while evaluating the option `den.homes.x86_64-linux.tux.instantiate':
(stack trace truncated; use '--show-trace' to show the full, detailed trace)
error: expected a string but found null: null
at «github:vic/den/6f2da36401ce851133e377a29712c0a7f382109c?narHash=sha256-RTNX98N2dLe/C51hqPQwutwKEI1WL7cyAPuKLMT86Bs%3D»/nix/lib/types.nix:169:44:
168| hostName = if nameWithHost then lib.last parts else null;
169| hostByName = den.hosts.${system}.${hostName} or null;
| ^
170| userByName = hostByName.users.${userName} or null;Any idea of what I did wrong ? Thanks in advance 🫰 |
Beta Was this translation helpful? Give feedback.
Answered by
vic
Apr 3, 2026
Replies: 1 comment 1 reply
-
|
Hey, you did nothing wrong, all the contrary you found a bug. fixed here, 7e18d2c |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
raplonu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey, you did nothing wrong, all the contrary you found a bug.
fixed here, 7e18d2c