-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS: /etc/bashrc
and /etc/zshrc
converted from links to regular files each reboot
#721
Comments
/etc/bashrc
and /etc/zshrc
converted from links to regular files each reboot
I believe this may be caused by #672 . 🤔 |
/etc/bashrc
and /etc/zshrc
converted from links to regular files each reboot/etc/bashrc
and /etc/zshrc
converted from links to regular files each reboot
/etc/bashrc
and /etc/zshrc
converted from links to regular files each reboot/etc/bashrc
and /etc/zshrc
converted from links to regular files each reboot
Thanks for the reply @Hoverbear. Yes, I was running nix from the determinate installer installed a few months ago that didn't experience this behaviour, so something has regressed since then. (it was also on macOS Sonoma back then) |
Yes, I'm seeing this behavior as well with dac0adc. |
We're investigating, thanks for this report. We are cutting a new release soon, it may not have a fix for this specific problem, that'll have to wait for a future release. |
+1, experiencing this too and it makes using
|
I discussed this with @grahamc and the planned solution would be to not do the shell recovery if the files are symlinks. |
This should be fixed in the next release! |
Love it, thank you!! |
@Hoverbear tysm! |
I am hit by the same issue. I guess in the meantime I can disable What will be the process of upgrading from |
Yes it will be that. I expect we'll cut a new release soon -- Sorry about the delay. The holidays are a thing. 😅 |
I'm a bit lost on the upgrading steps.
Though after that |
Those should be the steps! The installer looks for the binaries |
I tried to just run the installer again, but it prompted me to uninstall or just upgrade nix. So I figured I had to uninstall/reinstall. So I did the dance, but failed with a bunch of issues related to APFS etc. Had to reboot and clean up the remnants manually (I looked at the regular nix docs for some inspiration). After that was done I rebooted and re-ran the installer and applied my flake again, it worked well. After another reboot it all seems to work fine, I don't have this issue anymore! 😄 Thanks a lot for fixing this! 🙏 ❤️ It would be great to have a way to upgrade the hooks/helpers that this nix-installer puts in place w/o having to completely nuke the entire installation. 😊 |
@eripa I'm sorry about the apfs issues! Out of curiousity was this on Sonoma with Filevault? |
No problem @Hoverbear, I'm using macoS Sonoma with Filevault yes (fresh install, new computer) |
Okay, we've seen several reports of the same situation. |
I believe this was fixed by #767 (which was released in https://github.com/DeterminateSystems/nix-installer/releases/tag/v0.16.0) -- please let me know if that is not the case! |
Hi,
I have a slightly different issue than #593, but seem related. The workaround in #593 only checks the content of the file, and not the file type. I'll try and get a PR submitted.
Instead of the below files being overwritten on upgrades, each time I reboot my machine the symbolic links are dereferenced and "converted" to real files.
Before reboot (symlinks):
After reboot (regular files):
Which then results in:
nix installed via using the Determinate systems installer 0.14.0.
macOS:
Installation receipt:
receipt.json
The text was updated successfully, but these errors were encountered: