IRC channel logs
2024-04-28.log
back to list of logs
<freakingpenguin>Kolev: For those errors I find running guix repl <file> usually spits out something more precise. <wakyct>Kolev, is your load path including your module source directory? <Kolev>wakyct: Fixed GUILE_LOAD_PATH. It looks like it's trying to build. <Kolev>How long should "building /gnu/store/d4sgwln8w6fqk97fyvrkzm248v9a6hmc-guix-packages-base.drv..." take? <ajarara>as in, it breaks even if there are no actual substitutions <ajarara>unsure what entry point address actually means, and yes I want to build this (FOSS) binary from source but figuring out how to get node to work is not a weekend problem <ajarara>by 'break' I mean I get 'Exec format error' where before a subsitute run I get a different, more obvious error <KE0VVT>Is there a reason why tmux plugin manager will not run? <bienjensu>Having a slight problem with `guix gc`. I ran it for the first time in about a year (I know) and it was collecting around 250gb of trash. I used the duration flag. While removing /gnu/trash, after having apparently successfully collected, the process exited for some reason. Now running `guix gc` just reports "finding garbage collector roots..." and seems to hang? Planning to let it run overnight. <bienjensu>The guix daemon is running pretty hot, and there's occasional spikes of btrfs-endio-meta kworkers. <KE0VVT>Hi, Kolev here. Still no code for module. Is sudo messing with variables? <coyote>KE0VVT: did you try `guix system -L (path of module) reconfigure`? <coyote>maybe that'll tell us if sudo is messing with the environment or not, although i dont think that's the case <coyote>sometimes when a module has an error Guix (in my experience, at least) will simply bail out saying "no code for module" <KE0VVT>coyote: Aha! I was doing `GUIX_LOAD_PATH=$dir sudo guix time-machine`... <coyote>in that case it might help opening the REPL and trying to load it manually <coyote>KE0VVT: I'm not saying that's the cause of your error, just trying to check <coyote>also, that variable should be GUILE_LOAD_PATH. <KE0VVT>coyote: So you're saying, try loading the module in a REPL? <coyote>Yeah, that could tell you what's happening that Guix is not loading the module <coyote>`guix repl -L ...` and then do `(use-modules (...))` <coyote>you have to wrap it in parentheses: `(use-modules (chromebook alsa-lib))` <KE0VVT>coyote: scheme@(guix-user)> (use-modules (chromebook alsa-lib)) <coyote>hm, so there's nothing wrong with your module. ok <coyote>I'm assuming you haven't tried reconfiguring with the -L flag yet? <coyote>seems like there's no reason it shouldn't work with the directory in your load path <KE0VVT>coyote: I used -L $HOME/Projects/chromebook-guix <coyote>yeah, im not really sure what's going on then, sorry :-( <KE0VVT>What is modprobe? How do I change its settings? <KE0VVT>coyote: I haven't even done it the normal way. <coyote>well, each kernel module has an identifier where you can load it with the command `modprobe` while the system's running, or at boot with modprobe configuration files. probably the Arch Linux wiki page on it may help https://wiki.archlinux.org/title/Kernel_module :-) <KE0VVT>coyote: The files are supposed to be somewhere on the file system, but we all know what happened to the file system when Guix was designed. <KE0VVT>So I have to understand both Python and Scheme to get audio working... <coyote>would be much easier if the script linked in the page had a dry run option, heh X( <KE0VVT>coyote: Now I don't know which files I need for my computer. <wakyct>KE0VVT, if you want to hear audio, maybe just get a usb audio dongle. Then this is not such a blocker and you can work on it as you like. <KE0VVT>wakyct: I have my real computer that has audio, if I really need it. <wakyct>even better, you can just network your audio with pipewire ;) <KE0VVT>wakyct: I'm not opposed to PipeWire. I just don't know what I'm doing and got into something way over my head. <wakyct>well kudos to you for wanting to re/use hardware <trig_function>How do I obtain the wayland-scanner? I want to build a library statically but I get the following error: Failed to find wayland-scanner. <Altadil>Was there recently a change in the expected syntax for the os declaration ? <jonsger>ACTION got icedove@115 working. Sadly only the icedove-minimal package... <bdju> https://0x0.st/XHg6.txt krita build failure. might've already mentioned it some days ago but I just tried to update again and it still isn't fixed. I'll skip it for now. <bdju>qtbase failure too if I skip krita <apteryx>nathan_: thanks for the patch! I'll apply it shortly <apteryx>it's funny, I think I had a bad dream about that bug I introduced ;-) <apteryx>nutcase: look at (info '(guix-cookbook) Dynamic DNS mcron job') for an example <apteryx>you need the guile-gnutls extension, which is required by the (web client) module <apteryx>ieure: I applied your librewolf update; thank you! <cancername>dariqq: I'm trying to do that, but adding either (simple-service (simple-service 'name shepherd-root-service-type (shepherd-service ...))) or (service (simple-service (simple-service 'name shepherd-root-service-type (shepherd-service ...)))) fails with "wrong type argument". <dariqq>i think it should be a list. i.e (simple-service 'name shepherd-root-service-type (list your-service)) <cancername>thanks, that worked! tangentially related, but I've been meaning to ask: what's the difference between (list ...) and '(...)? <Kolev>Efraim: Oh, sorry. Have fun! <apteryx>Altadil: if you 'guix pull', it should be resolved <imadnyc>Hey, I'm trying a simple derivation where I'm building https://git.sr.ht/~rafael/gembro/commit/master, a simple go package. When I "guix-build -f gembro.scm", though, I get the error "%exception #<&invoke-error program: "go" arguments: ("install" "-v" "-x" "-ldflags=-s -w" "") exit-status: 1 term-signal: #f stop-signal: #f>". Can anyone help me troubleshoot? I don't know what this really means <Altadil>apteryx: Thanks, it indeed worked. :) <nathan_>imadnyc: you have to scroll up in the build log to see why the go command failed. i dont know go, but the go-build-system documentation at least says that you need to provide #:import-path in the `arguments' of the package. <imadnyc>Yea, I saw that, but I assumed that it would take some sort of default? I'm not familiar with Go either, but I was able to write this nix derivation here https://github.com/NixOS/nixpkgs/pull/301308 and assume Guix would be generally the same -- not sure what the paths are <nutcase>apteryx: Thank you, I already solved my issue. The problem was an empty $SSL_CERT_DIR env var <afm-victoria>ieure: yesterday I shared a pastebin with a Clojure class not found error. On a foreign distro, it goes away when I use your version of clojure-tools from bin-guix <afm-victoria>On a native guix system, I had to import the class from the main namespace in my program, which made it avaiable in the system. Upgrading to your version of clojure-tools was not sufficient. My guess is that on the foreign distro the class was loaded when I reverted to the Fedora-installed version of Clojure tools and was thereafter available.