<cbaines>I don't get why the library version is old...
<cbaines>I did try building it, and I'm 95% the way through what I guess is the build phase
<PotentialUser-29>cbaines: ty for the support earlier. I got it working. though I am still a bit unsure about the record syntax at work here since I never touched guile before. can a record be shadowed with "new values" per se so that the end result is old record with "new values" overriding where applicable?
<PotentialUser-29>cbaines: tyvm for the link again. Will have to learn more guile in the future guess :) I want to use guix system/sd on my work machine and with your help above I am 50% there. a bigger hurdle is getting a scala dev env (which I need for work) I guess till scala 3 drops in december the compler wont make it into guix perhaps I can make due with dock
<mfg>leoprikler: i'm pretty certain i don't understand things correctly. But now i think i know what i did wrong... git-fetch wasn't executed because i had used another link in between which has the same repo and therefore guix didn't try to redownload it. Thus the breakpoint on git-fetch doesn't fire - lel.
<mfg>but thanks for reassuring that guix repl is what i want to use :)
<jayspeer>hey guys, how do I get gnome to see my bluetooth device? I've managed to use using the bluetoothctl
<jayspeer>follow up question is: is there a pulseaudio-bluetooth package? I can't seem to find it
<apteryx>civodul: do you think https://issues.guix.gnu.org/43818 should be fixed at the level of Guile? it seems odd that a trailing slash ends in the %load-path or %load-compiled-path. If I compare with Python, it seems to normalize the entries in its sys.path in a consistent manner.
<jonsger>cbaines: you don't have your guix-patches thing running anymore?
<cbaines>jonsger, I do, but the domain names might have changed
<maav>lfam: guix refresh --list-dependent git says "Building the following 108 packages would ensure 241 dependent packages are rebuilt", so if its the sum it should go to staging, if the number that counts is the second one can go to master :)
<lfam>I guess that all of us who used to update Git immediately got tired :)
<maav>lfam: right now i don't have machine to compile these 351 packages, it's getting really hot just with one (new) test for check-system... :)
<lfam>It's okay, maav, that's what the build farm is for :) I'm building the latest Git now and will push shortly
<jlicht>does anyone know of a package that uses the guile scripting facilities of GNU Make?
<PotentialUser-92>Why is Guix System, a rolling release distro, still using an old version of GNOME from 2019? Isn't GNOME 3.38 stable enough?
<lfam>PotentialUser-92: It takes a lot of work to update the GNOME ecosystem, and nobody has completed that work yet
<ryanprior>PotentialUser-92: a couple potential reasons. First of all, it's work to update everything and maybe nobody's done the work yet. Second, we do have a stable release cycle for packages with lots of dependencies, which might include parts of GNOME.
<jonsger>cbaines: it would be pretty handy if the branch name would be derived from the issue number :)
<cbaines>jonsger, it's derived from the Patchwork series number
<cbaines>I guess the issue number could be used, but that would get a little complicated where you have multiple series for a single issue
<jonsger>cbaines: I know, but it would be nice so I can checkout it more easy
<morgansmith>is there a way to do package transformation to a manifest somehow? I tried guix package -m manifest.scm --with-branch... but that didn't work. It works with package update and package build, but not manifest
<leoprikler>you'll have to write your transformation as scheme code into the manifest
***amiloradovsky1 is now known as amiloradovsky
<morgansmith>oh no. that sounds tricky. Do I gotta do the weird gexp transformations that I still don't know what they do?
<leoprikler>I'm not quite sure, but I think most transformations should actually be exported somewhere.
<leoprikler>If not, you can still copy the relevant code portion from `guix build`
<leoprikler>or just import options->transformation from (guix scripts build)
<leoprikler>That should work even better than the command line, since you can specify it for just the package you need or the entire manifest at will.
<dustyweb>I also see a defconst for it in the downloaded file
<efraim>My pine64 thinks its 2115 again, I might need to implement a fake-hwclock service to set the date at startup
<vagrantc>when it leaps past 2038, it gets hard to set it right.
<vagrantc>haven't seen that problem for a long time
<vagrantc>it'd be nice to have a fake-hwclock service that at least sets the date to the date of the system generation, to avoid backsliding into the abyss from which ntpd refuses to leap even if you insist
<vagrantc>efraim: in other words, looking forward to your service :)
<civodul>morgansmith: --with-git-url is like using (git-checkout ...) instead of (origin ...) in the package of interest (meaning that the checkout happens on the client side)
<morgansmith>civodul: ok so I completely ignored everything you said and made a procedure using options->transformations but the procedure I made wants a "store"? idk what that is
<morgansmith>maybe I should look at the package-input-rewriting function...
<morgansmith>wait, am I going to just have to create my own package that inherits the old package but has a new input? That's gross. I don't want to do that. I wanna use something like the transform-package-source-git-url function
<lfam>vagrantc: I think it would be nice if wireguard-linux-compat was based on 5.4, since that version will be around for a very long time (through 2025)
<civodul>morgansmith: yeah you can use options->transformations and pass #f as the first argument, it should work, but don't repeat it to anyone
<morgansmith>but what is store :'(.... I've been jumping through so many files and I cannot for the life of me figure it out
<morgansmith>oh it worked. I finally built a manifest with a transformation
<civodul>we need to remove the 'store' argument from that procedure and properly document it
<civodul>then people will be able to use it in their manifest
<civodul>the other option is to use package-input-rewriting & co.
<civodul>it shouldn't be difficult, but how it maps to a specific transformation option is less obvious
<morgansmith>does using package-input-rewriting require me to pass it packages? that doesn't sound like it helps me since I'm trying to modify a package...
<civodul>yes, as in the openssl/libressl example in the manual
<morgansmith>so you want me to just make a completely new package using inherit, then use package-input-rewriting to replace the old package with my package? Seems really overkill
<morgansmith>I mean it sounds really useful. But overkill in my specific situation
<PotentialUser-38>Hi! I am wanting to set my PATH in guix sd/system but the only way I found so far is setting it in my bashrc. Unfortunately that does not cut it in a few use cases :o. Anyone have any tips as to how I could set the PATH (or other env variables) in preferably my system config.scm?
<morgansmith>I put it in .profile but it depends on a lot of things. Your shell should source .profile fine in the tty, but your desktop environment won't.
<morgansmith>You can sym link .profile to .zprofile or something? there's some filename that most desktop environments do source
<morgansmith>I just make sure to source my .profile in my .xsession, but that only helps you if you use a .xsession
<morgansmith>I don't think there is a way to set environment variables in your system config.scm. There is possibly a way to do it for a certain profile though
<morgansmith>It might require making a package definition just for that though
<PotentialUser-38>morgansmith: ok nice that looks like something I can try. it will be much more consistent then what I have currently. also I might borrow some of your emacs guix dev env config for emacs also if you dont mind :)
<morgansmith>Please read the disclaimer at the top of that file :P half of it doesn't work
<morgansmith>the emacs-guix package freezes my emacs a lot and often just doesn't work (idk why)
<morgansmith>It's licensed using the unlicense so you can plagiarize all you want :) I hope you find something nice in there
<PotentialUser-38>morgansmith: ok that mirrors my experiences with emacs-guix then :) I thought it was I who couldnt set it up :)
<morgansmith>If you can figure out how to work it, I'd love to hear it :P