Arch Linux User Repository

OK, so we have upgraded to 2.3.1. I also removed the hard dependency on archlinux-nix, as I got some feedback that not everyone wants to use this, so it's now optdepends.

@jsomedon, please try systemctl enable nix-daemon.socket. PS. This package is out of date, but the upgrade doesn't seem straight-forward, so if anyone has had any luck compiling 2.3, your help would be much appreciated!

I just installed and I am trying to set things up by following wiki.

I get this error:

error: cannot connect to daemon at '/nix/var/nix/daemon-socket/socket': No such file or directory

upon running this command:

nix-channel --add https://nixos.org/channels/nixpkgs-unstable nix-channel --update nix-env -u

I've created https://wiki.archlinux.org/index.php/Nix, let's collect there all tips and tricks how get Nix worked on Arch.

Ok, so I've cleaned up my helper script and uploaded it to AUR. It's now listed as a dependency for this package and does the following:

• handles setting up of build users (previously in the .install file)
• downloads binaries from nixpkgs to use in the build sandbox, lists them in nix.conf
• handles launching/enabling of nix-daemon

This should all be done automatically when this package is installed/upgraded. Hopefully this resolves all the issues people are seeing with nix-channel --update. If not, let me know.

Linking this discussion from #nixos: https://logs.nix.samueldr.com/nixos/2019-02-06#1938291

In summary, compiling nix from "outside" of nix hardcodes some paths like /usr/bin/bash, /usr/bin/mkdir, ... in the compiled binary. So in theory it could fail anywhere (however I only ever had the problem with nix-channel), and not much can be done against it apart from compiling all those tools statically and adding them to the sandbox path.

It’s quite sad actually...

@asppsa: Ok, sorry I missed that part of the discussion.

nix-channel --update doesn’t work either for me (I don’t use nix-channels), but I think it’s a global nix problem, not a packaging one: nix-channel is getting abandoned little by little and replaced with other mechanisms (I know, it’s still too present in configurations, I’m not the one making the changes :p ).

A workaround to make nix-channel work is to set sandbox = false in /etc/nix/nix.conf (and restart nix-daemon.service) while using this command, although I would recommend using that setting only for that command (and set it to true, the default since nix 2.1, for the rest of the time)

The proposed change with dash-static is for the rest of the nix commands (nix-build in particular). It is not used if you have sandbox = false. Any static sh-like could do the job but Archlinux doesn’t package any, so I had to package it myself

@immae, ok I've added editline. I'm still finding however that dash-static doesn't fix the issues with nix-channel --update.

@janat08 could you elaborate on what the issue you are seeing is? Is it the nix-channel error, or something else?

The install is unusable, and prevents a proper install with sh script. beautiful.