| 2 Apr 2026 |
TechWiz | * hi I'm trying to update from 2.94.0 to 2.95.1 and I got `WARNING: manual intervention will be required to complete this Lix install! The Lix daemon is now an instanced unit that is fully socket-activated.
This requires a new systemd unit: nix-daemon@.service
'nix upgrade-nix' will provide a profile with a new Lix, likely one of: /nix/var/nix/profiles/default /nix/var/nix/profiles/per-user/root/profile It will have the instanced systemd unit file at 'lib/systemd/system/nix-daemon@.service'
You should symlink or copy this file to '/etc/systemd/system/nix-daemon@.service', and then run 'systemctl daemon-reload && systemctl restart nix-daemon.socket'. Until you do that, all nix commands will require root and '--store local'.`
I'm trying to symlink said file lib/systemd/system/nix-daemon@.service to /etc/systemd/system/nix-daemon@.service but it's not there to begin with?
| 09:07:52 |
TechWiz | * hi I'm trying to update from 2.94.0 to 2.95.1 and I got WARNING: manual intervention will be required to complete this Lix install! The Lix daemon is now an instanced unit that is fully socket-activated.
This requires a new systemd unit: nix-daemon@.service
'nix upgrade-nix' will provide a profile with a new Lix, likely one of: /nix/var/nix/profiles/default /nix/var/nix/profiles/per-user/root/profile It will have the instanced systemd unit file at 'lib/systemd/system/nix-daemon@.service'
You should symlink or copy this file to '/etc/systemd/system/nix-daemon@.service', and then run 'systemctl daemon-reload && systemctl restart nix-daemon.socket'. Until you do that, all nix commands will require root and '--store local'.
I'm trying to symlink said file lib/systemd/system/nix-daemon@.service to /etc/systemd/system/nix-daemon@.service but it's not there to begin with?
| 09:08:39 |
TechWiz | * hi I'm trying to update from 2.94.0 to 2.95.1 and I got
WARNING: manual intervention will be required to complete this Lix install!
The Lix daemon is now an instanced unit that is fully socket-activated.
This requires a new systemd unit: nix-daemon@.service
'nix upgrade-nix' will provide a profile with a new Lix, likely one of:
/nix/var/nix/profiles/default
/nix/var/nix/profiles/per-user/root/profile
It will have the instanced systemd unit file at 'lib/systemd/system/nix-daemon@.service'
You should symlink or copy this file to '/etc/systemd/system/nix-daemon@.service',
and then run 'systemctl daemon-reload && systemctl restart nix-daemon.socket'.
Until you do that, all nix commands will require root and '--store local'.
I'm trying to symlink said file lib/systemd/system/nix-daemon@.service to /etc/systemd/system/nix-daemon@.service but it's not there to begin with?
| 09:09:55 |
TechWiz | * hi I'm trying to update from 2.94.0 to 2.95.1 and I got
WARNING: manual intervention will be required to complete this Lix install!
The Lix daemon is now an instanced unit that is fully socket-activated.
This requires a new systemd unit: nix-daemon@.service
'nix upgrade-nix' will provide a profile with a new Lix, likely one of:
/nix/var/nix/profiles/default
/nix/var/nix/profiles/per-user/root/profile
It will have the instanced systemd unit file at 'lib/systemd/system/nix-daemon@.service'
You should symlink or copy this file to '/etc/systemd/system/nix-daemon@.service',
and then run 'systemctl daemon-reload && systemctl restart nix-daemon.socket'.
Until you do that, all nix commands will require root and '--store local'.
I'm trying to symlink said file /lib/systemd/system/nix-daemon@.service to /etc/systemd/system/nix-daemon@.service but it's not there to begin with?
| 09:10:46 |
TechWiz | * hi I'm trying to update from 2.94.0 to 2.95.1 and I got
WARNING: manual intervention will be required to complete this Lix install!
The Lix daemon is now an instanced unit that is fully socket-activated.
This requires a new systemd unit: nix-daemon@.service
'nix upgrade-nix' will provide a profile with a new Lix, likely one of:
/nix/var/nix/profiles/default
/nix/var/nix/profiles/per-user/root/profile
It will have the instanced systemd unit file at 'lib/systemd/system/nix-daemon@.service'
You should symlink or copy this file to '/etc/systemd/system/nix-daemon@.service',
and then run 'systemctl daemon-reload && systemctl restart nix-daemon.socket'.
Until you do that, all nix commands will require root and '--store local'.
I'm trying to symlink said file /lib/systemd/system/nix-daemon@.service to /etc/systemd/system/nix-daemon@.service but it's not there to begin with?
| 09:10:57 |
TechWiz | * hi I'm trying to update from 2.94.0 to 2.95.1 w/ the Lix shell script and I got
WARNING: manual intervention will be required to complete this Lix install!
The Lix daemon is now an instanced unit that is fully socket-activated.
This requires a new systemd unit: nix-daemon@.service
'nix upgrade-nix' will provide a profile with a new Lix, likely one of:
/nix/var/nix/profiles/default
/nix/var/nix/profiles/per-user/root/profile
It will have the instanced systemd unit file at 'lib/systemd/system/nix-daemon@.service'
You should symlink or copy this file to '/etc/systemd/system/nix-daemon@.service',
and then run 'systemctl daemon-reload && systemctl restart nix-daemon.socket'.
Until you do that, all nix commands will require root and '--store local'.
I'm trying to symlink said file /lib/systemd/system/nix-daemon@.service to /etc/systemd/system/nix-daemon@.service but it's not there to begin with?
| 09:13:46 |
K900 | It is in your profile path | 09:16:57 |
TechWiz | ah, duh, right | 09:17:26 |
K900 | So /nix/var/nix/profiles/default/lib/... | 09:17:29 |
TechWiz | ty | 09:17:35 |
| TechWiz set a profile picture. | 09:18:28 |
| TechWiz changed their profile picture. | 09:19:06 |
drab | FYI per the support matrix on https://git.lix.systems/lix-project/lix-installer it does not seem to support non-root installs of lix for x86 or aarch linux (the "root only" column is checked). I think (?) you might be able to do non-root lix via the static binary on hydra, but I haven't tested this. URL is https://hydra.nixos.org/job/nixpkgs/trunk/lixStatic.x86_64-linux/latest/download-by-type/file/binary-dist for the x86_64 linux binary if you want to see if it works for you. There's a blog post on using static nix at https://zameermanji.com/blog/2023/3/26/using-nix-without-root/ that might be relevant (i.e. getting around /nix/store) | 12:56:10 |
tebriel | 80/80 installcheck - lix:fuctional2 is failing on my m4 Mac. Says 418/420 subtests passed, has anyone else seen this on 2.95.1? | 16:30:21 |
raitobezarius | do you have more details on which test of f2 failed? | 16:30:40 |
raitobezarius | (if you want to open an issue with details, that'd be welcome) | 16:31:03 |
tebriel | I have the nix log but haven’t found the subtest details. I’ll do so thanks. | 16:31:15 |
tebriel | #1173 still trying to wrangle the nix log to see the subtest failures if you have any advice there I’d love it. | 16:37:32 |
raitobezarius | what if you try to look at all processes running | 16:47:12 |
raitobezarius | normally you will see pytest process names | 16:47:18 |
raitobezarius | perhaps you will see the "stuck" process name in the process name | 16:47:24 |
tebriel | Also interesting the output seems to be misaligned with things like 7709stests passed and 248.19s exit status 1ssed | 17:02:59 |
tebriel | Never say a pytest proc that had stuck in the name, will keep searching | 17:13:18 |
tebriel | * Never saw a pytest proc that had stuck in the name, will keep searching | 17:13:35 |
raitobezarius | darn | 17:21:06 |
raitobezarius | I'm asking the F2 experts on this | 17:21:09 |
Rutile (rootile) | Cab you build with --keep-failed and send the meson testlog.txt? | 17:26:02 |
Rutile (rootile) | Also, we should re-open the discussion about tap, as this hasnt been the first time people need to dig deep to figure out what failed :/ | 17:26:35 |
Yureka (she/her) | which package are you building specifically? there was a recent issue with the nixpkgs packaging on mac os | 17:29:24 |
nightuser | I'm getting errors like error: NAR info file '4dh8j6q43apjc62yjp1fwxh55l2qrzhx.narinfo' is corrupt: expecting '\n' at line 2. The issue disappears when I specify --option substituters https://cache.nixos.org, and indeed curl https://cache.nix.systems/4dh8j6q43apjc62yjp1fwxh55l2qrzhx.narinfo gives the correct output while curl https://cache.lix.systems/0z54cs3y9xif48f4zvgnfgsnzva0fv8y.narinfo outputs some binary data (but still with status code 200). | 17:40:25 |