IRC channel logs
2025-10-18.log
back to list of logs
<apteryx>does being part of a team, for non-committer, at least means the person becomes part/member of the guix organization on codeberg? So that they can be assigned to reviews, say. <adanska>okay, finally got mutter building properly! awesome <hunter>I installed the gcc-cross-avr-toolchain but it seems like it's missing the libc components. Am I missing something or is it just broken? <Rutherther>hunter: have you sourced the profile / relogged? <hunter>Rutherther no I hadn't... sorry and thanks. <trev>can someone sanity check me and eval `(specification->package "git:send-mail")' ? i keep getting a "wrong type argument" error <Rutherther>You probably meant the send-email output of a package git, for that there is specification->package+output. Still, this by itself doesn't produce a wrong type argument, it produces an error that the package git:send-email is unknown <trev>it was working for me before :\ <Rutherther>specification->package produces packages, so it cannot accept outputs, because there is no way to distinguish <Rutherther>no way to distinguish... what output of a package you would like... (sorry sent early) <trev>Rutherther: this is true. I was really using specifications->packages, which seems to work that way <Rutherther>yes, but you need to provide a list to specifications->packages, it doesn't accept strings, but a list of strings <trev>a bit misleading, but my main issue i guess is that i can't use that on packages that are defined in my own modules, like (specifications->packages '("my-local-package")). <apteryx>am I the only one struggling to connect to the oftc network? <Rutherther>trev: you definitely can. How did you add those modules to load path? <trev>Rutherther: I'm in the middle of a bit of a system config refactor, but just using -L <trev>trying to think of a good way to describe what i have going on <apteryx>re OFTC network, seems to work, it was some stale connection or something from ERC <Rutherther>trev: I would look at the backtrace. It seems that in your environment an assumption of specifications->packages is violate <trev>Rutherther: i did an audible laugh after ,bt gave nothing <trev>yeah, it seems something got really messed up cause after reverting to a good commit of my configs, the problem still happens <trev>really irritating me, but doesn't seem to have any negative effect <vntsuyo>are there any guides on how to manage a Guix channel? <vntsuyo>how do I test all packages of a channel? <vntsuyo>guix pull fails when a package from a channel fails to build (i think?) <kestrelwx>If it fails to compute package definitions - you can have broken builds just fine. <kjartano`>To test all packages in a channel you would have to set up something like a Cuirass job to build that channel. <vntsuyo>so how do I test if a channel fails to compute package definitions? <kestrelwx>I think you could set up a Makefile that would compile your `.scm` files like it's done in Guix source. You would also need to keep track of your patches if you have any. <jackhill>I found https://codeberg.org/guix/guix/issues/3399 but I don't know if that's what I'm experiencing or not (unclear to me from the voluminous GDM debug logs) I do know if the wayland session fails to start up for some reason, GDM will fall back to x11 <jackhill>any thoughts on GDM not starting in Wayland mode even with (wayland? #t) after the recent GNOME updates? <luca>Hi, does anyone have any tips for setting up any kind of dbus keyring in a non-gdm/non-gnome environment? I don't even know where to start 😅 <jonsger>ACTION opened his first pull request at codeberg. This AGit workflow is pretty cool :) <Rutherther>luca: have you tried installing and starting a keyring of your choosing? Really there shouldn't be anything much complicated... as long as you don't choose a keyring that depends on something you do not have, like the gnome-keyring expecting gnome. As long as you will have only one keyring installed, you don't even have to start manually, it will get started by dbus <luca>Rutherther: Do you have any recommendations for keyrings? The only one I know of... is gnome-keyring :/ <listentolist>luca: What is the problem with gnome-keyring? I think that gnome ist no dependency of it. <luca>listentolist: lack of knowledge on how to use it I suppose 😅 <listentolist>Did you set up the gnome-keyring-service-type in the system configuration?? <luca>If I try to run gajim and save my password it will throw an error with `The name org.freedesktop.secrets was not provided by any .service files` <Rutherther>1. have you relogged after getting the service?, 2. if so, that means the pam didn't really start the service. Installing the service into one of your regular profiles should put the dbus file to a location where dbus can start it afterwards. However the keyring requires a org.gnome.keyring.SystemPrompter so you will also need to install gcr-3 <Rutherther>I think the keyring can get unlocked by pam only if your password is currently the same as the keyring password <luca>> Installing the service into one of your regular profiles <- What does this mean in practice? Is it not enough to add it as a system service? <Rutherther>no, because the service only adds pam rules, it doesn't put the package to any of the profiles. It assumes pam will be able to properly start the service. That might not happen in all cases (namely when the password doesn't match, but maybe there are some other issues I fail to see) <luca>Oh I see. So I should install gnome-keyring and gcr system-wide? (I assume in my home profile it won't have enough permissions) <Rutherther>of course it would have enough permissions in your home profile, it is ran as a user service, under the dbus session daemon <chipb>if you're still considering other options, keepassxc has a feature where it provides the org.freedesktop.secrets dbus service. <chipb>oh wait, maybe kwallet specifically does *not* provide it. that may have been why I ended up using keepassxc. it's been a while and my memory is fuzzy.