IRC channel logs
2025-04-19.log
back to list of logs
<PotentialUser-89>I keep getting 502 errors, both from guix pull and from trying to manually visit the cgit interface in my browser <nomike>I found some time to continue working on prusa-slicer@2.9.2 again, but I've run into an issue and I have zero experience with CMake so far so I don't really have a clue how to tackle this. <anemofilia>The expat input shouldn't specify the output static? <nomike>anemofilia, thanks. So that I understand it right: the expat package has two outputs '("out" "static") and when I use `(,expat "static") instead of simply expat in the inputs list, I'm getting the "static" output. Right? <nomike>Unfortunately I'm still getting the same error. <nomike>Yes, exactly the same. Bit by bit. <nomike>The weird part is, that in the package definition of prusa-slicer@2.7.4 which I used as a starting point, the input also just has a plain "expat" in it. And the corresponding section in PursaSlicer's CMakeLists.txt hasn't changed between 2.7.4 and 2.9.2. <nomike>If it helps I can commit the changes I did so far to a branch and upload it to github. <old>I'm wondering, If I have a Guile project that is using guix through #:use-module, can this project be LGPL or it can only be GPL because Guix is GPL? <cow_2001>styling the original up in org-mode format for an info manual output <cow_2001>wait a minute, peanuts sees srfi-n and gets the srfi-n/srfi-n.html page <nomike>`guix lint` tells me "parentheses feel lonely, move to the previous or next line". So I do as I'm told, remove the newline and attach them to the previous line of code. Then I run `guix style`. which moves them down again. ermm... I'll let `guix style` win this time, but that's still strange. <ieure>nomike, Yeah, those two tools don't agree. <anthony_325>I tried a vanilla guix (1.4) installation this morning, and it failed at the internet connection stage. Also, I can't reach guix.gnu.org from my debian machines. Are servers down I wonder? Or something on my end perhaps? <ieure>anthony_325, Do you have a network adapter with Free drivers? Most require blobs, thus, don't work with Guix. <anthony_325>I don't think that was the issue, as I connected with an Ethernet cable to my router, rather than using wifi. It also seemed to succeed with initial network configuration (I don't recall the exact message). It is also strange that I can't reach guix.gnu.org, as I can usually reach it from debian machines. <ieure>anthony_325, Yeah, hmm. I can reach guix.gnu.org right now. I don't think the installer accesses that for anything. It needs the Git repo and substitute servers, none of those are on guix.gnu.org. <anthony_325>Okay, thanks for checking. It looks like I should double-check my motherboard's Ethernet, and check up with my ISP with a traceroute (or some such) about the inability to access guix.gnu.org. Thanks for checking that for me. <lilyp>old: it should be GPL. That's the main reason why Guile itself is LGPL. <hanker>Is there a package that contains most licenses files, for reference? <ruther>hanker: I don't think so, but there are links to the licenses in (guix licenses) module. <jA_cOp>I think since an update, elogind doesn't respect my configuration anymore. Lid close suspends, and the power button shuts down, despite the configuration file having everything set to 'ignore. Anyone else experienced this? <bdju>Is there info anywhere on how to set up xdg-desktop-portal-wlr with Sway on Guix System? Do I need anything in my config.scm or do I just install the package? <ruther>bdju: install both xdg-desktop-portal and xdg-desktop-portal-wlr in the same profile. Other than that it is same as on other distros, so there is no need for a guide on Guix System. <ruther>Of course after doing that you also need to relog like with any new env vars added to the profile <bdju>I've never done it on any distro before anyway. <bdju>I've still never even gotten pipewire to work on Guix System since all the docs talk about Guix Home, which I'm not using, so maybe it's pointless anyway. <ruther>It is not different... It's like saying oh because someone says bash is at /bin/bash, I can't do it the same way on guix system... <ruther>Of course that on Guix System packages are installed under the respective profile and not to root of FS... <bdju>Well, if I need some path with a hash in it that will change on an update, that doesn't seem fit to go in my Sway config, is what I was thinking. <ruther>First of all you don't need any path in sway, you don't start desktop portal yourself, dbus starts it <ruther>second, even if you did, you would put the profile path in there - ~/.guix-profile/libexec/xdg-desktop-portal. <jA_cOp>yeah, don't start xdg-desktop-portal yourself, let your user dbus session start it on demand. But depending on how you start dbus and sway, xdg-desktop-portal may not end up with the required environment variables <ruther>The only time you would start it manually is for debugging purposes when you're setting it up <jA_cOp>on Arch Linux, this is solved by having etc/sway/config.d/50-systemd-user.conf, which can be included from your Sway config with `include`. On Guix, you may want to just include the equivalent configuration directly in your sway config <jA_cOp>In my config, I have `exec dbus-update-activation-environment WAYLAND_DISPLAY`, while XDG_CURRENT_DESKTOP is set in my guix home config, so dbus already has it <bdju>Thank you both for the info. I don't want to restart my Sway session at the moment, but I'll make some of these changes in preparation for next time I do. <ruther>You don't need to restart your sway session to start using xdg desktop portal <adanska>hi, trying to write a package definition, how do you reference a prior version of a package? for instance, im trying to reference the `fmt@10.2.1` package. <adanska>found it out. just referenced `fmt-10`. <apteryx>I wonder what happens when two shepherd service instances log to the same file? <meaty>HEAD of rust-team has been on a 'squash!' commit for 5 days, is it ok to base a patch off that commit? <hako>meaty: What have you changed? <meaty>hako: I did a git pull and rebase and only realized after that my local branches got rebased onto 1959cffa14afbb8594cd8ab2db3b2d7ca9a0c8f6 which is apparently due for squashing <meaty>if I send those branches upstream as patches will they have issues? <hako>depending on which files you have changed <hako>but the conflict can be resolved, so feel free to send patches <ayys`>Hi, anyone know how I can install emacs 31 on guix? Guix seems to only have v29 (or atleast, that's the only one I could find). <ayys`>Do I perhaps need to build it from a manifest? <ayys`>ops I was using the wrong account. sorry. <divya>Hello, can one install a Guix System from another host GNU/Linux distribution? <ruther>divya: as long as you don't want to replace that one, yes, and quite simply. Mostly like if you installed it via live iso manually. <divya>ruther: The plan is to replace it. <ruther>divya: that is much harder then and I would rather recommend using live iso. But you can still try and see what problems you end up with during the regular guix system init steps. They will probably have a solution, albeit possibly not an easy one. <divya>ruther: A friend is trying to install guix but for some reason the guix installer simply doesn't boot. <divya>Would trying the latest rather than the stable installer work? <ruther>divya: It's hard to say without knowing what the cause is. Possibly it would. kfirst I would try adding the nomodeset kernel parameter in grub though <divya>ruther: I understand, the system is quite a new CPU so that could be a possible issue. <ruther>divya: maybe the easiest option in your case would be to boot live iso of different distribution, and install guix inside of it <divya>ruther: We'll probably have to do that <ruther>divya: but note that unless you figure out what the actual cause is, you cannot be sure the system will actually be working, and not have the same issue. <ruther>s/the system/the installed systm <kby>Hello, is there an issue with the guix.savannah channel right now? I have been getting 502s the last few days. I can view the savannah.gnu.org page just fine over the browser. <kby>Okay... 502 is Bad Gateway, that can't be some misconfiguration on my side, no? <kby>Now it went through, odd <ayys>I just sent a patch 10 minutes ago to add `guile-slugify` library to guix via guix-patches@gnu.org. The email went through, but I cannot see my patch reported on https://issues.guix.gnu.org/. This is my first time sending git patches, so maybe I did something wrong? Should I resend the patch? I'd be very grateful if someone could help debug this issue with me! <ayys>I ran this command to send the patch: `git send-email -1 -a --base=auto --to=guix-patches@gnu.org'. Pretty straight forward, but maybe I did something wrong? I was CCed and received the email so it was definitely sent. <ieure>ayys, The patch system is complicated, your email goes to a list which feeds into debbugs, which mumi (which runs issues.guix.gnu.org) fetches from. <PotentialUser-84>My first time to build a package. Can some one help me? It can't access the network. If I put it in config.scm and reconfigure, the result is the same. <ruther>PotentialUser-84: right, you can't access network during build time, you need to make all dependencies available without network access inside of the build itself <PotentialUser-84>I don't understand. How to do that? Define every native-input in the .scm file? <ruther>PotentialUser-84: something like that. See examples for go in the guix repo, ie. (gnu packages golang-xyz) <futurile>PotentialUser-84: use the golang importer: see the guix import command - this will help a lot <ruther>I would scratch that makefile approach here. The makefile is just not made for Guix compilation way. It does multiple ways that do access the internet <ruther>PotentialUser-84: probably switch to go-build-system and first you can just try and hope, maybe it will just work... if not, you might need to understand what the makefile is doing and make new build phases that will do the same things <ruther>(of course you still need to put the deps in native-inputs as was discussed) <ruther>PotentialUser-84: and to get the proper inputs definitely do utilize the guix import go importer <ruther>there is no reason to do it all manually <PotentialUser-84>how to import go? `guix import go go` and `guix import gnu go` didn't work. sorry, im a beginner <ruther>PotentialUser-84: I don't understand what you're trying to do. If you want to import the package you're trying to package, you would do `guix import go github.com/daeuniverse/dae --recursive` <PotentialUser-84>thanks. I used `guix import go dae` and it failed, so i never tried it again. i thought it must be put some go's package repository to be able to be imported. Now does that mean i can import any github repo? <ruther>PotentialUser-84: yes, you can import from any git https repo with the go importer <PotentialUser-84>How about this one. It uses Typescript. And i didn't see the corresponding importer. <PotentialUser-84>After `guix import`, i was unable to build it. What's the typical reason for this type of error? <ruther>PotentialUser-84: you haven't imported(used) module that has that variable. <ruther>PotentialUser-84: grepping the source is the easiest way probably <ieure>PotentialUser-84, Did you pass the --recursive flag to `guix import'? <ruther>PotentialUser-84: though this one is not in Guix... Are you sure you did recursive import? <PotentialUser-84>I did use --recursive. the file is very long. i'm adding modules by looking at the errors <PotentialUser-84>I think i found the reason. `guix import` isn't consistent in defining and using. <PotentialUser-84>I continued to find the same pattern of bug: XXX (defined) and XXX-v3 (called). <gcarlos>Hi guix! I was wondering why does we have stadalone mingw packages instead of having those only as dependencies of cross-gcc-...-mingw-toolchain packages. As I understand, mingw provides a set of libraries and it's like a libc for the target architecture, but I cannot find a use case where I would like those non-native libs installed except when I would be cross-compiling something. As I see, there <gcarlos>is some architectures, like avr, that doesn't provide a standalone libc package, as it would be useless without the cross-compiler. Could someone point me out some use case for having mingw packages other than using them in cross-compiling with cross-gcc-...-toolchain? <RavenJoad>I've already gotten some feedback about 77448 for changing the (assoc-ref inputs ...) with #$(this-package-inputs ...) and changed as many as I could. Is there any other feedback I could get?