IRC channel logs
2025-02-09.log
back to list of logs
<craigbro>the guix manual, particularly the dev/contribute process, is refreshing well done and documented <craigbro>I was able to get a working dev env and try to get kitty updated in no time at all, mostly waiting for the single threaded guile build phase <craigbro>added two deps it needed, but I decided I dont need a terminal that requires simde, go, python, it's own crypto libs, and fonts in it's build phase <hapst3r>does anyone know if there is a "standard" branch expected when creating a new channel? <jakef>if you don't specify the branch i think the default value is master <hapst3r>I fought for a felt eternity yesterday and struggled to get it all working. And part of it seems to have been that I was using the branch "main" instead of the branch "master", when specifying this in my channels.scm file, problems seemed to dissappear, whereas commenting out the branch specification would make problems re-appear. <hapst3r>I mean I kinda figured by watching the defaults of other channels and watching a youtube video about setting up your channel, but this was very frustrating and should DEFINATELY be documented <hapst3r>jakef: Thanks for mentioning the code where it is specified. When setting up the channel, I only checked the manual and went bonkers. Since I am in the process of preparing some adjustments of some parts of the documentation, I will include a note regarding this. For a newcomer, this is definately something to trip over, and the manual section about "Creating a channel" -- a step by step tutorial otherwise very well written -- should <meaty>is it just be or are scheme regexps wierd? <meaty>.* is un-greedy when it's in a sub-expression, seemingly <apteryx>that'd be surprising; guile just uses the gnu libc <apteryx>which should be as standard as any when it comes to regexps <meaty>Then "(target_include_directories\\(.*)(core/deps/json)(.*\\))" on "target_include_directories(${PROJECT_NAME} PRIVATE core core/deps core/deps/stb core/deps/json core/deps/asio/asio/include)" should make the third field cover " core/deps/asio/asio/include)", right? but it gives ")" and my substitute* expression doesn't work right <hapst3r>when changing documentation in preparation for a patch to be sent, to I need to run `./configure` even when I already ran it before using `make` when setting up my local source checkout? <Kolev>Does Guix have a Matrix client? <luca>Looks like just weechat-matrix and emacs-emenmt <Kolev>luca: Ement does not work currently. I'll just keep using it in LibreWolf then. <Kolev>I hate Matrix but project chats are on it. <luca>There's also matrix2051 if you don't feel like leaving your IRC client <Kolev>luca: I actually of primarily use XMPP. <luca>Is gnutls an official gnu project? <luca>Usually they are pretty against POSIX ways as opposed to just GNU. (thinking in regards to which) <apteryx>luca: not anymore, but it still feels as one <hanker>How do I file-append with an output from a package? <civodul>hanker: unfortunately ‘file-append’ does not let you refer to specific outputs <iyzsong>hanker: this could work: #$(gexp-input (file-append gtk+ "/bin/gtk-launch") "bin" #:native? #t) <sneek>Welcome back futurile, you have 1 message! <futurile>jlicht: ah got it - sorry fallen down on writing up the notes (been on holiday) <pastor>Hello, the NTP license to which license corresponds in 'guix/licenses.scm'? <futurile>pastor: I think there's something like 'other' that you can use <pastor>futurile: is there really that option? Do you know of a package that makes use of that to specify the license? <futurile>pastor: not of the top of my head, (sorry!) - I've definitely seen packages have to specify something else <futurile>nmeum: seems very quiet around here today and QA hasn't processed it yet, you might have to nudge a couple of times <nmeum>I still haven't fully understood how QA works and why it sometimes take more than a month to process a patchset <futurile>nmeum: it's having a really really really tough time is the bottom line. It's been struggling to 'catch-up' for about 3 months, for some reason a set of patches that got accepted meant the build graph exploded. That's what I got from a conversation with Chris at Guix Days, but I'm not expert by any means <wakyct>hey all, is there shepherd bonjour/zeroconf (not sure if that's the right term) service? Or is the perl-net-bonjour pkg what I want? <wakyct>I'm trying to navigate to a local address like <name>.<local> in my browser, the IP works but not the name so I'm assuming I don't have bonjour-type service installed <wakyct>as maybe expected searching 'bonjour' on the mailing list is not that specific ;) <wakyct>I already have avahi-daemon running -- shouldn't zeroconf just work then? <freakingpenguin>wakyct: You could try using avahi-browse to confirm the machines are publishing the .local hostnames perhaps. $ avahi-browse -alr i think. <wakyct>thanks freakingpenguin, yes I found that and I see the service <wakyct>I can resolve it with avahi-resolve-host-name. I can't ping it or browse to it though <mirai>maybe you need to set (name-service-switch %mdns-host-lookup-nss) in your operating-system config <wakyct>oh thanks mirai, I take it that's not the default then? <mirai>iirc its not, you have to set it yourself <ElephantErgo>Hey, so I'm having some trouble getting alpha-background working in Emacs, and the only lead I can think of at this point is something Guix is doing. When I set "alpha-background" using set-frame-parameter, nothing happens, but when I set "alpha", the alpha of the whole frame is set correctly. I'm running X11, EXWM, and Picom. I'm not sure where to go from here. Anyone else experience this? Any thoughts? <ElephantErgo>Important bit of context is that this works totally correctly out of the box on other machines running Arch and Arch derivatives, which is why I think it's something to do with the Guix's Emacs variant <podiki>i investigated the very same thing before and couldn't figure it out <podiki>i compiled emacs with the same configuration as on arch where it worked <podiki>but then i moved to wayland and with emacs-pgtk it works there <podiki>it does on x11 with pgtk too but runs into some issues i think since pgtk is not for x11 <ElephantErgo>Oh that's very strange... I wonder what about pgtk makes it start working... 🤔 <podiki>but didn't get to the bottom of it <ElephantErgo>Making sure it's the same flags as on Arch certainly saved me some time, as that was going to sorta be my first guess 🙂 <podiki>i also i think tried with newer cairo maybe? but yeah, could be something in dependencies for x? <podiki>i hope those are some clues, maybe stuff on emacs devel and around those patches when they included them is helpful? <ElephantErgo>Having it be something outdated somewhere in the X11 stack somewhere would make a lot of sense. It's likely something that isn't needed for the PGTK version <ElephantErgo>This background is really good, though. Thank you a bunch for your investigation, because I would really love to see what it takes to get this working. I'll save all of this to take a deeper look at some time when I'm feeling more adventerous. Thank you a bunch 🙂 <podiki>ElephantErgo: no problem, good luck! <hanker>When I use eglot + rust-analyzer, rust-analyzer keeps spamming me with errors about not finding `sysroot` <hanker>What is rust expecting, and how can I give it to him? <graywolf>nckx: It actually needs to be: yes '' | ./guix-install.sh <graywolf>Was hoping for a way to allow selecting the options :/ <graywolf>But yeah the part I did not mention is that I am running the install script via guile-ssh. <graywolf>I wonder, is anyone working on upgrade to the 3.0.10 guile?