<Kabouik>Ok, thanks. Yeah exactly, I was used to guix shell on my GuixSD test machine, but here I only have guix package manager on another machine and it seems to be an older version with just environment
<the_tubular>I was wondering if he built the package or used substitutes.
<Kabouik>Currently `guix` installed from Debian repo is in /usr/bin though, so if I understand well, I should use it temporarily just to `guix pull`, then add `~/.config/guix/current/bin` to my PATH, after which I can uninstall the old version from Debian repos. Is that correct?
<the_tubular>But I've never been able to fix my own sigfault so I shouldn't help people with theirs :(
<nckx>Yeah, it reminds me of the bad old Exherbo days when I managed to get into a similar state with glibc. A forgotten static binary saved the day but not until I'd panicked the legally required amount.
<jlicht>it manages package builds and garbage collection among other things
<jlicht>if it changes something in /gnu/store, it goes through the daemon
<Kabouik>I see, and is that not an issue if it's an old version while the package manager is updated thanks to guix pull?
<Kabouik>For instance, will it correctly garbage-collect for the shell subcommand that is not available in the guix version provided in Debian repos?
<jlicht>usually, not really. There are some exceptions, specifically with a recent bug fix w.r.t. a problem with the giant texlive substitute (if I'm not mistaken). Generally the daemon is pretty stable though.
<rekado>would be a shame not to use them until they give up
<rekado>civodul: it’s been a while since our last CI infrastructure hackathon, but there are still a few issues that keep the aarch64 build nodes on my desk. Should I describe the issues I need help with on guix-devel or should I open issues for each of them?
<gnoo>how can i use a file provided by a package in /etc/example.confg as an argument to (config-file)?
<rekado>I like these guys, but I think I need the desk surface for other clutter soon. The broken headphones in wait of repairs also deserve a more central spot on my desk.
<ytc>rekado: how can i set the 4.4.297 kernel in the /etc/config.scm file?
<rekado>ytc: you can add the (kernel …) field and provide the name of the variable bound to that version
<rekado>I see 4.4.298 in my version of Guix; that’s bound to linux-libre-4.4
<rekado>so (kernel linux-libre-4.4) should be enough
<rekado>you may also need to import the module defining it, so add (use-modules (gnu packages linux)) to the top of the file.
<rekado>good luck with these changes! I gotta go now
<attila_lendvai>is anyone using qbittorrent? since the c-u-f merge it's not working in a weird way: can connect to the trackers, gets a peer list, but peers are constantly showing up and getting immediately dropped from the peer list of the running torrents
<attila_lendvai>i mean, probably, because there's no new torrent blocking happening, and the issue start about the same time
<ss2>hello, I recently submitted a patch to get plugins in Thunar working: https://issues.guix.gnu.org/53008. I’m still trying to figure it out. It looks like that thunar can’t find the plugins, but XDG_DATA_DIR looks fine, and when installed, the plugins are in the thunarx-3 directory. Don’t know further.
<attila_lendvai>hrm, my ssh-agent keeps respawning as observable from constantly showing up on a new pid
<attila_lendvai>the unpack phase includes the applying of the (patches ...) entry, right?
<daviwil>fproverbio: Thanks! It's also very hard to summarize the value of Guix to other people because it can serve so many purposes. The best one can really do is try and demonstrate the functionality to help it click for people
<civodul>monadgauge: also, "guix home" allows you to run Shepherd services, whether or not you're on Guix System
<monadgauge>civodul: interesting, can these services interfere with the foreign distro ones? i'm not very well versed in this side of system management
<civodul>monadgauge: no, unless of course you're running the same service twice, for instance
<cbaines>civodul, I spotted in the maintainer meeting notes that you're looking at adding hardware to bayfront. Is there a plan for what to do with that new storage?
<civodul>cbaines: hi! the top priority will be backups, so we can manage more or less zero downtime for the essential services
<civodul>but before we get there, we'll have to pick storage devices and get them in place...
<cbaines>civodul, do you have an estimate of how much storage space is required for those backups?
<civodul>cbaines: i don't have that offhand, is it in the minutes? (haven't seen it yet)
<civodul>i think we threw some figures during the discussion
<cbaines>There's an increase of 1.3TiB mentioned, but I'm not sure what the baseline for that is
<apteryx>cbaines: 200 GiB used by world rebuilds, at the rate we were doing world rebuilds two weeks ago
<cbaines>apteryx, and is that 200 GiB space in the berlin store, or guix publish cache, or something else?
<apteryx>cbaines: I'm not sure, but probably mostly in the store
<cbaines>apteryx, ok. So I spotted the 1.3TiB in relation to storage space on bordeaux (which I'm assuming means bayfront)
<cbaines>I'm asking about this mostly as I'm uncertian about the discussion previously in the week, as it seemed like there at least part of a plan to try to serve ci.guix.gnu.org substitutes from bayfront in some manor (and I'm not sure how that would work)
<roptat>attila_lendvai, no the patches from the origin record are applied before the unpack phase, even before the derivation is started: the source for the package already has these patches applied (guix build -S will already have them)
***stikonas_ is now known as stikonas
<attila_lendvai>roptat, thanks! add-after 'patch was running after the build, so i have changed it to add-before 'build
<mikko>possibly a stupid question but how do i get sort of the base configuration that i can start editing? i'm just trying out guix with the provided QEMU image so i sort of skipped the installation step, and it seems there is no /etc/config.scm
<gnoo>there should be in ~/.cache/guix/checkout(s?)/...
<jpoiret>you can find one at /run/current-system/configuration.scm
<nckx>I think I'll take this moment to randomly point out that guix/contributor/$you! cloaks are a thing for those who want one. Possibly also guix/user/$you! cloaks because why the hell not. Enquire within for details. Offer void where prohibited. Not valid on Palm Sunday. May contain nuts.
<nckx>Don't let civodul hog all the pretty cloaks!
<lilyp>As far as it being a frontend to all of debbugs is concerned, I think only Guix users actually know that and make active use of it.
<nckx>I've deliberately avoided passing issues.guix links to non-Guix bugs. It feels… wrong, althoug there's absolutely no rational reason, I know.
<nckx>jpoiret: I think so, but I don't know what you're building. *If* it's something that would make it worth exporting X, *then* it's worth the temporary ugliness of @@, is my reasoning. But only then.
<jpoiret>i'd want to raise &invoke-error in the installer
<lilyp>nckx: Absolutely. "When in Rome" and everything.
<jpoiret>basically, i'm rewriting system* to be able to pipe the output of a command and display it in real time while also logging it
<nckx>I don't know what the policy of using (guix build …) in the installer is. If it's already used—hm, should we go straight for porting to INVOKE here? Or is that too much/too limited?
<rekado>did you know that the lower branches of conifers support a nutrient-rich layer of canopy soil? That soil supports a unique ecosystem of canopy-dwelling arachnids that cannot be found anywhere else.
<rekado>how do trees know how to grow their roots and branches? A big part of the answer is plant hormones called auxins that accumulate in the bottom half of branches and roots, inhibiting or enhancing growth. It’s little more than gravity and growth hormones!
<florhizome[m]>I’m not sure if I should report this or just send a patch for the one package that I experienced it:
<florhizome[m]>you can set TERMINFO_DIRS in search–paths so that the terminfo file for a terminal emulator will be definitely found. So far alacrity does this, which means a problem I had with foot was solved by installing alacritty.
<florhizome[m]>this should be relevant for a lot of other terminal emulators though, that have custom terminfos
<viivien>I’m sure there are 1-handed people out there that occasionally use computers
<nckx>Well, the *modern* way would be for these services to dynamically adjust to a changing world, not be configure-on-start monoliths that have to be brought down each time $something changes… It would depend on the service, of course, but it's rather an obselete design premise.