<PotentialUser-18>On this note, if I understand it correctly, when I time-machine or change generations, I use the guix version from that commit to operate, so can I use a new version of guix while installing old software?
<rickame>i get it i just dont really like it but np
<rickame>there's something special and unique about a snapshot release of a known good, + minor version for fix only patches, that a rolling release can't ever give
<singpolyma>PotentialUser-18: I'm not an expert there, but pretty sure time machine means using an old version of guix to install the old software
<rickame>because y ou can only pull x version, but then never the y patch only thta follow
<unmatched-paren`>hi guix, when my device hibernates i hear a horrible scratching sound coming from the ssd; i checked and noticed that my swap is 4gb, while my ram is 16gb; would that be related? i know this isn't specifically related to guix, but i'm wondering if there's something i can do in my config.scm to stop that?
<sneek>unmatched-paren`, rekado_ says: pascal is not bootstrappable. There’s an old unmaintained GCC frontend for pascal, which I failed to package. And there’s the free pascal compiler, which we already have. We build it with an older binary of the free pascal compiler.
<rickame>well that doesn't match how i dev. i put more polish in before cutting a release than in the middle
<rickame>the 'continuous' improvement has no structure. just seems endless stream of rabbit 'pellets'
<rekado_>you need people to actually backport fixes, carefully test to make sure the backport isn’t actually creating new bugs, and make sure everything keeps building with all the other packages that are frozen in time and patched beyond recognition
<rickame>sure, so have an evergrowing testharness to automate that part
<unmatched-paren`>i'm sure it would be possible to write a guix-stable channel if you really, really wanted to, but then... what's the point? you just get slightly older versions of things. there's no stability benefit (unlike arch v. debian) because of the transactionality inherent in being a functional package manager
<rekado_>rickame: sure, just saying that this cannot be extrapolated.
<rickame>id like that personally. the point is that the ppl accepting updates to guix-stable would evaluate them for scope and probability to introduce regressions
<rickame>the goal would basically be any code that fixes something and nothing more
<rickame>so if someone is running into a bug they report, code fixing it is pulled into guix-stable, then anyone else running it can update and just get fixes
<unmatched-paren`>pacman is not transactional, updates can and often do break stuff, which is probably the main reason people why people stay away from arch and derivatives (it was the reason i did, at least, and it seems like a logical reason to avoid it)
<PotentialUser-18>what might be better is to collect statistics about failed builds and mark commits that have those, so then you could just set guix to not use commits that can't build stuff you need
<nij->Hi! `guix describe` says I'm in commit f870977 (2022, Jan 28), but I still don't get `guix home`. What did I miss?
<rickame>guix has so much promise. it can be the biggest distro in all linux
<rickame>nothing is better than declarative reproducible config in simple composable files
<unmatched-paren`>when you do a `pacman <whatever>`, it literally swaps out all the files that it needs to. when you do a `guix pull/upgrade/system reconfigure`, it builds a profile in the store, creates a bunch of symlinks in /var/guix, then atomically replaces your profile in one go, which makes it really easy to implement stability features etc. there's a reason the word `dependable` is on the front page of the guix website ;)
<rickame>imagine typing things into lightning box to make changes
<xelxebar>The command `id -u` just prints out your numerical user id, so `/run/user/$(id -u)` expands to something like /run/user/1000, most likely.
<nij->ls /run/user/1000 : No such file or directory
<nij->Bummer.. reconfiguration just failed "... guix substitute' died unexpectedly. Will do it again.
<xelxebar>nij-: Note, elogind probably needs to be added to your *system* services in your operating-system declaration, since creating directories under /run/user requires elevated priviledges.
<nij->Oh! Adding %desktop-services this time did work.. last time it appeared to be broken because the system took some time to set things up ( I guess..), and I thought the system was broken by the updates. Thanks :)
<nij->Baby! I'm ready to rock n' roll! Thanks so much for your help today. I will be back tomorrow. Gn :):)
***califax- is now known as califax
***aya is now known as gyara
<Charles[m]1>Any clue why docker containers cant use internet unless --network host ? I'm using nftables.
<raingloom>/run/user/$UID/gvfs is broken again for me for some damn reason.
<dp0>So I recently did a guix pull and guix system reconfigure and was wondering if anyone else has run into an issue with gnome being yellow?
<dp0>I even re-installed from scratch using the latest stable from gnu.guix.org (just to make sure it wasn't from my mucking around) and even the login page is still like entirely yellow.
<Charles[m]1>dp0: I'm not sure what you mean by yellow. When I upgraded to gnome 41, I noticed that my color profiles were off. try messing around with the profiles in the "color" section of the gnome settings.
<gordon1>so i'm trying to make simple package that have few files in the channel repo alongside with the .scm recipe that i want to install in /bin/ of that package but with (source #f) and trivial-build-system it looks like i have no access to channel repo if i try to do (copy-file (search-path %load-path ...)), am i doing it wrong?
<gordon1>it is build in some sort of container, isn't it?
<gordon1>can i somehow put just a local file as an input?
<vivien>guile-gcrypt has a really strange behavior when generating small-sized RSA keys
<vivien>Up to 64 bits it complains that it’s less than 16 and aborts (!), starting at 65 it works, but sometimes for less than 64 bits it simply raises an exception and I get: In procedure generate-key: gcrypt: Échec de l'autotest
<pinoaffe>jpoiret: I managed to set up git send-email and send some patches using it, thanks!
<sneek>zimoun_ was last seen in #guix 2 days ago, saying: civodul, thanks. I will open an issue once I will access again to my colleague's machine. But I guess it requires a kernel update..
<cmack>my guix system had gotten into a state where `guix pull` fails and I think it's because it either went to sleep or lost power while doing a guix pull before. I have tried rolling back but I still get build errors with guix pull. `(exception system-error (value "git_libgit2_init") (value "~A") (value ("Function not implemented")) (value (38)))`
<cmack>Does this look familiar to anyone? Or, does anyone have ideas on how I can try repairing it?
<jpoiret>are you able to guix pull --switch-generation?
<pinoaffe>I think porting guix (the package manager) to os X would be great, but it seems like it'd be a lot of work
<cmack>jpoiret: I've been dealing with this as I have time for over I week... my memory is it was a guix pull. I've tried rebooting into a previous system generation but that didn't fix guix pull either
<cmack>does the error `(exception system-error (value "git_libgit2_init") (value "~A") (value ("Function not implemented")) (value (38)))` point to anything that's not related to the generations? I have git installed so that is a bit mystifying
<drakonis>sounds like something not implemented in guile-git?
<podiki[m]>anyone know how to get correct time in a guix container?
***nickreset[m] is now known as chattering[m]
<drakonis>cmack: you've done a pull and a reconfigure, yeah?
<drakonis>try rollbacking and doing it again to see if a generation based on a newer commit does not have this problem
<eonn>Does anyone on GuixSD have a `which cc` that links correctly to gcc? The python module I'm trying to package assumes that cc will point to something useful, and I'm deciding whether I should set an alias on setup
<drakonis>cc isnt available by default but you can certainly include a symlink
<gordon1>adding mount tmpfs to /run is a sure way to brick your system, just keeping updated if someone wants to try that for some reason
<lfam>eonn: It's typical for Guix package definitions to set make flags such as "CC=gcc", or to use environment variables in a similar way. It depends on how the package's build scripts decide to where to look for the compiler
<eonn>lfam: Unfortunately it's hardcoded to just be whatever "cc" resolves to. I'll browse some other packages to see how it's done
<lfam>eonn: That package doesn't have any non-implicit dependencies at all. I grepped, and cc-for-target is provided by (guix utils), so you'll need to import that if it's not already imported
<lfam>Alright, it might be a little tricky since it's a Python module written in a language other than Python. But it's definitely possible
<gordon1>drakonis: well, i don't have anything that manages "sessions" (whatever it is), so /run/user/* stuff never gets cleaned, for example keeping "on-first-login-executed" flag from guix home, so i'm trying to work around