IRC channel logs

2025-11-14.log

back to list of logs

<mwette`>How big can /gnu/store get for a single-ish user system? I'm laying out partitions on a new system. I want ample space for other data.
<sneek>mwette`, you have 1 message!
<sneek>mwette`, janneke says: yes i got your reply, thanks! so it's actually a bug/feature of gcc to accept this, fair enough!
<mwette>exit
<civodul>Hello Guix!
<benjaminwil>hello guix!
<cbaines>morning o/
<trev>anyone ever experience propagated-inputs working with guix shell but not if installed using guix home?
<Rutherther>trev: did you relog?
<trev>Rutherther: no, let me try that now
<trev>nice, i'm stupid. guess it's a shell profile thing
<crestofthebeast>hi! installing guix on a fresh fedora 43 install, and am getting a signature verification error on running guix pull. anyone have advice on where to go from here?
<untrusem>hello crestofthebeast , welcome to guix land :)
<untrusem>are you installing using the script?
<crestofthebeast>i used this copr (https://copr.fedorainfracloud.org/coprs/lantw44/guix/), which probably isn't the best for understanding my install haha
<trev>crestofthebeast: what is in your ~/.config/guix/channels.scm ?
<trev>use the install.sh script from guix instead
<crestofthebeast>nothing, seems i actually have a broken symlink in there which doesn't bode well
<Rutherther>you didn't break any symlink, it's not supposed to point anywhere until you successfully do guix pull
<Rutherther>how's the full error message?
<crestofthebeast>guix pull looked like:
<crestofthebeast>```
<crestofthebeast>Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
<crestofthebeast>Authenticating channel 'guix', commits 9edb3f6 to 7e28687 (113,205 new commits)...
<crestofthebeast>[
<crestofthebeast>guix pull: error: signature verification failed for commit 9af82e589fff804c191a820a935a623f23c14bf1
<crestofthebeast>```
<Rutherther>please don't send mutiple lines here, use a paste site instead
<crestofthebeast>i'm currently giving a try to uninstalling the stuff the copr put in and using the install script instead
<crestofthebeast>apologies for dropping out--don't have a bouncer set up. been running off the install script, and am now bumping into what look like DNS issues when trying to guix pull. seem to not be able to reach any substitution servers during the command.
<crestofthebeast>error log is here: https://pastebin.com/kBw13S24
<Rutherther>did you follow this https://guix.gnu.org/manual/devel/en/html_node/Application-Setup.htm, namely the "Name Service Switch" section?
<crestofthebeast>did not, will do so now
<crestofthebeast>building and running nsncd did not fix the problem, though it definitely did receive connections during the guix pull run
<Rutherther>so you're still getting temporary failure in name resolution?
<crestofthebeast>yup. https://lists.gnu.org/archive/html/help-guix/2023-10/msg00102.html seems to indicate it's an SElinux issue of some kind, will try entering permissive
<crestofthebeast>ah, yup, that did it. must be a problem with the policy file, then
<Rutherther>are you using the latest policy file?
<crestofthebeast>i should be, if that's what the install script added when it asked if i wanted it. i'll go have a look-see
<Rutherther>no, it's not
<Rutherther>the install script adds 1.4.0, that's almost 3 years old
<crestofthebeast>ah, well that seems bad haha
<Rutherther>after you pull successfully as your user, try replacing the current policy file with /var/guix/profiles/per-user/$USER/current-guix/share/selinux/guix-daemon.cil
<crestofthebeast>will do, thank you for all the help so far
<Rutherther>really the situation is not ideal, it should get better after next release which should happen in January. I definitely have to check if this issue can persist and if so, we need to fix it before the release
<crestofthebeast>that file doesnt seem to exist on my install btw. i do have the file listed in https://guix.gnu.org/manual/devel/en/html_node/SELinux-Support.html#Installing-the-SELinux-policy though
<Rutherther>did you already pull successfully?
<crestofthebeast>not yet, just getting a lay of the land whilst it runs
<Rutherther>(as your user)
<Rutherther>it will exist only after you pull
<crestofthebeast>ahh
<Rutherther>you should definitely also pull as root and that will update the file from that link
<Rutherther>but currently it's probably old version - you could check that if you wanted with "/var/guix/profiles/per-user/root/current-guix/bin/guix describe", looking at the commit and checking the date it has been made in guix repo
<crestofthebeast>set my selinux back to enforcing and set the new policy file, and `guix install glibc-locales` seems to work perfectly :) thank you again!
<pranav>Hello, is there a preferred method to use an older version of the linux kernel (a version that got removed from latest guix commit) in an OS config? I tried using an inferior package but the kernel field only accepts a package type and not an inferior-package type argument.
<civodul>pranav: hi! maybe you’ll need to define that old version for yourself, either in your OS config file or in a channel?
<civodul>you could also file a bug to see whether ‘kernel’ could be changed to accept an inferior package
<ArneBab>mwette: that depends on how often you run guix gc. For me (two users, both are me) /gnu/store varies by 50-100 GiB in size (between calls to guix gc -d 1m ; guix gc --optimize). I don’t always run guix gc, because rebuilding stuff like Chromium or Firefox/Icecat takes ages. /gnu/store is currently 650 GiB for me (if anyone has a hint how I can reduce that efficiently, please tell me!)
<JodiJodi1>ArneBab: do you not use substitutes?
<FuncProgLinux>Is a newer version of libwnck planned for 1.5.0 or are those fundamental Desktop Packages already frozen?
<attila_lendvai_>my guix system started to have a cracking sound at some point when sound is played back by the browser, or FreeTube installed through flatpak. movie playback is fine. anyone else with this? any ideas what to look at?
<attila_lendvai_>it should be something recent, but could be that it's only now that i notice
<df0>i've not experienced any audio issues
<ieure>Does anyone have working _local_ printing on Guix System? I have an old LaserJet with parallel to USB adapter, but it isn't working.
<ieure>I added cups-service-type and added my user to lp & lpadmin groups. Gnome print settings doesn't open at all. Web interface can't find a local printer, and adding one asks me for a URL even though I selected local.
<ieure>On Debian, I basically install CUPS, plug in the printer and it Just Works.
<trev>ieure: mine recognizes the printer but doesn't print all the time. can't remember when it stopped working
<trev>i've successfully scanned recently though
<trev>don't forget to add the driver to the extensions of the cups service, if needed
<ieure>I don't think it is, at least, I've never had to care about that before. It talks PostScript or PCL.
<ieure>hplip-minimal is in the default driver list, though.
<ieure>Maybe I can use ghostscript to convert this PDF to PS and cat it to /dev/lp0
<trev>o_O
<ieure>That's basically what CUPS is doing.
<dajole>I'm trying to understand a section in the documentation (https://guix.gnu.org/manual/en/guix.html#After-System-Installation). It says that `sudo guix system reconfigure /etc/config.scm` updates the current user's system, not root's system. Does this mean I always have to run the command for root as well to ensure the entire system gets relevant security updates?
<Rutherther>could you quote the exact part that you think says that?
<ieure>Was just going to ask the same thing.
<dajole>"Note: Note that sudo guix runs your user’s guix command and not root’s, because sudo leaves PATH unchanged. To explicitly run root’s guix, type sudo -i guix …. "
<dajole>I may well be misunderstanding what this is trying to say :)
<ieure>Yes.
<Rutherther>that just says that the _guix_ executable comes from your user's path, ie. the one you got when you "guix pull"ed, instead of the one you would use if you switched to root completely, with"su -" and "guix pull"ed as root
<dajole>What are the repercussions of that?
<Rutherther>not any general ones, just something to know for making your workflow
<Rutherther>...like if you wanted to have distinct guix versions for system and your user's profile
<dajole>Wouldn't that mean that if I only ever upgrade from my regular user root doesn't get the updates? Or perhaps I'm still misapprehending 😅
<Rutherther>upgrade from your regular user meaning what command? and root doesn't get updates... of what? and why would root need any updates, do you log in as root on your system?
<ieure>Yeah, it's only a problem if you directly log in as root, which you really should not do except in extraordinary circumstances.
<dajole>My mental model is probably inadequate. The goal is to make sure I always have all security updates installed. Usually, I just log in as a regular user and run `guix pull` and `guix system reconfigure` as that user. I'm trying to figure out if I also need to pull/reconfigure as root. It seems that in a traditional distro if I e.g. have unattended system upgrades, it installs the updates for all users.
<dajole>And as I understand the documentation and what you are saying, in Guix it doesn't quite work that way, since the update commands are user-specific. Or am I still misunderstanding?
<ieure>dajole, You cannot run `guix system reconfigure' as a user, you must run it as root, with sudo. You do not have to do anything with the root account.
<dajole>Ah, so `sudo guix system reconfigure` does always upgrade the entire system; just that the guix executable that gets used is the user's rather than root's. Does that sound correct?
<ieure>dajole, Yes. Though depending on your definition of "the entire system," it may not update that.
<ieure>dajole, Example, if the two of us had accounts on the same system, and you ran `sudo guix system reconfigure' as user "dajole", it wouldn't touch packages in my user "ieure"'s profile.
<dajole>Thanks for your answers and being patient while I wrap my head around all this.
<dajole>Ah okay. Hm. So is there a way to ensure security relevant upgrades are always installed for all users?
<Rutherther>there is a way to do everything, it just means not using guix as most users do, like installing everything to system instead of using "guix install" as the users, being an example how to do it, not the only way to do it
<dajole>By "installing everything to system" you mean adding it to `(packages...` in the operating system configuration?
<Rutherther>another example would be that the user's wouldn't pull, but all would use the system guix in /run/current-system/profile/bin/guix and during updates of the system you would also run, as every user on the system, "guix upgrade"
<Rutherther>dajole: yes, that's a way to install packages to system profile
<dajole>Okay, that's all very helpful and clarifies what is going on. Thank you!
<bdju>Any updates on packaging deno for use with yt-dlp?
<ieure>bdju, Don't think so, I gave it an attempt but didn't get far.