<raid5atemyhomewo>though note that some of the patches for ZFS change things in the gnu/build/ as well, can a channel override those?
<jgart[m]>That's fine. Let's keep in touch. I still have to sign all the packages/rewrite git history in that channel. It is currently not "ready for production"
<jgart[m]><raid5atemyhomewo "though note that some of the pat"> Maybe we can ask the community what would be the best way to go about this. A macro might help out here. Let me take a look at your patches first and I'll get back to you.
<raid5atemyhomewo>for example, it changes the dependencies of the file-systems Shepherd service, makes it extensible as a Guix service that accepts Shepherd provisions it should wait for
<raid5atemyhomewo>which is needed for /home on ZFS, otherwise /home will not get mounted early enough
<raid5atemyhomewo>as well as changes to allow a Guix service type to add kernel loadable modules
<jgart[m]>raid5atemyhomewo: feel free to reach me at #libremiami:matrix.org or the xmpp-matrix gateway to the same channel. I also check the logs at #freenode_#guix:matrix.org daily
<iyzsong-w>raid5atemyhomewo: your ZFS work look great! I'd likely look into them this weekend...
<mdevos>apparently it has been eaten, it doesn' appear on logs.guix.gnu.org. Resend:
<mdevos>Hi Guix! What's the recommend method for compiling a single C source file, depending on some shared libraries from a package, to a single executable in the store? (To be used in a service definition)? c-compiler in guix/scripts/pack.scm perhaps?
<leoprikler>does the single c source file come with no makefile whatsoever?
<omnivg>Hi, I have a beginner's question regarding installing guix. I am running a foreign distro and performed the binary installation as described in the manual. I also would like to use emacx-guix (guix.el) to manage the system. Instructed by the README in guix.el, I installed guix and guile to my user profile (~/.guix-profile). Now, I am confused because the ~/.config/guix/currentbin/guix is shadowed by the newly installed
<roptat>omnivg, that's not good, the guix in .guix-profile is older than the one in .config/guix/current
<omnivg>roptat, yes it seems to be the stable version 1.2
***str1ngs_ is now known as str1ngs
<roptat>yes: the one in .config/guix is the latest you pulled, and it defines a guix package. Since it cannot know of itself, that package is necessarily at least one commit earlier than what you pulled
<roptat>if .guix-profile/bin/guix shadows the latest pull, next time you do "guix upgrade", it will use its own definition of guix, which is older than itself, so you'll keep downgrading guix without even noticing
<roptat>that's the whole reason why we have a separate profile for guix pull
<vagrantc>lfam: i'm of the opinion in general that anything anyone wants on any of the -generic kernels that doesn't interfere with the "linux-libre" kernels (e.g. no-op because already enabled) is a good thing
<lfam>I was also thinking that perhaps some enterprising Guix porters should apply for early access to the upcoming BeagleV RISC-V computer from BeagleBoard. They will be making them available to developers early
<lfam>It would be nice if Guix System was supported when they were released. I bet there will be a small surge of interesting in this platform at that time
<thorwil>hi! the `guix` command suddenly stopped working (every argument is taken without effect). /home/thorwil/.config/guix/current/bin/guix points to /gnu/store/xa1xx4gpnvvf4wpzx63v1swl7gvqyw5d-guix-command
<thorwil>which `file` tells me is empty! any idea how something like this can happen?
<thorwil>meanwhile, `sudo guix pull` still works. is there any chance of repair short of installing guix anew?
<lfam>I use btrfs for /home but I use /gnu so heavily and I've been worried about performance there with btrfs
<lfam>Anyways, after you change that symlink and get your Guix working again, please send your info to the bug thread
<stikonas[m]>btrfs is alright... Especially if you do incremental backups
<lfam>thorwil: The questions I asked should be answered in your reply. The history of your current-guix profile will also be important. You can use `guix package -p ~/.config/guix/current -l` to show it
<vagrantc>debian now enables user namespaces by default ... that's more-or-less good news for getting guix running on debian
*vagrantc suspects to see more test suite failures
<thorwil>lfam: ok. still a bit puzzled by the structure in /var/guix/profiles/per-user/thorwil ... but i’ll get there
<lfam>thorwil: The 'current-guix' file is the profile updated by `guix pull`. The 'guix-profile' file is the default profile for package installation, like with `guix install foo`
<lfam>The numbered variants of those files are the previous generations of those profiles
<lfam>And these numbered profiles ultimately point to their "real" location in /gnu/store
<lfam>I hope that helps! Please ask questions if you are stuck
<thorwil>oh well: ln: failed to create symbolic link 'current-guix/current-guix-4-link': Read-only file system
<lfam>Indeed, my missing store item is not in the database
<thorwil>scrolling back, i just notice that `sudo guix pull` led to several "removing corrupted link ‘/gnu/store/.links/xxx’"
<Kabouik>Hello #guix. I'm new to guix and still into the testing phase. Could anyone confirm that if I installed it using the guix-installer.sh script, deleting /gnu would delete everything guix related including installed packages and dependencies, or is there something else I would need to clean to start from scratch?
<Kabouik>I'm sorry to flood the channel about how to remove guix! I really liked the tool, but don't want to do my tests on this machine. And unfortunately removing guix is not as easy as getting it ready with the install script.
<Kabouik>There's indeed something in /etc/profile trying to load any .sh file in /etc/profile.d/, but it doesn't mention guix anywhere and the modification date is older, I can't tell if it was there before
<lfam>It's a normal mechanism for extending /etc/profile
<lfam>What I mean is that most (all?) distros will have it
<lfam>I think the existence of that guix.sh file is probably cached by bash somehow, which is why I suggested logging in again
<Kabouik>I tried logging in again (just with bash --login, not by restarting my full session)
<surpador>So just installed espeak on guix system without any DE installed, and it seems really quiet. Might just be my speakers- is there any concept of a global volume setting other than espeak's own command line option for amplitude? And if so how would I change it?