<jmd>janneke: It is a service which doesn't (yet) exist in git.sv.gnu.org/guix.git
<ng0>I will release an update of gnurl today (just doing last fixes).. I think someone else should update the package in guix then because you either trust me that I checked my own gpg key or you want to be on the extra safe side that it is signed and good to go. otoh I would have no problem sending the update on the guix package. wdyt?
<jmd>Is there a deactivation-service-type? IE, something which runs when a service is disabled?
<taylan>if anyone else has 'guix pull' print stack traces, please let me know
<jmd>What does "make-kill-destructor" actually do?
<jmd>If it is an automake based configure, then there should be a rule called distcheck, unless it was explicitly disabled.
<ng0>argh. i updated it.. i checked for configure and even downloaded it again after i uploaded it. yet guix doesn't get the change oO can someone download gnurl 7.50.2 and tell me that the file is there now and I am not imagining things? https://gnunet.org/gnurl
<jmd>Seems to have a ./configure from where I stand.
<jmd>Yes. But I don't understand why you are talking about systemd .
<davexunit>ACTION finally has avr firmware compiling with avr-gcc
<davexunit>still some issues to work out with our avr-gcc package, things definitely don't "just work", but at least I can compile now
<dvc>jmd: I'm still running on nixos. So I have a systemd service that starts the guix daemon. I'm trying to use the guix daemon I compiled, but I think I'm missing some compile options, because doesn't it doesn't find guix substitute.
<jmd>... and ... as I have pointed out several times already, this is probably wrong, because (make-kill-destructor) does NOT run a kill-destructor. It simply returns a procedure, which when run, will do the necessary actions.
<jmd>Ipso facto adding a procedure directly after this call is probably not going to work. Am I wrong?
<alezost>jmd: it looks incomplete/broken, what's the code for your service
<davexunit>and there are docstrings for these procedures
<davexunit>so you can also inspect them at your repl without reading the source
<jmd>ERROR: In procedure module-lookup: Unbound variable: mount
<davexunit>you haven't imported the right module, then.
<jmd>I would be tempted to ask which is the right module to import, but I fear I would be told to read the manual and stop asking annoying questions.
<davexunit>a quick grep tells me that it's in (guix build syscalls)
<sajt_>wow, installing away.... btw. I really wish there would be something like paredit for zile
<alezost>dvc: I've just noticed that you changed syslog-service to make it accept syslog-configuration instead of keyword arguments. I probably missed a discussion, is it a convention now to use configurations in services?
<lostcoffee>I symlinked ~/.config/guix/latest to my clone of guix and now guix package -i can't connect to the daemon socket. Do I have to make changes to the daemon to get my own build of guix to work for my user?
<lfam>losfcoffee: When you built Guix from source, did you set a value for `./configure --localstatedir=???`?
<edangor>running the same command over and over to install the other packages
<lfam>dvc: Also personal bias against the mouse coming into play. But, the security issues happen to be a better excuse.
<lfam>edangor: I'm a little confused. Which command did you have to run repeatedly? And, can you share the operating system configuration file that you used, and also the exact error message you are seeing?
<lfam>You can share those files using paste.lisp.org
<lfam>I assume edangor's font doesn't show the difference :)
<alezost>edangor: sorry, but I'm afraid this error message doesn't tell anything useful
<lfam>edangor: I assume that your OS configuration specified the wrong device for the bootloader field, or that the partitioning was incorrect. It's very hard to say without seeing the configuration file
<lfam>If you can mount the storage of the computer in question from another computer, you should be able to extract the configuration file, assuming you followed the instruction that recommends to copy it to /etc
<lfam>If not, I would rewrite the configuration, keep a copy of the file, and try again
<sajt_>how could I run the xorg-start-command procedure from the shell?
<AppAraat>it's a "curl | bash" thing but in the script I found no daemon.
<lfam>In any case, the daemon is the only process that can write to /gnu/store. It runs as root because you need root privileges for things like chroot, which is used to set up the deterministic build environment
<alezost>sajt_: you can't use xorg-start-command in the shell, if you mean you installed X server to your global (system) profile, you can use /run/current-system/profile/bin/X
<dvc>just checked, it requires logind and I don't think our xorg-server is built with elogind
<lfam>Using Guix without the daemon will mean that your build environments are unpure, and if a build process even completes, the resulting binaries will almost certainly fail to run due to trying to link against libraries from the host distro and Guix at the same time
<AppAraat>lfam: in the use case of single-user Guix, would it be possible to create a store within a homedir and build all your stuff from source? Because the scenario you've mentioned must talk to the Guix build servers to make sure the hash strings coincide with Guix build environments, right?
<alezost>sajt_: you can specify paths to libs in /etc/X11/xorg.conf.d/
<dvc>alezost: is rainin knowledge on to us today :)
<alezost>sajt_: I think the best would be to install required X modules (xf86-input-evdev, xf86-video-XXX, etc.) globally, and to point modulepath to "/run/current-system/profile/lib/xorg/modules"
<AppAraat>lfam: ah, right, now I see it too. It invokes sudo. My bad :)
<lfam>AppAraat: As for putting the store in your homedir, I would search the archives our mailing lists guix-devel and help-guix. There has been some discussion of unusual setups like that, and you might find something useful
<AppAraat>hmm I see. I don't think it'll be a problem for me to install the daemon on my systems (I usually have root there anyway). I'm more interested in making my own definition files from which I can build things from source. In Nix it's called Nix expressions, how is it called in Guix?
<lfam>edangor: Okay, that should install GRUB on /dev/sda, assuming it exists. And, it also assumes that there is a disk device whose label is "root". You can set and check those labels with the `e2label` program
<edangor>lfam: i installed everything else 'cause i thought i could install openldap later, but grub did installed
<lfam>edangor: Well, it really sounds like GRUB was not installed, since you didn't see the completion message, and because the system is not working now
<edangor>lfam: so if i re-install the system, how do i make openldap's intallation complete?
<lfam>edangor: It depends on why it failed. I am trying to build it now to see if it works
<edangor>lfam: it said that some substitutes for the outputs of the derivation failed
<sajt_>alezost: I think I'm a bit confused, since I didn't use this package manager before
<sajt_>I'm getting the error unsupported manifest format
<lfam>edangor: Right, that's what I thought. Whatever operation failed, you should add '--fallback' to that command. The effect of that argument is to build from source if something goes wrong with the substitutes
<lfam>I wonder if you became disconnected from the internet
<lfam>If you did become disconnected from the internet, --fallback won't help because you won't be able to download the source code to build things yourself
<mark_weaver>dvc: I didn't read the whole log, but two things: pass --prefix=<PREFIX> to configure instead of setting the make variable, and to run guix-daemon uninstalled, prefix the command with /home/dvc/guix/pre-inst-env guix-daemon ...
<edangor>lfa: no, i din't 'cause re-running the command installed other derivations
<lfam>edangor: The GuixSD installation process is still somewhat brittle. Once GuixSD is installed, it's very solid, since you can always roll back to a previous generation of the system. But, getting that first generation built can be a little annoying the first time, especially if you are new to Guix
<lfam>To make the installation more likely to succeed, you can try starting with the 'bare-bones' configuration template. That will need to download and build less, so it will complete more quickly. Once that's installed, you could reconfigure to the desktop system you want. But I understand if that sounds like even more complexity you'd rather avoid right now
<edangor>uhm talking about my noobness, what command am i going to do the fallback?
<mark_weaver>sajt_: I didn't read the whole log yet, but I also run GuixSD on Libreboot machines. I recommend installing GRUB even though the only part of it that will be used is the grub.cfg
<edangor>lfam: ok, it says: error: wrong number of arguments for action 'init'
<mark_weaver>sajt_: the default menu item from Libreboot's grub.cfg should load the grub.cfg from Guix on the hard disk, which is probably what you want, because that will allow you to boot into older versions of the system in case the latest version is broken.
<lfam>edangor: Please show us the full comand when sharing errors
<snape>is it a requirements for packages to be able to run in a guix environment -C?
<sajt_>mark_weaver: thanks, I ended up with installing grub. the newer libreboot releases don't need reflashing btw. you can put a libreboot_grub.cfg in /boot/grub/ and the grub payload picks it up automatically
<lfam>snape: Not really, since that command would not provide network access, and some software requires the network
<mark_weaver>sajt_: every time you update your system with "guix system reconfigure", it will add new entries to /boot/grub/grub.cfg, so it's important to arrange to use that one without having to manually copy it somewhere else.
<lfam>I think that SSH is one of those things that users should install if they want it. Git can be used locally.
<sajt_>mark_weaver: did the same thing (the symlink), should have worked in the first place then
<alezost>sajt_: how did you get that manifest error? I meant you specify 'xf86-...' packages in your system config the same way you did for 'xorg-server' package and then do "guix system reconfigure", after that "/run/current-system/profile/lib/xorg/modules" should contain all installed modules
<lfam>Read `man su`. The default invocation of `su` is usually not what you want
<alezost>sajt_: when you run "guix package" you install packages in a user (root) profile which is ~/.guix-profile, while if you want to install packages globally, you need to add them to your system config file and run "guix system reconfigure"
<lfam>You might have to sell your sell to non-free software, but nothing's perfect :)
<lfam>Now, I just have to figure out how to do that for myself :)
<dvc>janneke: When I made the statement I meant it as a general rule and made no assumption over individual cases. The jobs that are popular among women make such general statements statistically correct.
<dvc>The only way to analyse or make statements about such behaviour is through statistics - that doesn't account for individuals. Also statistics don't make assumptions as to motivation - which I did admittedly
<lfam>BTW, janneke: what's the status of your mingw patches? Still waiting for review?
<janneke>lfam: review is done, waiting to be merged