<pkill9_>in the manual, it says that "you can insert an inferior package pretty much anywhere you would insert a regular package". I can't use an inferior-built kernel to the 'kernel' parameter in the operating-system declaration, is this because of a fundamental incompatibility with how the 'kernel' parameter handles the kernel package given to it, or has it just not been modified to transparently handle
<pkill9_>inferior-packages like the other parts of guix have (like manifests and the 'packages' field of the operating-system declaration, like the manual says)?
<pkill9_>(the specific error I get when trying to build that system configuration is: gnu/system.scm:909:35: In procedure kernel->boot-label:
<pkill9_>In procedure package-name: Wrong type argument: #<inferior-package email@example.com 3d4b2a0>
***tilpner_ is now known as tilpner
<pkill9>oh looks like it's not incompatible, it's just the part that generates a boot entry name
***catonano_ is now known as catonano
<pkill9>sweet, that is the only part that needs changing
<pkill9>the checked out version of guix with that part modified to use inferior-package-name and inferior-package-version successfully builds the system configuration
<pkill9>so i think it just needs to check if the package given is an inferior-package, i think that's what the guix manifests does
<brendyyn>Anyone running a Tallos II with a free system written any blog posts about it? i'm quite curious
<j3kyl_>hey, icecat 60 are not correct displaying fonts. But its filled with those utf8 square all over. Guix .16/guix-install.sh
<j3kyl_>locale are instaled as emacs, vlc are displaying fonts correctly...
<j3kyl_>fps: it keeps warning me to install locale but IT IS installed
<brendyyn>im always getting a blackscreen when i reconfigure and i have to force a reboot. perhaps we should have a feature to reconfigure such that the new configuration is available in grub on reboot, but not instantiated immediatle
<vagrantc>hrm. trying to build an aarch64 installer image ... basically added target-arm64 almost wherever there was a target-arm32 doing essentially the same thing ... but it just hangs on the qemu step
<pkill9>well, the issue of not getting the package, not the issue of possibly someon sneaking in bad certs :) it's probably a technical issue though
<pkill9>kudos for all the work on inferiors, now I can upgrade the system without recompiling my modified kernel when any of it's dependencies change :D
<jlicht>pkill9: could you explain how you do this? One of my machines also has a custom kernel, and life is too short to be compiling kernels every week
<pkill9>yes! I'll write a guide, it currently requires modifying guix because the part where it generates the name for the boot entries fails with inferiors, but a simple check to see if the kernel package passed is an 'inferior package' or a normal package, and using the functions for inferiors will fix it
<jlicht>that seems interesting, I'll gladly read it once you have something written down
<janneke>aaarrrrgh, how do i print (with cups) i don't remember
<cbaines>janneke, I fought with cups this morning as well, I did win eventually though :)
<cbaines>enderby, right, so it's using the guix-daemon from root's profile. I think that updating the guix package in root's profile, then restarting the guix-daemon service might help.
<ennoausberlin>I currently run a low spec laptop while traveling. It has only 32 gb disk space. And texlive is quite big. Is it possible to transfer the store to an sd card to safe internal drive space?
<cbaines>enderby, guix pull works per user, so to update the guix package in root's profile, you'll need to run guix pull as root, then guix package -u guix also as root
<cbaines>ennoausberlin, ok, so moving the store to an sd card is probably possible, but it'll require a little care, as guix reads from the store during booting, so if you remove the sd card, the system won't boot
<pkill9>ennoausberlin: out of interest, what laptop are you using for travelling?
<cbaines>ennoausberlin, ok, I think I've done this before, but I'm no expert. I think I copied the contents of the store to the other device, then changed the mount configuration, reconfigured, checked it worked, and then removed the store data from the original device.
<cbaines>One neat trick I picked up is that once you've got the system booting and mounting the store from the sd card to /gnu/store, you can bind mount /gnu to somewhere else, say /mnt/gnu to allow access to /gnu/store on the internal storage, so you can delete it to free up space.
<ennoausberlin>cbaines: Do I have to start copying from a live boot or stop guix daemon? I am a little nervous because I dont want to break something
<cbaines>ennoausberlin, as the store contents is immutable, it should be safe to copy it while the system is running
<cbaines>I'd avoid running any commands that would change the store contents though
<ennoausberlin>cbaines: I thought so, but was not sure. I am not a long time guix user yet :)
<cbaines>providing you don't delete anything from the internal storage until you've got it working with the sd card, you should be able to boot previous system generations if something goes wrong
<ennoausberlin>cbaines: Ok. I will give it a try. Thank you for your suggestions
<cbaines>ennoausberlin, you're welcome, good luck :)
<ennoausberlin>Is there an easy way to get the internal ath10k wifi to work? At the moment I use an USB wifi extender, but that blocks one usb port and I have to boot ubuntu first because usb_modeswitch is missing on guix I guess
<grewil>Newbie question: I wanted to start over with a fresh guix package manager on my Debian (as I accidentally installed a huge number of packages). I deleted /gnu and /var/guix, then did a new binary installation according to instructions. But when I did "guix pull" in the new installation, it started to install the huge pile of packages from the previous installation. What do I need to delete apart from /gnu and /var/guix in order to
<grewil>mbakke just in case you're interested. I have now tried again with both 0.15.0 and 0.16.0, and I can only get the substitutes authorized in 0.15.0. My reinstall script is here: https://paste.debian.net/1054964/ - afaik it should be correct enough to work.
<civodul>vagrantc: the one rue d'Alibert looks like the closest one
<civodul>they have veggie options, not sure if it's gluten-free though
<mbakke>grewil: For 0.16, the key that needs to be authorized is "~root/.config/guix/current/share/guix/ci.guix.info.pub"
<mbakke>Throwing Glib into the mix only adds 200 rebuilds for current staging.
<grewil>mbakke aha, thanks! I should try update the manual, it still says the old one.
<mbakke>grewil: Hope it works! Note that once you've run "guix pull", it doesn't matter if you started from 0.15 or 0.16.