IRC channel logs

2024-08-09.log

back to list of logs

<ieure>Rutherther, You need to use gexps.
<Rutherther>really? I thought they were unnecessary inside of package derivations
<ieure>I'm not sure that's what you're dealing with here. The lambdas in your build phases get evaluated by the build daemon, so they don't have access to the things in scope when they're defined -- that's (one of) the problems gexps solve.
<Rutherther>hm, I thought regular unquoting is for that, not gexps "unquoting"
<Rutherther>though I've tried just replacing the wrap-paths with "(list ffmpeg pandoc ...)", and also got unbound variable. I thought I tried that before and it was fine. From that I see why a gexps is needed here
<ieure>Rutherther, Pretty sure (list ffmpeg pandoc ...) has the same problem, the `ffmpeg' and `pandoc' symbols aren't in scope when the lambda is evaluated by the build daemon.
<Rutherther>ieure: okay, I will have to figure out how to put gexpression here. But I am also thinking that it might be much easier to just take native-inputs as argument and filter out the ones I don't want
<freedomforge>finally got my wifi dongle, no I can try Guix out for awhile. Does it let you install wayland or sway during the inital installation?
<jaft_r>freedomforge: last I remember, (outside of Gnome) it didn't. I'm not sure if anything's changed, since then.
<freedomforge>jaft_r: okay, dang seems Devices not supported by free software were found on my laptop [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] so does this mean I can't use this graphics card either?
<jaft_r>freedomforge: Do you know the full details of the graphics card (such as which series it is, etc.)?
<freedomforge>jaft_r: yes, AMD A9-9425 Radeon R5 2 cores
<chubbymomo>I'm pretty surprised that nobody has asked this yet but now that NVIDIA is stepping fully into open-source kernel modules (https://developer.nvidia.com/blog/nvidia-transitions-fully-towards-open-source-gpu-kernel-modules/), will there be comparable support for NVIDIA drivers as we have for AMD?
<chubbymomo>Malformed the link: https://developer.nvidia.com/blog/nvidia-transitions-fully-towards-open-source-gpu-kernel-modules/
<jaft_r>freedomforge: I'm having a hard time telling; annoyingly, https://h-node.org/videocards/catalogue/en/1/1/undef/undef/undef/undef/video-card-works/undef doesn't seem to have your card for me to check, for sure.
<jaft_r>I'm assuming you got the message from seeing it on your screen. Are things rendering alright on your screen, in spite of the message?
<freedomforge>jaft_r: yes, things are rendering perfectly within the installer
<jaft_r>freedomforge: Then you /may/ be fine? I forget if Guix does a pull, first, before the install or not but, if it doesn't, it's likely going to be dealing with an older version of the kernel. So it's also possible that any issues you might encounter, graphically, will go away once you install the latest kernel version. But, you know, I can't say for certain.
<freedomforge>last question for the day, does this Tor anonymous network router service,used everytime you use the network or only when I wish to use it?
<freedomforge>jaft_r: thanks for your input, I think I better just put guix on this laptop(thinkpad x200) and run trisquel on the other one.
<pabs3>chubbymomo: the official NVIDIA GPU drivers will still have proprietary signed loaded firmware and proprietary userspace libraries. due to the signing, even the libre reimplementations of the userspace libraries will have to use proprietary firmware
<cnx>hello guix, may i have some eyes over https://issues.guix.gnu.org/72396 (add zydis library for x86* binary processing)
<mekeor>has anyone had luck with flashing qmk on guix system onto a rp2040-compatible controller?
<Rutherther>ieure: thanks for the tip with gexps, it worked after I managed to get my head around how the quoting! here is a result if someone was interested https://termbin.com/pzsl
<Rutherther>, maybe I will contribute it to guix at some point
<admmq>Hi everyone! Is it ok to ask for my patch review here? Or would it be better to wait?
<pranavats>admmq: Would you like to ask something about the patch you've already mailed? Or would you like to request a code review here?
<admmq>pranavats: I thought about asking for a code review of the patch I sent
<pranavats>I see. I'm not sure either. Personally, I'd use IRC for pointed questions/answers and advice about something particular, and email for long form/open ended (coherent) reviews.
<admmq>sounds right, I will wait then. Thanks
<mekeor>some people do ask for patch-reviews here in this irc channel. personally, i have the impression that guix maintainers are on vacations during the ongoing summer :D
<mekeor>oh cool, go-team branch has been merged! yayyy
<Rutherther>I've tried "guix system container" on a foreign distro. It seems to work somehow. Though there is one thing, it seems the environment is inherited from my system. My PATH is wrong, instead of being set to stuff like /run/current-system/profile/bin, it's still on the original value. How do I ensure I get the correct one? should I just source /etc/profile upon entering the container?
<spanko>Is there a way to specify `--allow-discards` on a guix dm-crypt partition ?
<chubbymomo>pabs3 I see... I'm not familiar with the entire ecosystem but what do you think is the likelihood of the userspace becoming open-source? Furthermore, is AMD's userspace open-source?
<chubbymomo>I never thought I'd see a time where NVIDIA would open-source just about anything, honestly.
<pabs3>unlikely, but there is already nouveau/nvk for open userspace
<pabs3>I'm fairly sure AMD userspace is, not sure about their firmware though
<chubbymomo>Will the open kernel modules make newer NVIDIA cards actually usable on Guix? I have an NVIDIA 2080 ti (Wish I had gotten something a little more respectful of open-source).
<chubbymomo>Also, do you know if they also have an open form of CUDA for applications that use it (AI and such)?
<chubbymomo>Sorry if it seems like I'm using you like a search engine... There's a certain threshold of knowledge to properly look into something and I'm most certainly not there. I didn't even put the dots together on the userspace being open-source from nouveau.
<pabs3>not sure since you'll need the proprietary signed firmware blobs and nouveau/nvk might not yet support that card
<pabs3>(I read that some of the former proprietary kernel module likely moved into the firmware)
<pabs3>re CUDA, no, that is pretty much their main moat against AMD
<chubbymomo>Fantastic, so they just wanted to earn some surface-level brownie points and not actually achieve anything reasonable...
<chubbymomo>Fair point on CUDA... Time for this poor college student to get himself a reasonable AMD graphics card, then. Lol
<pabs3>pretty much, and also avoid the pain of maintaining their kernel driver with constantly changing interfaces and making interfaces GPL-only
<pabs3>btw AMD are working on supporting CUDA too in different ways, nothing easy though
<chubbymomo>Final comment before it gets too off-track for this chat: Reminds me of how glsl (Shader language) is completely closed-source. Absolutely no creativity to be had with that.
<chubbymomo>Huh, that sounds odd. I guess ROCM is just not doing well enough?
<pabs3>their CUDA stuff is built on top of ROCm, but everyone probably doesn't want to port CUDA stuff over to a different language and then make their codebase CUDA incompatible
<freakingpenguin>Can a Guix package use Guix in part of its build process? e.g. shell commands in test scripts?
<lechner>freakingpenguin / Hi, what's your use case? And thanks for those two blog posts!
<lechner>Hi, how may I run './pre-inst-env guix reconfigure' as root from a user account, please?
<lechner>pabs3 / hi, what are you doing here?
<mirai>lechner: iirc, sudo -E …
<triangle-man>(New to irc, guix, qemu.) I am running Ubuntu under QEMU on Aarch64 and attempting to run Guix under QEMU. The command `guix system image --image-type=qcow2 --image-size=128G config.scm` produces the error: "guix system: error: EFI bootloader required with GPT partitioning".
<triangle-man>But ... my config.scm reads "(bootloader (bootloader-configuration (bootloader grub-efi-bootloader) (targets '("/boot/efi")) (terminal-outputs '(console))))
<triangle-man>And so I thought I *had* specified an EFI bootloader.
<triangle-man>Can anyone point me in the direction of my error?
<weary-traveler>freakingpenguin: it could reference the guix package which slightly lags behind the version you get when you do guix pull. i have never tried it, however
<jaft_r>triangle-man: I'm not terribly familiar with any of this but perhaps the partitioning isn't GPT, rather than it not being an EFI bootloader. I know there's two types of partitioning often used (though I forget the name of the other type). What OS are you trying to run QEMU on (what's your installed OS)?
<Rutherther>how would I go about putting output of "computed-file" to a profile manifest? putting it directly to packages->manifest leads to wrong type argument