IRC channel logs


back to list of logs

<civodul>rekado: thanks to the changes you made the closure of (gnu packages base) went from 304 to 297 modules
<civodul>not as much as we'd like, but it's a start :-)
<janneke>civodul: [how] would i parameterize patch-and-repack to not use xz (use gzip or no compression) for initial bootstrap packages?
<civodul>janneke: good question
<civodul>currently it's not possible, but you could add a parameter
<civodul>or maybe something like the <compressor> record in (guix scripts pack) though that's prolly overkill
*civodul -> zZz
<civodul>happy hacking & sleep well! :-)
<ArneBab>this is me from my new Guix system.
<ArneBab>Is there a simple quick-start tutorial for "I miss this package, it uses autotools, how can I add it"?
<ArneBab>for homeoffice i need openfortivpn
<ArneBab>… and I see the time, it is time to sleep, see you in ~18h …
<ArneBab>I should have a backlog, if I don’t get kicked. If I’m not here, give sneek a botsnack :-)
<ArneBab>sneek: botsnack
<bavier`>anyone else use binfmt-misc to check builds for non-native systems?
<bavier`>I'm seeing one of libgc's tests hang with '--system=aarch64-linux'
<adfeno>Hi there :D
<adfeno>I'm trying to decide if I'll install QEMU or Virt-manager I'll go with QEMU from Guix :D
<pkill9>virt-manager is a wrapper for qemu isn't it?
<pkill9>to give you a GUI interface for managing qemu virtula machines?
<adfeno>But I found out that it seems to require more stuff than QEMU
<adfeno>also, requires a virt server running and that the user is member of libvirt group
<adfeno>That's fine, but I wounder if this could be simplified for more friendly use cases
<pepa65>Hi there, someone able to help me with a botched install?
<pepa65>Had an issue with a first install after many hours running, was wondering if I need to start from scratch or if what I am left with is salvagable/usable to arrive at an install
<bavier`>pepa65: did you make it through the install?
<pepa65>What I had after reboot was /etc/config.scm and close to 4GB of files in /tmp
<pepa65>Needless to say it didn't reboot
<pepa65>Because it made all these files in /tmp/guix-inst I was wondering if I could avoid building them all over again
<pepa65>Just restart the install on the current state, with some modified commands to get it to successful completing is my hope. :-)
<bavier`>pepa65: if your have files in /tmp, it's possible you might be able to just start the cow-store and rerun the 'system reconfigure'
<pepa65>So I can start cow-store and it will take whatever is already there?
<pepa65>I'll try that, thank you!
<bavier`>pepa65: I believe so yes; I've had to do the same in the past ;)
<pepa65>I'll let you know how it goes :-D
<bavier`>good luck
<pepa65>It's not mentioned in the guide, and I have specified it in the config.scm, but do I also need to mount /boot/efi ?
<pepa65>(I mean before starting)
<pepa65>I did mount /mnt/boot/efi just to be sure...
<pepa65>So instead of `guix system init /mnt/etc/config.scm /mnt`I replace the `init` with `reconfigure`, right?
<bavier`>pepa65: sorry, no, 'init' is correct in this case
<pepa65>OK, reconfigure had wrong number of arguments in any case
<pepa65>Output: building /gnu/store/(...)-module-import.drv building /gnu/store/(...)-Python-3.7.0.tar.xz.drv
<pepa65>Then: builder for '/gnu/store/(...)-Python-3.7.0.tar.xz.drv' failed to produce output path '/gnu/store/(...)-Python-3.7.0.tar.xz'
<pepa65>It says `view build log` but it's binary, I can
<pepa65>'t make sense of it...
<reepca>pepa65: it's most likely compressed
<bavier`>pepa65: the logs are bzip2 compressed; I think the install system has bzless available
<bavier`>pepa65: I'm guessing it's a network problem
<pepa65>Indeed, I had forgotten to initialize the network...
<pepa65>The log (bzless) said no connection
<pepa65>It's now downloading lots of stuff again. I get the impression that it's not using anything cached in /mnt/tmp/guix-inst
***ChanServ sets mode: +o lfam
<pepa65>It just started building
<leungbk>i'm having trouble setting up a decent environment for writing haskell on emacs + guixsd. when i used debian, i used stack and emacs' dante-mode, and everything worked fine; but on guixsd, i'm having a hard time getting even one of dante-mode/intero/ghc-mod to work. does anyone have any suggestions for editor integration?
<reepca>well, that was a good 5 days wasted. python-2.7-site-prefixes.patch hard-codes a /gnu/store, so if you try doing anything with python-2.7 in test-env, it breaks.
<reepca>leungbk: guix import elpa --archive=melpa -r dante will give you package definitions for dante and the packages it depends on. You can put it in a guile module and import the relevant stuff (like (guix) and (guix build-system emacs)) and add that module to your GUIX_PACKAGE_PATH. Then a guix package -i dante will install it.
<reepca>took one second too long
<reepca>sneek: later tell leungbk: guix import elpa --archive=melpa -r dante will give you package definitions for dante and the packages it depends on. You can put it in a guile module and import the relevant stuff (like (guix) and (guix build-system emacs)) and add that module to your GUIX_PACKAGE_PATH. Then a guix package -i dante will install it.
<reepca>oh there you are
<leungbk>ah, thank you @reepca and @sneek
<sneek>Welcome back leungbk, you have 1 message.
<sneek>leungbk, reepca says: guix import elpa --archive=melpa -r dante will give you package definitions for dante and the packages it depends on. You can put it in a guile module and import the relevant stuff (like (guix) and (guix build-system emacs)) and add that module to your GUIX_PACKAGE_PATH. Then a guix package -i dante will install it.
<pepa65>Install finished, /mnt now looks properly populated, including /boot/efi -- rebooting.
<bavier`>hope it works
<pepa65>Weird thing that I am now going to look into. Stuck at EFI boot manager, and the EFI partition has EFI/GuixSD but when I looked at /mnt before rebooting, it had a grub_x64.efi binary there, but that's not there now...
<pepa65>It says volume not properly unmounted. I was almost going to say here before rebooting, it feels wrong not to properly unmount everything...
<pepa65>OK, fsck done, efi binary is visible again, root fs also cleared from many orphaned nodes... :-('
<pepa65>After manually seeding the efi boot manager I reached GRUB and now it's booting!
<pepa65>bavier: Thank you for your help!
<bavier`>pepa65: glad you could get it working!
<bavier`>let us know if you you have any other questions
<pepa65>How can I properly reinstall grub? There is no update-grub :-)
<reepca>I don't know much about grub, but if you're booted up maybe you could just try a 'guix system reconfigure <your-config>'?
<pepa65>Us there no commandline git??
<reepca>have you installed git?
<pepa65>I searched for it, but only found cgit, git-daemon and gitolite
<bavier`>pepa65: guixsd doesn't have a whole lot until you install it
<pepa65>How can I install it?
<bavier`>pepa65: 'guix package -i git'
<reepca>pepa65: that's strange, how were you searching for it?
<pepa65>guix system search git
<pepa65>Obviously not the right thing...
<reepca>aye, you'll be wanting guix package -s for searching packages (including descriptions) or -A to just search names
<reepca>I didn't even know we had a guix system search
<pepa65>So is updating just `guix package -u` after `guix pull`?
<reepca>that'll update the packages in the current user's profile. If you want to update the system (kernel, services, etc), 'guix system reconfigure' does that.
<pepa65>OK! That's what I am doing in one tab, while installing git and tmux in the other -- not harmful I hope, doing it in parallel?
<reepca>thanks to guix's transactional properties, installing in parallel *should* never cause any breakage, but there is one annoying thing: 'guix package' stuff operates on the user's profile by looking at the current profile and generating a new one with the new/updated/etc stuff. It then builds the new profile, and finally symlinks your ~/.guix-profile to it atomically. This means if you do guix package -i foo and then switch to another
<reepca>terminal and run guix package -i bar, you will end up with either the new profile produced with foo or the one produced with bar, but not one containing both (since it wasn't told to produce one containing both).
<reepca>this can be annoying if you start installing something and then halfway through remember something else you wanted to install
<reepca>but since reconfiguring only affects the *system* profile and 'guix package' installs stuff into your *user* profile, it shouldn't cause any issues whatsoever
<reepca>Question... do we assume that if the store is in a non-/gnu/store place that NIX_STORE will have to be set by the user accordingly, even if they configured their install with the proper --storedir flag?
<pepa65>Very strange how the `/etc/fstab` file contains a great many entries, but none about the swap, EFI and root partition (the former 2 were not mounted then...)
<pepa65>I guess you have to manually add them, even at the install stage..?
<pepa65>No wonder grub does not boot
<efraim>my /etc/fstab has UUID=F010-1913 /boot/efi vfat defaults
<roptat>pepa65, you're supposed to declare these fs in your config, then fstab is filled automatically from that. But I don't think grub needs that. Can you share your config so we can try and help you?
<pepa65>I am using the desktop template. In the bootloader part I didn't change anything, it already had grub-efi-bootloader and "/boot/efi" as target.
***rekado_ is now known as rekado
<rekado>reepca: no, NIX_STORE does not need to be set. But Guix should have been configured with the different store location.
<rekado>ArneBab: here’s a packaging tutorial:
<reepca>does that mean that if I want to do testing I should configure with the store location being test-tmp/store?
<pepa65>Funny, grub seems configured correctly, but I can
<pepa65>'t find a single grub-command...
<rekado>reepca: hmm, no. NIX_STORE is used by the test, after all.
<rekado>reepca: but if someone wanted to install to a different store location that hardcoded /gnu/store would bite them
<rekado>and we don’t expect them to set NIX_STORE.
<rekado>(it’s not mentioned in the manual AFAIK)
<reepca>ah, so a different solution than the patch I sent should probably be used
<rekado>pepa65: grub is configured exclusively through the operating-system configuration.
<pepa65>I try to install efibootmgr by `guix package -i efibootmgr` and then afterwards, it doesn't seem to be installed, in spite of all the downloading and activity
<rekado>pepa65: efibootmgr installs files to $profile/sbin and $profile/share
<pepa65>Oh, I guess you have to do the recommended exports after every install?
<rekado>make sure that you’re not just looking in bin.
<rekado>what do you mean by ‘recommended exports’?
<rekado>with GuixSD your default profile will always be ‘activated’ automatically.
<pepa65>Do you have to make a list of all the recommended exports after every install, or is that just for the current shell?
<rekado>(you can do ‘source $profile/etc/profile’ when using bash)
<rekado>GuixSD sources $GUIX_PROFILE/etc/profile for you automatically.
<pepa65>After doing `guix package -i ...` it often concludes with something like `The following environment variable definitions may be needed`
<rekado>right, but they are all recorded in ‘etc/profile’ as well. If you’re using bash you can simply source that file.
<rekado>but on GuixSD the defaults are such that it is sourced automatically.
<pepa65>OK, so any new login shell should be good
<reepca>'bash -l' is my lazy way of getting new environment variables
<rekado>on GuixSD GUIX_PROFILE is also set, so you shouldn’t have to even get a new shell.
<reepca>Although I suppose I could do a "tail call" of sorts and do 'exec bash -l' instead...
<rekado>all the vars should be relative to your default Guix profile anyway.
<rekado>so there’s no point in exporting them again.
<rekado>I suppose in this case it may be because previously you had nothing in sbin, so it wasn’t part of your PATH.
<reepca>seems GUIX_PROFILE is set but never exported, at least on my GuixSD system.
<g_bor>hello guix!
<g_bor>I got a Mailer Daemon message for, not found.
<pepa65>Thanks for all the teaching & tips!
<civodul>Hello Guix!
<pepa65>Installed grub-efi, did a grub-install, and now I have to enable cryptodisk in a file that doesn't even exist..?!
<pepa65>On a read-only filesystem as well...
<pepa65>I must be doing something very wrong
<reepca>pepa65: could you post your config?
<reepca>oh sorry I didn't see the part where you discussed it already
<reepca>disregard that
<pepa65>It is basically the desktop template. Somehow I can't easily copy it from the VM except for typing it out manually
<pepa65>I think it
<pepa65>'s just my misunderstanding of GuixSD
<pepa65>Maybe I can find a way to paste it to some site
<g_bor>pepa65: one easy way around that is to enable ssh, connect trough a terminal from the host, and copy/paste from there.
<g_bor>usually in concert of lauching the vm with a portforward, or with some other netwoking that allows you to use servers on the guest.
<pepa65>Here it is:
<roptat>hi guix!
<roptat>pepa65, I'm a bit confused after reading the backlog. Do you still need help, or did you solve your problems?
<roptat>pepa65, I think you will need a filesystem declaration for your EFI partition
<pepa65>The emergency is over, things are running, and I'll try a reboot (probably won't work, but I can start it manually)
<pepa65>I just thought it is supposed to work, why isn't it?
<roptat>see the last example of
<roptat>there's a filesystem declaration for the EFI partition that you don't have
<pepa65>Every time I do a `guix system reconfigure /etc/config.scm` it takes hours, but I'll try now if it fixed the boot issue
<roptat>what's wrong exactly?
<pepa65>What is the recommended way to shut down?
<pepa65>(Or reboot?)
<roptat>there are the reboot and the halt commands
<pepa65>When I did reboot after the install there was lots of fs corruption
<roptat>if you're in the installation environment, there are more steps in the manual
<pepa65>This is what I was following:
<roptat>yeah, that should work
<pepa65>Grub is now working..!
<roptat>mh... did you mount the efi partition to /boot/efi as well as /mnt/boot/efi?
<roptat>ah nice!
<pepa65>only to /mnt/boot/efi
<pepa65>(Well, I didn't at first)
<roptat>so does it work now?
<pepa65>Sorry, it feels a bit I am just spouting, but you've all been very patient. It seems GuixSD is really different from anything I have tried before
<pepa65>Yep, booted straight through to the GUI loging
<roptat>it's very confusing, I agree, but once you get used to it, it's really great!
<roptat>congrats :D
<pepa65>It seems the main thing I initially did wrong was to not mount the EFI partition
<roptat>ah I see, there's no explicit instruction to mount it
<pepa65>So is it normal for it to always take very long after `guix system reconfigure /etc/config.scm`?
<roptat>depending on the availability of substitutes and your configuration, it can take a lot of time, but usually it takes only a minute or two on my systems...
<rekado>pepa65: no. It depends on how much is to be built. If you didn’t change the version of Guix then reconfiguring shouldn’t take a long time.
<pepa65>I'll try it again
<pepa65>Doing a pull now
<pepa65>Is guix the only package manager that GNU ever made?
<civodul>pepa65: yes, though Stow and GSRC get close to it
<civodul>in cases there's interest: there's a free software funding even in Paris at the end of the month:
<civodul>i don't plan to participate, but you can spread the word to other free software projects!
<jlicht>hey guix
<civodul>the spinner after "Computing Guix derivation" behaves weirdly today
<civodul>like during 20 seconds it doesn't spin, and then it starts spinning
<civodul>and it doesn't seem to be a matter of buffering
<civodul>oh the spinning thread is actually stuck on the resolve-variable mutex, uh
<davidl>Does someone know how to start using guile-bash after having installed it? just running (use-modules (gnu bash)) in the guile REPL doesn't work. I found the /gnu/store path for the package but don't know how to add it the load path correctly.
<davidl>guile-bash seems to only have packages for guile-2.0 - does that mean I must install guile 2.0 instead of 2.2 in order for guile to find it in the default load-path?
<roptat>davidl, most likely yes. Then guix will tell you how to set up environment variables for guile-bash to work
<roptat>you have to install both in the same profile to get the hint
<davidl>roptat: ok thank you. I will try that.
<jonsger>civodul: maybe we could issue a statement which gets listed on
<civodul>jonsger: yeah, though it seems to be more about "big names" and sponsors
<davidl>roptat: thanks again - I finally got it working!
<bavier`>just playing around a bit, packaged two subgames for minetest
<bavier`>I think packaging mods would work similarly, though we might need to add another native-search-path for minetest
<g_bor>hello guix!
<bavier>hi g_bor
<g_bor>hello bavier!
<g_bor>a bug report just fell in regarding nss-cert having wrong hash on mirror hydra.
<g_bor>It is strange...
<roptat>how do you make a list that's a sequence of numbers in guile (from 2 to 21 in my case)?
<g_bor>srfi42 might be an overkill, but works :)
<bavier>roptat: (use-modules (srfi srfi-1))(iota 20 2)
<g_bor>bavier, roptat, yes, I've just found iota also :)
<g_bor>nice to know
<roptat>now I need that on the build side
<bavier>roptat: you can list srfi-1 as an imported module (see examples), or use guile's builtin 'iota' procedure: (map (lambda (n) (+ n 2)) (iota 20))
<roptat>ah sure, thanks :)
<bavier>map necessary because the builtin version always starts at 0
<civodul>bavier: our openmpi package is getting old, were you planning by any chance to upgrade it? :-)
<bavier>civodul: indeed, I hadn't seen the latest releases
<bavier>I can put it on my todo
<civodul>cool :-)
<davidl>roptat: re making a list 2 21: (use-modules (gnu bash)) (display (string-split #$(seq 2 21) \#newline))
<jlicht>I'm playing around with an nginx/php-fpm install on GuixSD atm, but am having trouble getting nginx to allow for leaving off the "/index.php" at the end of URL's. Is this possible using GuixSD services configurations, or do I need to dive into manual nginx-configurations?
<jlicht>nvm, I just needed to restart my nginx service. Everything works wonderfully :-)
<g_bor>It seems to me that I am hitting some kind of resource limit. I got a build where unzip returns 9.
<g_bor>It goes well when I run it in the kept build directory.
<g_bor>Any idea?
<g_bor>Maybe I should just close the temporary file ports...
<ArneBab>rekado: thank you!
<ArneBab>a strange thing I missed during installation: a suggestion for the partitioning scheme.
<ArneBab>(specifically: a suggested size for the efi filesystem, a suggestion whether I should have a boot filesystem)
<ArneBab>how can I change the default desktop at the login screen?
<ArneBab>(and where can I find answers to such questions myself?)
<davidl>ArneBab: I think I have seen example modification of the slim package in the mailing list.
<davidl>websearch for help-guix archives
<reepca>I know in slim you can press f1 to cycle through different window managers before logging in, haven't installed any desktop environments to try though.
<ArneBab>found it, I think:
<ArneBab>reepca: I’m doing that, but I want to change the default so that I don’t have to hit f1 by default
<reepca>ArneBab: ohhhhh, I misparsed your sentence as basically "how can I, at the login screen, change the default desktop". Makes sense now.
<reepca>it looks like 'auto-login-session' in slim-configuration might do what you want
<reepca>If true, this must be the name of the executable to start as the default session—e.g., ‘(file-append windowmaker
<reepca> "/bin/windowmaker")’.
<reepca>from the manual
<ArneBab>ah, found it, info -> guix system configuration
<mubarak>Hello Guix! :-)
<mubarak>amz3, o/
<mubarak>hey pkill9 :)
<mubarak>how are you?
<pkill9>I'm alright, how are you?
<mubarak>I'm good, thank you
<mubarak>does anybody here have an email, who use it Emacs or Mutt for mailing list? do I need to go to the settings and enable something?
<mubarak>I think I tried Icedove before but it didn't connect
<mubarak>I want to follow some mailing lists, and I don't want to use non-privacy respecting like @gma.. @hotma.. . If anyone have an email in any of emails recommended by the FSF, who able to configure it in Emacs or Mutt, please let me know
<bavier>mubarak: iirc, you need a premium subscription for IMAP access with openmailbox.
<apteryx>what is the entry point for network-manager-openvpn? I'm trying to set up a VPN.
<g_bor>ok, I've managed to find out what the problem was.
<g_bor>it is fun that unzip and zip status codes are completely different :)
<g_bor>good night!
<mubarak>bavier: thanks a lot for the info. have you tried any of FSF recommended emails, that have IMAP or POP3 for free
<bavier>mubarak: I have not
<mubarak>bavier: :) thank you, I'll try other FREE emails tomorrow and see if i can get one of its working in iirc
<ArneBab>my ntp does not work out of the box: time is wrong
<bavier>ArneBab: you may need to tell ntp that it can make a large adjustment
<ArneBab>ntpdate says 9 Jan 04:11:59 ntpdate[23734]: no servers can be used, exiting
<ArneBab>I just use %desktop-services plus (gnome-service) and (console-keymap-service "de")
<ArneBab>bavier: do I have to set ntp servers myself?
<bavier>ArneBab: you shouldn't need your own server, no; I'm not sure what's going on in this case
<ArneBab>bavier: when i try to configure services, I get the error that the service is duplicated
<ArneBab>am I getting some concept wrong?
<bavier>ArneBab: are you using 'modify-services'
<ArneBab>I did not know that it exists
<ArneBab>ah, found it — thank you!
<ArneBab>bavier: can I use a local repository as package channel?
<ArneBab>additional channel
<bavier>ArneBab: I believe so, but I haven't tried it myself
<ArneBab>I get errors when I try — using ME@localhost authorization failed (which ssh key does guix use?) and using a local path it … it actually just complains that I have no master branch
<davidl>mubarak: a friend of mine used openmailbox before but has now switched to, which cost $1/1euro per month. I can recommend it on their behalf.
<ArneBab>bavier: I just had to add a first commit and now it works with an absolute path to the repo — sorry for the noise.
<ArneBab>bavier: and thank you for your support!
<bavier>ArneBab: np, glad things are up and working
<ArneBab>not yet completely, but I’m moving forward :-)
<serichsen>good evening
<lfam>Hello serichsen
<serichsen>I'm looking for help. I'm trying to install GuixSD on a new laptop. When doing the `guix system init' step, stumwm fails to install. The build log shows that a dependency of the testing library cannot be found. I installed it on the installation system using `guix package -i …', but that changes nothing even though the file now definitely exists.
<lfam>My recommendation is to 'init' a more basic system, without stumpwm, or with some other window manager. It's not efficient to try debugging package build failures before installing the OS
<lfam>There is an open bug report about the stumpwm build failure: <>
<serichsen>Heh, that would have been my next question, thanks.
<pkill9>if the manual doesn't suggest using a barebones system config for `guix system init` i think it should, because it seems to solve a lot of issues and everyone who comes here with an issue just gets directed to do that anyway
<pkill9>the downloaded guixsd image is quite out of date in terms of software anyway so people will need to update soon after installing anyway
<lfam>It's not that out-of-date, especially compared to other distro installers
<lfam>But yes, people should update after installing
<serichsen>Hmmm. I'm down the bug report rabbit hole right now. It seems plausible that this is caused by, which looks like a more systematic problem.
<lfam>Yeah, that's an important bug for all SBCL software
<lfam>But it is a general issue in the sense that the reference scanner could be improved
<serichsen>Where do I find that reference scanner? I also read something about “grafting code”?
<serichsen>I am a bit surprised that it matters how SBCL stores strings internally.
<serichsen>If this is a guix api that is called by SBCL, it should be a simple matter of specifying the external-format.
<ngz>Hello. I have a question about the install script. It "makes guix command available to all users" by putting a link in /usr/local/bin. Isn't that process outdated, since each user can have their own guix command?
<lfam>serichsen: After building a package, Guix scans the result of the build for references to other files in /gnu/store. This information is used for several things, like knowing a package's runtime dependencies, so that they can be downloaded when installing the package. It is also used so that garbage collection of /gnu/store works properly. If the references are obscured somehow, for example by chunking them, or compressing the file that
<lfam>contains them, they will be missed the scanner
<bavier>ngz: the install script is for an initial system-wide install; afterwards each user is free to 'guix pull' their own guix.
<lfam>My understanding is that, currently, the scanner only reads ASCII, since file names in the store are ASCII and that's what most compilers use
<lfam>But, this issue with SBCL highlights the need for something more sophisticated
<bavier>this has been an issue too with gcc doing things with string alignment or vectorized loads of strings (iirc)
<apteryx>is anyone using a VPN with NetworkManager?
<ngz>bavier: I thought putting guix command in /usr/local/bin was discouraged. Nevermind then.
<lfam>serichsen: Check the code in 'nix/libstore/'
<lfam>And the grafting mechanism is in 'guix/build/graft.scm'
<serichsen>OK, so maybe one could (as a workaround) add some sort of guix manifest for the dependencies to the build output, in UTF-8?
<serichsen>thanks, lfam
<lfam>There's a difference between build-time dependencies and run-time dependencies. The build-time dependency graph is explicitly specified in the package definitions. But it's not the same as the graph of software needed at run-time. That can only be determined by something like a post-build reference scanner
<ArneBab>I run into crashes with guix package -i pv:
<apteryx>lfam: Aren't 'inputs' and 'propagated-inputs' essentially run-time dependencies?
<lfam>ArneBab: What does `guix describe` say?
<ArneBab>guix describe: error: failed to determine origin
<lfam>Hm... `guix version`?
<lfam>apteryx: One of them is the reality, the other is more like a prediction :)
<serichsen>It then seems that this is not the problem here, since the dependencies are explicitly noted: stumpwm has native-input fiasco, which in turn has input trivial-gray-streams, and the latter is not found.
<ArneBab>guix --version
<ArneBab>guix (GNU Guix) 0.16.0-8.7ba2b27
<apteryx>lfam: I don't understand
<lfam>ArneBab: Are you using any channels or GUIX_PACKAGE_PATH things?
<ArneBab>I tried to add channels, but removed them now
<ArneBab>my channels file only contains %default-channels
<apteryx>strange: I've rebuilt my system multiple times today, on the same Guix revision, and everytime it goes of building something new and unexpected such as "tar", "bash" or "guile". any explanation?
<ArneBab>I now deleted the channels file, but that did not help: guix pull fails
<lfam>apteryx: I mean that the list of 'inputs' is merely a prediction of what we think the software depends on. But, the actual store references in the built software are concretely the actual dependencies. Of course, this breaks down if the reference scanner can't read the references for some reason
<lfam>And propagated-inputs are another complication
<apteryx>lfam: OK, I understand now. I wouldn't expect package A to have B as an input to suddenly refer to C in the store though, that'd be a bug.
<ArneBab>lfam: restarting my computer actually worked …
<ArneBab>sadly I don’t have the time to find out why
<ArneBab>need to get this working the next hour
<lfam>apteryx: I disagree it's a bug. It's typical for transitive dependencies to become referenced after building
<lfam>Or, it doesn't happen "after building"
<apteryx>lfam: and in fact if we were using content addressed items, we wouldn't need to cache those references, or if only as a sanity check (since they'd be super cheap to find out given a specific Guix commit a package came from).
<lfam>But once the build is complete you see that they are referenced
<apteryx>lfam: OK, that's interesting, I've never scrutinized the binaries produced to see what sorts of thing they actually linked to
<lfam>Ah, I think you are hitting on something discussed in Dolstra's PhD thesis on Nix ideas. I forget the names he chose for these two models: The one used by Guix and Nix, and the one you seem to describe
<lfam>Extensional vs intensional
<lfam>It's possible I misremember, not sure. It's been a long while since I read it
<apteryx>yes, I should reread it too :-0
<lfam>FOSDEM book club
*apteryx will probably give a shot to the docker patches tonight
<cnmne>hello, I'm having trouble setting up a dual-boot situation
<apteryx>cnmne: that's something the manual doesn't really touch I'm afraid -- what does your config look like so far?
<cnmne>i've followed the Bootloader Configuration section of the manual pretty well and tried to setup the menu-entries field as they say
<cnmne>my system is up an running, but whenever I include the menu-entries I get a comically large scheme error output
<cnmne>the important part seems to be "In procedure map: Wrong type argument: ..."
*apteryx is reading on the Bootloader Configuration section
<cnmne>not sure if this matters, but I've only been doing a dry-run: `guix system reconfigure -n /etc/config.scm"
<apteryx>cnmne: for one you hae a typo in linux-argments -> linux-arguments
<bavier>cnmne: the bootloader-configuration 'menu-entries' field expects a list of menu-entries; do you have a list?
<cnmne>pretty new to lisp things (and lists are important!!) how do I make a list?
<apteryx>cnmne: could you show the full config
<bavier>cnmne: e.g. (menu-entries (list (menu-entry ...) (menu-entry ...)))
<cnmne>unfortunately it's in a vm and I'm copying everything over by hand
<cnmne>trying the list function now!
<apteryx>cnmne: I see :-/ no ssh?
<cnmne>that's an idea!
<cnmne>the dry run went through! and even the real thing compiled fine. grub listed everything as expected, but trying to boot from the non-guix dropped me into an emergency shell after not finding the device. I'll play with this a little bit...
<cnmne>thanks for that easy fix! I think I misunderstood the menu-entry objects to be the menu-entry arguments, and so didn't even consider an explicit list operation
<apteryx>cnmne: good to know!
<bavier>cnmne: great
<apteryx>is there a way to have a GuixSD service start as 'stopped' by default? I'm thinking about a VPN service I'd like to turn on only at times.