27 Replies
huh, have the nix install changed, it worked when i tested it in a vm i think last month (i dont use nix on my system)
The only thing I can think of that seems like it could be relevant is I installed on a single ext4 partition, but I haven't noticed other problems from that.
just got home and about to head to bed but i will fire up my main pc and run a test
Thanks!
yeah installer has changed i believe so the old install is no longer valid
buggy installer, for some reason it fails on the first try, if you re-run the command again it will work...
My initial error is different from yours (Matches above), re-running gives the same as yours, re-running again repeats that error, removing the offending systemd files (.service and .socket) results in the initial error again
they shouldnt be there to begin with if nix was uninstalled properly 🤔
The initial install that fails doesn't cleanup and leaves them installed is what I gather.
its an issue with determinate systems installer for nix
i managed to replicate it just once
Hm. Guess I'll go post an issue with that convenient link.
Thanks for checking!
yeah i just uninstalled nix and rebooted the VM and tried again and it worked fine
so the error in the pic that i got is the only one i got after that i could not replicate
I think I have diagnosed the issue to a conflict with selinux. The nix installer is trying to load the systemd unit from the /nix path.
The just command copies it over to /etc/systemd/system afterwords, but it has already failed and I don't see it trying to enable it after that either
Running ujust nix -> install and then enabling the units by name seems to work.
if enabling it after the install is all that is needed i can easily fix that
I believe so
Avoiding or suppressing the error from the installer obviously would also be good
just give me the correct command and i will put it into config
cant suppress that as thats all on determinate systems installer, can suppress ALL errors if they go to stderr but that will benefit nobody
so instead just adding an echo at the end "fixing systemd service" and run the command is all that we will need
@Icy mind giving me the command that fixed it then i can copy it to config, unless you want to open a PR yourself to fix it 🙂
i dont mind guiding you how to if you have a github account and havent done it before
Sure, I'm just trying to figure out if there's an option in the installer to not try to start the units, the error bothers me
Well, maybe I'll get it later.
Anyway, I did
got a github account so i can co author you then 🙂 if not dont worry
great, i will get to this as soon as im able to 😄
I’m not sure it’s resulting in a working install yet to be clear, I’m just getting around to getting my dev environment set up (trying devbox) and I am running into errors with that. It has installed packages but is erroring when trying to run or shell so I haven’t figured that out yet
ok keep me posted then since i dont use nix myself, i will just make a draft if i get to this before you finish testing
I think that works. the installer self-test passed and now I'm down to fixing ntfs permissions.
ok i will make a pr then
just to make check with you, this is all that was needed right
https://github.com/ublue-os/config/commit/9099af8430c05d6f567eb856be82eb67e9f20ece
dont get to test before i go to work
I don't know about the removal part, but the enable part is what I did when i re-did it earlier
i added the disable on the removal just to be sure
habit from when i wrote my own installer scripts in bash