<maximed>And being allowed to ‘convey verbatim copies’ isn't suffcient, because 4 freedoms?
<dstolfa>i don't think there's any real issue in guix specifically as long as: (1) guix doesn't offer a substitute for zfs.ko; (2) guix doesn't modify any source; (3) guix only fetches a tarball and runs make. something that may make sense to do (as per your original suggestion) is warn users that they are in a legal grey area when it comes to redistributing zfs.ko, link to the article and maybe remind them of the 4
<maximed>(oops, I'm reading the GPLv3, Linux uses the GPLv2)
<geex3>openvpn-client service, to use openvpn.conf file, need to split out cert,ca,key into /etc/openvpn/client.key ? or can use /etc/openvpn/mything.conf
<dstolfa>there might be an issue in OpenZFS itself (e.g. they might have to explain how they build a linux kernel module without violating anything), but in guix we'd just kind of fetch a tarball and run make
<dstolfa>it's no different from having a GPLv3+ install recipe that fetches something like steam
<maximed>About (2): possibly guix itself is _legally_ in the clear, but I think we try to guarantee that all software in guix (not counting channels), respects the third freedom?
<mjw>muradm, civodul's valgrind trace is probably not related. It is somewhat embarassing code though. If now cwd is given then a null string is used for chdir, which fails, but the failure isn't checked... the code has a /* FIXME: Handle the return value */
<mjw>but NULL simply meant we didn't need to chdir
<mjw>what a frustrating bug. there is clearly some bad code, but none of it explains the issue
<roptat>muradm, well, your patch works for me, but maybe as you said, we should try with an older gcc?
<roptat>but it's weird we get a different result with my patch, shouldn't it be reproducible?
<muradm>roptat: i'm looking at jikes, jamvm and classpath-bootstrap, trying to build with some older gcc like from 2016 could be an option to try
*apteryx remembers fighting with this monster before
<iskarian>Maybe it had to do with the vendoring? (vague recollection)
<apteryx>yes, I think it vendors a massive amount of rust things
<apteryx>my new rust bootstrap only builds intermediates rusts at stage 1, which means they aren't usable. That's doesn't seem to be an issue for most software (can be built with latest rust happily) but not mozjs
<attila_lendvai>how do i get my trezor gpg agent working? i have installed for my user: trezord, trezor-agent, trezord-udev-rules (no restart). and i get: "Failed to enumerate WebUsbTransport. USBErrorAccess: LIBUSB_ERROR_ACCESS [-3]" any hints?
<civodul>mbakke: that getpw fails suggests the "file" NSS backend is not getting embedded
<civodul>i think there were changes in this area in glibc
*civodul builds icedtea 1.13 on core-updates-frozen \o/
<attila_lendvai>how do i tell guix to use my local guix.git checkout when running e.g. guix system reconfigure? after scanning the docs, i still don't know how to test my changes on my live system. i have set up my own channel, but that only helps with testing added packages. i want to test changes some to a service (tlp).
<cbaines>attila_lendvai, that's what the ./pre-inst-env script is for, you would run ./pre-inst-env guix system reconfigure ... for example
<nckx>I'm failing to SEO-keyword something so I'll ask here: does anyone happen to know if/how I tell NetworkManager to add an entry to /etc/hosts only when I'm connected to one specific Wi-Fi network? All I find is people complaining that NM modifies /etc/hosts. I want that, I just don't know how to harness it.
<nckx>It doesn't have to be /etc/hosts, it can be something fancier in dnsmasq. I just want the (public) foo.bar.baz name to resolve to a LAN IP on one specific network.
<ekaitz>they are, but they are treated differently
<abrenon>that were more or less uncompressed or something when the kernel started
<nckx>ekaitz: If you care enough about the name you could submit a patch to update the manual (I agree that it's misleading if you're not used to ignoring actual initrds as obsolete), but I don't think the name initrd should be changed in the code.
<nckx>abrenon: ‘At rest’, sure, but they are extracted very differently
<ekaitz>nckx: Honestly, i don't really care, but I was confused by it.
<nckx>abrenon: Initrd was an actual file system init (as in mke2fs img; mount -o loop img /mnt; cp stuff/ /mnt) that is 'loop mounted' in RAM, initramfs is a cpio archive (an older & simpler tar if you will) that is extracted & thrown away.
<abrenon>I think it'd be a good idea to fix the naming in the documentation, if only because I and roptat were confusing both types of objects
<lfam>Guix is categorically better than Docker in this regard, since Docker uses many things from the host system, whereas Guix *is* the host system
<zacchae[m]>ok, so I can specify a commit stirng for guix pull
<roptat>if it's to provide an artifact for a conference for instance, I usually have two instructions, one with virtualbox (not really reproducible) and one with guix: "guix time-machine <some-hash> -- guix build whatever"
<roptat>yes, you can find your current revision with "guix describe"
<zacchae[m]>maximed: That blog post is the right answer: i.e. any work I do should be wrapped up in a guix package
<zacchae[m]>but as a matter of practice, not everyone doing research is going to want to do that, so many might find it easier to make something work, then distribute a system config that they ran on
<muradm>roptat: did you push that commit regarding ant-boostrap/classpath-bootstrap thing? :)
<roptat>muradm, civodul pushed something different
<roptat>but because of a patch to jemalloc, I'm stuck building the rust bootstrap chain right now...
<iskarian>sneek, later tell atilla_lenvdai: regarding "the resulting binary gets a different ld loader, etc...": this is necessary because of how Guix works; without this, the binary would not use the libraries packaged by Guix, which defeats the purpose of Guix :p
<sneek>milkey, nckx says: <it needs gl.pc at build time> tells you only that mesa should be an input, which you already knew, not which flavour. Whether its dependents require mesa, for example because mesa's in Requires.private of (say) libbplacebo.pc, is the question. If yes, propagating mesa might be an appropriate hack.
<podiki[m]>from what I've read you can write directly to that (text file) with something like "detect". having some issue with some displays being detected (not specific to guix, had before on arch too)