<efraim>I think I uncovered another bug in guix at the same time, but it looks like the short version is zef in guix doesn't actually work
<efraim>so I got an interesting case where 'guix package -f perl6-package.scm -i rakudo', perl6 (from rakudo) fails to know about the perl6-package, but insert it into the guix source and 'guix package -i perl6-package rakudo' works without problems
<rekado_>g_bor[m]: hey, I wonder if you had some success with writing Guile bindings for that networking library.
<rekado_>g_bor[m]: I connected berlin to two 10G ports … and right now I can only use one of them, because we can’t do link aggregation or other forms of bonding.
<rekado_>I suppose we could run some network manager commands, but doing the network configuration without that intermediary would be sweet.
<numerobis>Hi #guix! I'm thinking of getting guixsd on a VPS. Is 2GB enough?
<numerobis>roptat: Oh, that's interesting. Is there a way to update only the packages for which substitutes are available? Or is it just that the Berlin servers are generally more up to date than the other ones?
<roelj>What do I need to get Guix to be able to verify a certificate when doing 'guix import cran ...'?
<rekado_>roelj: probably just nss-certs and the variables as specified in Application Setup
<roelj>rekado_: Ah, I was missing the environment variables. Thanks!
<rekado_>I’d like to offer rsync access to the nar/narinfo files on berlin. My plan is to create an unprivileged user account for SSH login, but restrict that account to just the directory containing the files.
<rekado_>do you know how a user account could be jailed?
<pkill9>wouldn't it be desirable to have each machine generate the system for itself, rather than generating it locally and then sending it to each machine?
<rekado_>in my case that wouldn’t be desirable; but I think that “guix deploy” also supports that.
<rekado_>for ci.guix.gnu.org, for example, it wouldn’t make sense. We have dozens of identical build nodes, none of which accept substitutes.
<rekado_>so building the system once (by offloading the work to all of the build nodes) and then pushing it to each of the nodes is much better than building the system without substitutes on each of the nodes repeatedly.
<efraim>i just broke master, searching the previous commits for a stray "name" tag
<xavierm02>I couldn't find any tutorial showing qt.conf accepting several paths. If it doesn't, would it make sense to use a package union of all the qt plugins, so that the path to this union can be added to the qt.conf?
<xavierm02>And more generally, when is it fine to use union packages?
<str1ngs>xavierm02: qt.conf and well qt in general work better when referring to a single prefix I found. for example locations of locales etc.
<str1ngs>xavierm02: in short I think a union would help the Qt packages. if not then some work on the current qt.conf inheritance would help
<str1ngs>xavierm02: or maybe a qt-build-system with help with qt.conf creation for modular qt packages.
<apteryx>rekado_: I think you misunderstood the error; it was trying to eval a string like ("ext4" fs) due to a variable name clash.
<rekado_>davexunit: have you tried setting GUIX_LD_WRAPPER_DISABLE_RPATH?
<rekado_>apteryx: yeah, I stopped reading at run-with-store… sorry
<rekado_>trying to apply something that’s in procedure position is a very common mistake, so I whipped out my default response.
<apteryx>rekado_: eh, that's pretty much where the error becomes unreadable, so I can understand ;-)
<davexunit>rekado_: no I didn't know about it. I will try it out!
<davexunit>if it can save me from building a custom gcc that is great
<apteryx>rekado_: the "In unknown file:" without any line information was the problematic part of it, mostly, followed by some cryptic expansion like: (_ #(#(#(#<directory (gnu system vm) 3c22820>) "disk-image" "x86_…" …) …))
<str1ngs>xavierm02: also from my example you may not want to install qt.conf. though for this package it was a hack to get qtwebengine to find locales. which is related to the union issue you describe earlier
<pkill9>rekado_: how could i use `guix deploy` such that the system is generated on the remote machine?
<rekado_>pkill9: I don’t know. “guix deploy” is currently under development, so it’s gaining features regularly. Don’t know if building on the target has already been added (or even if it’s planned at all).
<lispmacs>if I wanted to examine the bootstrap-binaries (like, to dissassemble them) how can I download them or figure out which binaries belong to that package? I tried guix build --source but that did not work of course
<lispmacs>or, maybe the question should be, where is the package definition stored?
<str1ngs>bootstrap-binaries is kinda subject. but maybe you mean gnu/packages/boostrap
<str1ngs>lispmacs: in which case they are in the guix source tree already.
<lispmacs>str1ngs: where is pulled version of guix source tree on my system?
<bgardner>Good morning guix, I'm trying to set up authentication against an LDAP server. I have a running server and a client with the nss-pam-ldapd package and an (nslcd-service-type) entry, but I know I need pam entries still - can anyone point me at an example configuration for that?
<str1ngs>for this it would be best clone the guix repo
<str1ngs>lispmacs though all of this is dependent on if these are the bootstrap binaries you are referring to
<rekado_>bgardner: I’ve got a configuration which … almost works.
<Adamclisi>Hi. I'm trying to install guix on my laptop but the installation stops with an error when installing the bootloader.
<bgardner>rekado_: I prototyped this out on a Debian box (so I could steal the config from there) but it includes a lot of Debian-specific plumbing that isn't present on guix, nor do we want it. Trying to do it the 'right way'. :P
<rekado_>bgardner: the nslcd-service-type provides the required PAM services; it extends the pam-root-service-type
<bandrami>Is there a package for the moby/docker CLI front-end? My guix package -s fu is failing me here.
<rekado_>bgardner: it ensures that for all pam entries “pam_ldap.so” is loaded and marked as “sufficient”.
<rekado_>bgardner: you will need to extend the name-service-switch field yourself, though, because that’s no system service.
<rekado_>bgardner: unfortunately, though, I haven’t been able to make this work; using “id”, for example, won’t look up the account in LDAP. Only if I set LD_LIBRARY_PATH to point to the pam_ldap.so location.
<rekado_>so I still can’t log on with LDAP accounts.
<rekado_>looks like something’s wrong, but I haven’t been able to find it.
<bgardner>rekado_: Oh boy, I might be too dumb to help, but I'll report if I find anything
<rekado_>I’m dumb, too, and I got that far. If we’re dumb together maybe we can crack it.
<bgardner>rekado_: First I need to factor out mdns, it conflicts with my network. Give me a bit and I'll get back to you
<dftxbs3e>I'm getting: "/gnu/store/vx06vchdp2lwlfd1k9rhxzpcph4km1ph-binutils-cross-boot0-2.31.1/bin/x86_64-guix-linux-gnu-ld: cannot find crt1.o: No such file or directory" on master when changing default gcc with gcc-6, any idea what that is about?
<dftxbs3e>I am running the command: guix build -M 2 --target=powerpc64le-linux-gnu bootstrap-tarballs --keep-failed
<dftxbs3e>and I found that error inside config.log for libmpx
<rekado_>dftxbs3e: this sounds like the error that we had to work around on the core-updates branch.
<dftxbs3e>hmm, should I use core-updates instead to change default version to 6?
<nixo_>hi, do you know why cross-compilation to armhf does not work? I get: while setting up the build environment: a `armhf-linux' is required to build `/gnu/store/f21dmq9kdxd097xq1vx6w7m90i3qrry4-arpack-ng-3.3.0.drv', but I am a `x86_64-linux'
<nixo_>or maybe I should pass --target instead of --system...