<Apteryx>I have no idea how services are start, haven't investigated that part of the system yet :) But I'm using the lightweight desktop base config, which I believe only manage services with Shepherd, AFAIU.
<albertoefg>oh i normally found video tutorials easy so u can see exactly what happens in terminal and the person explains what is going on :)
<Apteryx>jmd: I for one found the GuixSD install procedure enlighting and empowering (thanks to the good info manual). But command line is not for everyone. I have coworkers, programmers, mind you, that are horrified at the idea of having to use a terminal.
<albertoefg>:( ok i am sorry i wasn't trying to speak bad of anyone nor guix
<Apteryx>albertoefg: Didn't get it that way! It's nice to get feedback, whatever it is!
<Apteryx>If GuixSD is to appeal to larger demographics it will need to become easier to install for sure.
<Apteryx>rekado: Thanks! And sorry for interrupting your studies :D
<jmd>Whenever I use one I'm constantly bombarded with yes/no questions.
<jmd>and I always find myself worring: "I wonder what it's actually going to do if I say yes?"
<jmd>For that reason I think most people prefer a command like interface where the *user* explicitly says what should be done.
<jmd>However some people have expressed interest in a gui - so I want to know exactly what they expect in one. What would you expect?
<rekado>I find command line interfaces difficult to explore. ‘--help’ isn’t always helpful as the scope of commands grows. In my opinion, a GUI should help users to assemble a series of commands by initially hiding complexity and revealing it step-wise in a controlled fashion.
<rekado>Apteryx: no problem. I’m not very successful right now anyway :)
<Apteryx>Maybe one thing that I did before this problem occured was to point my /root/.config/guix/latest to ~/.config/guix/latest as recommended in the manual ("If you are the sole user of your system, you may also
<Apteryx>consider pointing the ‘/root/.config/guix/latest’ symlink to point to
<Apteryx>‘~/.config/guix/latest’; this way it will always use the same ‘guix’ as
<Apteryx>I'm not familiar with installing Guix on a foreign distro, but glancing over the installation section of the manual, it seems that you'd have to remove /gnu/store, /var/guix and ~/.guix-profile to undo the actions there, +++ PATH, services, etc.
<albertoefg1>SELinux is preventing (x-daemon) from execute access on the file guix-daemon.
<Apteryx>I'm facing the regression that my guix cannot uses substitute from mirror.hydra.gnu.org because of the HTTPS regression that has already been fixed in master; As a result, I can't even update my guix using the usual "guix pull" (fails with the invalid cert error). Can I get out of this catch22 situation using my git checkout?
<alezost>albertoefg1: ok, now you can try "guix build --dry-run hello"
<Apteryx>alezost: OK. I'll just point my ~/.config/guix/latest to it then :). I thought there was something special about a git checkout that if I ran "guix gc" it would collect stuff which guix rely on, such as guile, and break the system.
<alezost>Apteryx: no, it doesn't matter, both "guix pull" and latest git checkout have the same code
<alezost>albertoefg1: it is explained in the manual (info "(guix) Application Setup") how to solve the locale warning; as for the https_proxy thing, I've never seen it, the rest is ok. So now you can try to install something
<len__>I can not install wpa_supplicant it says that it is unrecognised package
<alezost>albertoefg1: well, fedora's emacs will not find *.el files inside ~/.guix-profile, so you need to use guix's emacs if you want to use emacs packages from guix (including emacs interface for guix itself)
<alezost>for example, if you do "guix package -i magit", and start fedora's emacs, you will not "M-x magit-status" command
<len__>It lasted more than a month since installation and than flashing new bios ...
<rekado>for work I now must publish status updates to Google docs each week. Does anyone know of a tool that allows me to do this a) without a google account and b) from the command line / within Emacs?
<necrophcodr>I've install Guix on a non-GuixSD system, and I'm wondering if it's possible to take my user-profile with me to another location?
<necrophcodr>But without all the files and folders and structures
<necrophcodr>Just a general file that can recall the exact generation on a different platform
<rekado>necrophcodr: this can be achieved with manifests
<rekado>a manifest is a file in which you declare the contents of your profile
<rekado>you can instantiate a manifest with ‘guix package --manifest=/path/to/manifest.scm’
<rekado>alternatively, you can export the closure of your profile and import the exact same binaries on another Guix system.
<superflip>I am trying to run gnome on Debian stable using guix. So I ran "guix package -i gnome". When I try to run gnome using "DISPLAY=:1 gnome-session", I get "dbus-update-activation-environment: error: unable to connect to D-Bus: /gnu/store/3s8ifq6vpdykaw695k4b083xwrsvc3k5-dbus-1.10.8/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed." and "** (gnome-session-failed:3532): WARNING *
<Apteryx>Just to be sure about one thing: When I use a git checkout as my ~/.config/guix/latest, to update, I just run
<Apteryx>git pull... Then I need to rebuild guix if I want the new guix version using "guix environment guix", "make -j3 check"?
<Apteryx>Not sure I need the "guix environment guix" part.
<necrophcodr>rekado, oh my god, that was amazing. thank you so much for the explanation of how it works, and the links for me to read on about it. i surely will too! this will help me be a lot more productive at work, thanks!
<Apteryx>This means I'd never need to issue "git pull" anymore.
<Apteryx>rekado: This won't do. The certificates are installed and the envars point to these. I believe the problem is that mirror.hydra.gnu.org doesn't have a certificate and it was being validated. The commit you referenced turns validation off for certain situations where it doesn't matter.
<rekado>necrophcodr: I’m glad you found this helpful. That’s the documentation for the Guix deployment at the institute where I work. Note that all instances of ‘guixr’ should be ‘guix’ (unless you’re on one of our institute’s machines.)
<rekado>Apteryx: hmm, I had a problem with cert checking for substitutes on Friday at work and I fixed it by setting SSL_CERT_DIR in the daemon’s environment.
<necrophcodr>rekado, which i'm not, but i figured as much. i'm using per-user profiles, can the manifest files be used from those directly then? that is, the manifest files in, for instance, $HOME/.guix-profile/manifest ?
<necrophcodr>they appear to, but i wanted to be sure before i test it out and ruin test environments too much ;)
<civodul>Apteryx, rekado: re the TLS error in 'guix substitute', i fixed it earlier today
<civodul>i sent a message today, though i can't find it
<necrophcodr>rekado, it says in the docs that "file must return a manifest object, which is roughly a list of packages: ", which it appears the `manifest` file does, so it should work :) i'll do a bit of testing, but i've got a good feeling about this guix deal.
<Apteryx>I've linked my ~/.config/guix/latest to ~/src/guix (my git checkout). Does that mean that any guix commands from now on get run from the binaries under ~/src/guix?
<Apteryx>I just tried "sudo herd restart guix-daemon", then "guix build hello", but I still get the cert error. Maybe I have to logout & back in after pointing ~/.config/guix/latest to my git checkout?
<Apteryx>Because right now, `which guix` returns "/run/current-system/profile/bin/guix", which is a link to a store item.
<civodul>you have to use --no-substitutes to work around the bug until you've successfully reconfigured
<necrophcodr>rekado, it didn't work to use the existing one, but rebuilding it from scratch was surprisingly easy to do, so i'll keep a profile.scm file along with me instead, it seems to be a lot more useful anyway. thanks again!