<apteryx>thanks for the config, I guess it'd work; I'm still trying to figure out the most minimal thing to do to get it to work, so that if I find it I can arrange to have the service default to use that
<ChocolettePalett>AFAIK, it defaults to some weird directory in /var/... when launched as mpd user (as a system service) so I don't think $HOME is a problem
<apteryx>I'll try it after I've run out of things that look simpler to try :-)
<smmm>hey all, I am writing a service to manage a daemon and I am having some trouble actually using it in my system config: https://paste.debian.net/1278502/ when I use the guile repl to load the path, things like (define s ...) (service? s) do return true, but `guix system search -L ....` comes up empty, any ideas?
<ngz>Hello. I get a "Throw to key `gnutls-not-available' with args `("(gnutls) module not available")" error when trying to use mumi from a Guix worktree. Are there additional steps required to make use of this tool?
<abrenon>sorry I really thought I could help, but I'll let someone who actually knows these things answer your questions to avoid adding more confusion and I'll read eagerly because I'm interested in the subject too
<Gremlin8483>still for a server or minimal build the less the better
<andreas-e>Well, if there is nothing to do, the daemon does nothing... It is mainly an interface to the store. I think it is a daemon because it needs root rights and then interacts with different users.
<jpoiret>it technically would be possible to run the daemon as user in a PID+mount namespace, on demand
<jpoiret>Gremlin8483: you can basically tweak Guix in exactly the way you want, but you'll have to rebuild all packages that change
<jpoiret>compared to gentoo, where modifying one package in the dependency graph doesn't cause all dependents to be rebuilt (I believe)
<jpoiret>civodul: so, looking at the git history, a lot of basic tools have been updated, but I'm not sure if it's enough to warrant a comment in the core-updates news
<jpoiret>i guess there's the update of wayland-protocols that is quite noteworthy
<Guest26>hello. Since recently when I log into gnome xorg on guix system I get the gnome error page asking me to log out. No matter what generation I roll back to. May this be because of the core-updates merge?
<jpoiret>do "dmesg" or "/var/log/debug" contain any lines that could be related to this error?
<Guest26>in GNOME when you press the super key the desktop gets smaller and you can select apps amd stuff. thats what i mean with "shell view". when you press the super key again you get the desktop fullscreen again. but in my case instead of the desktop i get a blank page with the error message
<Guest26>would be helpful if someone who already uses gnome (wayland) could try xorg and report if they get the same error or if its just an error on my side
<Guest26>i'm not seeing any obvious errors in /var/log/debug or dmesg afaict
<zamfofex>Are both of those important to have installed for you?
<panosalevro>hmm I use network-manager for internet access. idk what would happen if I uninstalled glib?
<zamfofex>Is glib directly installed to your profile, or is it a depenency of a different package you have installed?
<zamfofex>Note that you can’t really cause packages to malfunction by “uninstalling glib” in Guix. Usually you’d have it installed to your profile if you want to e.g. write GTK applications and compile them.
<panosalevro>let me check which package causes the problem and will get back to you. thanks!
<panosalevro>removing `network-manager` seems to have fixed the issue
<andreas-e>"guix pull" was really slow for me yesterday, with around 50kB/s. I noticed it because I had deleted the checkout cache.
<civodul>it eventually succeeded for me, but connection establishment took a minute or so
<PotentialUser-6>Has anyone got guix with linux working on a new-ish Dell XPS 13? I can't figure out how to get the sound working. I think I need to add `sof-firmware`, which I've added to my config.scm and reconfigured...but I think I might be doing something wrong. The only potentially helpful error I can see in dmesg is: "unknown sof_ext_man header type 3 size
<abrenon>alethkit: as in the data/program duality ?
<podiki[m]>PurpleSym: re: pyproject-hooks and setuptools; right agreed. I left it as a propagated input to avoid me changing however many packages that used it via pep517; but I also didn't do the actual deprecation in my patches. let's see how it looks first and I'll get some review, and if so can go through with that change and hopefully not too many packages needing setuptools
<mekeor[m]>even still after reading about the 25MiB guile binary
<podiki[m]>PurpleSym: actually, I will remove the setuptools propagated-input and at least see how bad it is trying to build to yubikey-manager; I'll have to see about the deprecation for pep517, but I've been holding on to this series for too long already
<attila_lendvai>the warning "imported module (guix build utils) overrides core binding `delete'" is very pervasive... it would be nice to have a solution for it that doesn't involve every package writing #:use-module ((guix build utils) #:hide (delete))
<mekeor[m]>personally, i feel like this bootstrap attempt within the guix community is one of the very few things in recent software development that brings hope...
<mekeor[m]>would it make sense to directly and dedicatedly share this blog post in the mailing-lists of gcc and glibc? because they are explicitly criticized
<janneke>of course gcc-4.8.0 comes with g++, but in _source_
<janneke>you need a _binary c++ compiler_ to compile that first g++
<mekeor[m]>yeah, i understand that making the path of bootstrapping gcc4.8.0 longer is tedious, but i guess it's not a fundamental issue. a fundamental issue, for me, would be not be able to bootstrap at all...
<jpoiret>persona5: you can use modprobe.blacklist=... to disable some drivers manually
<persona5>jpoiret: when i try to install linux-libre isn't that automatically as if the proprietary drivers are blacklisted? i think the problem is that guix wants to use that device nevertheless, instead of considering the other gpu
<jpoiret>persona5: some drivers are still included because they might have some completely free support for some gpus but not all of them
<apteryx>jpoiret: OK, I've found something new: Apr 26 13:48:45 localhost pulseaudio: [pulseaudio] module-udev-detect.c: /dev/snd/controlC1 is accessible: no, by adding (log-level . debug) to the puseaudio's daemon.conf
<apteryx>I've added the mpd user to the 'audio' supplementary-group, but that doesn't change that
<soygirl>i hate being stuck between the options "works but blobs" (nvidia), "doesn't work but open source" (amd), and "lol" (other (intel))
<lilyp>didn't i just say that amd has the same blob shit?
<apteryx>they used to compete in the mainstream before Nvidia bought all their employees
<bjc>i still have one of their cards. from 1996. in my bebox
<ieure>bjc, Yes, but they're not a player in the consumer space anymore.
<ieure>I had some of their cards ages ago, pre 3D era. Worked fine, but nothing special.
<bjc>they had hardware video decoding, and fast blitting, as i recall
<unmatched-paren>unless some miracle occurs and $COMPANY's executives magically obtain souls i honestly don't see how linux-libre is going to be survive in the long term, given the three have all abandoned open drivers for their latest gpus
<soygirl>when i tried using beos on my old computer in the 90s and it didn't support my network card but everything else worked :( im still sad about that
<person5>do you think Purism will be the solution for free hardware longterm?
<attila_lendvai>quilt fails to build on master due to one failing test:  $ quilt patches -- /dev/null dev/null null --- -- failed
<Guest3>When I give a package a native-input and run it with "./pre-inst-env guix shell some-pkg -- some-pkg" and that works, does that mean that native-input is enough or could it still be that e.g. propagated-input is necessary?
<rekado>if you have that package installed then this test doesn’t allow you to make a decision either way
<rekado>a native input is one that must run on the host architecture at build time
<rekado>a propagated input is one that must be installed into the same profile as the target package
<jpoiret>Guest3: in general it depends on what kind of input it is
<attila_lendvai>ACTION gives up for today with the hope that the opensource fairies will fix this overnight, and substitute availability will be better, too
<Guest3>so there is no easy way to check if i make the right decision? i'm packaging a gtk app and for me it works having glib:bin as native-input only, but that could be because i have that already installed from some other package
<jpoiret>cbaines: seems like the data.qa website is being extensively crawled by search engines. Searching for "gnu quilt" on duckduckgo returned 3 hits
<jpoiret>Guest3: you can test your package out by using `shell -C`, although it might break more than expected
<podiki[m]>gajim users, it builds locally, patch incoming (for python-k5tests and python-gssapi)
<carmenshea[m]>Hello Guix. Updated my system last night, Guix running Sway. Alacritty crashes now with the following error [wayland-client error] Attempted to dispatch unknown opcode 0 for wl_shm, aborting. Aborted. I've done some digging and found that this was occurring a couple of years ago (2020 - 2021), as noted in the alacritty issues #4206, comment indicates that this was a wayland.xml issue. At the moment everything else seems okay.
<bjc>carmenshea[m]: yes, it's an incompatibility with alacritty 0.9 and the current version of sway. alacritty 0.12 fixes it, but unfortunately requires *a lot* of dependency updates, so is being worked on separately