3 ms·

> The Nix shell script installer is a one-time that you can rerun without it reinstalling Nix (it will just skip if it detects an already existent Nix). Guix re

by mbakke 6y ago

> The Nix shell script installer is a one-time that you can rerun without it reinstalling Nix (it will just skip if it detects an already existent Nix). Guix reinstalls (and take forever doing it). Wait, what? The Guix installer script also stops if it detects an existing installation, and has done so since the initial commit: https://git.savannah.gnu.org/cgit/guix.git/tree/etc/guix-install.sh#n297 https://git.savannah.gnu.org/cgit/guix.git/tree/etc/guix-ins... > You also need to make sure you import keys when installing Guix because security. If you are complaining that the installer verifies the GPG signature of a file it downloaded from the internet, I don't know what to say. :-) > Doing any package related thing will tell you about a failure to install locale. This can happen when your installed locales are from a different glibc than what the guix-daemon was built with. Upgrading and restarting the daemon will solve it. That said, I think the daemon recently got smarter about it. > Guix should lean into this one major strength and put out an Emacs-centered heavily opinionated installer image that uses EXWM for its window manager. The system installer disk image does give you an option to create an EXWM system (as well as GNOME, Xfce, etc).

emptysongglass 6y ago
> Wait, what? The Guix installer script also stops if it detects an existing installation, and has done so since the initial commit: You're right about this, apologies. What I intended to convey was that Guix hard bails on an install so can't be scripted as part of a "dotfiles up" on a new system. Nix gracefully bails and can therefore be scripted. > This can happen when your installed locales are from a different glibc than what the guix-daemon was built with. Upgrading and restarting the daemon will solve it. This is from 5 minutes ago. I have both glibc-locales and glibc-utf8-locales installed: /gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) > If you are complaining that the installer verifies the GPG signature of a file it downloaded from the internet, I don't know what to say. :-) Speaking strictly from the perspective of a desktop end-user, this should probably be rolled into the one-liner. And, as I'm testing, I also notice that even for operations which require no changes, a guix pull takes 5 or more minutes over the equivalent nix operation. Why am I building guix-system for 5 minutes with nothing to be done? I urge you to take all of this as friendly advice from someone who fits into the market category of Guix's next million users. How you capture them is by removing the barriers to entry, streamlining the package management process, and massaging over papercuts that a brand-new user won't have the patience for. > The system installer disk image does give you an option to create an EXWM system (as well as GNOME, Xfce, etc). This is awesome. :-D
- mbakke 6y ago
  > This is from 5 minutes ago. I have both glibc-locales and glibc-utf8-locales installed: > /gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) Right. The problem here is that you haven't updated the guix-daemon since you installed Guix. To get the fix rekado mentioned, you need to 'guix pull && guix upgrade' as root and restart the daemon. (I can tell because you're using bash 5.0.7 from 1+ year ago) You can also change the systemd service to use guix-daemon from your users Guix instead of 'root'. Arguably the installer could ask whether to do this, although users probably won't understand the security implications. > And, as I'm testing, I also notice that even for operations which require no changes, a guix pull takes 5 or more minutes over the equivalent nix operation. Why am I building guix-system for 5 minutes with nothing to be done? That happens when there are no substitutes available for 'guix pull'. Work is ongoing in improving the compiler performance, but this is mostly "bad luck" (because you pulled a commit not yet built by the CI). Wrt scriptability of the installer, IIUC the problem is that it returns "1" when a previous installation was detected? You can easily account for that in your "dotfiles up" script, no? Similarly, if you add the GPG key to your dotfiles you no longer have to download it every time.

by mbakke 6y ago

emptysongglass 6y ago

> Wait, what? The Guix installer script also stops if it detects an existing installation, and has done so since the initial commit: You're right about this, apologies. What I intended to convey was that Guix hard bails on an install so can't be scripted as part of a "dotfiles up" on a new system. Nix gracefully bails and can therefore be scripted. > This can happen when your installed locales are from a different glibc than what the guix-daemon was built with. Upgrading and restarting the daemon will solve it. This is from 5 minutes ago. I have both glibc-locales and glibc-utf8-locales installed: /gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) > If you are complaining that the installer verifies the GPG signature of a file it downloaded from the internet, I don't know what to say. :-) Speaking strictly from the perspective of a desktop end-user, this should probably be rolled into the one-liner. And, as I'm testing, I also notice that even for operations which require no changes, a guix pull takes 5 or more minutes over the equivalent nix operation. Why am I building guix-system for 5 minutes with nothing to be done? I urge you to take all of this as friendly advice from someone who fits into the market category of Guix's next million users. How you capture them is by removing the barriers to entry, streamlining the package management process, and massaging over papercuts that a brand-new user won't have the patience for. > The system installer disk image does give you an option to create an EXWM system (as well as GNOME, Xfce, etc). This is awesome. :-D

mbakke 6y ago
> This is from 5 minutes ago. I have both glibc-locales and glibc-utf8-locales installed: > /gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) Right. The problem here is that you haven't updated the guix-daemon since you installed Guix. To get the fix rekado mentioned, you need to 'guix pull && guix upgrade' as root and restart the daemon. (I can tell because you're using bash 5.0.7 from 1+ year ago) You can also change the systemd service to use guix-daemon from your users Guix instead of 'root'. Arguably the installer could ask whether to do this, although users probably won't understand the security implications. > And, as I'm testing, I also notice that even for operations which require no changes, a guix pull takes 5 or more minutes over the equivalent nix operation. Why am I building guix-system for 5 minutes with nothing to be done? That happens when there are no substitutes available for 'guix pull'. Work is ongoing in improving the compiler performance, but this is mostly "bad luck" (because you pulled a commit not yet built by the CI). Wrt scriptability of the installer, IIUC the problem is that it returns "1" when a previous installation was detected? You can easily account for that in your "dotfiles up" script, no? Similarly, if you add the GPG key to your dotfiles you no longer have to download it every time.