<apteryx>rekado: currently things are as we left them last time -- we'd need to edit the GRUB menu entry manually to return to the current generation.
<apteryx>Perhaps I can revert the last failed bits pushed for the config that were supposed to transition it to the new RAID10 array, reconfigure, and then we should have something rebootable without this kludge
<PotentialUser-59>Is there a way to have grub-efi-bootloader install to `boot/bootx64.efi` instead of `Grub/grubx64.efi`? My systems bios forgets efi entries often
<atari_database>What are the minimum hardware requirements for installing 64 bit Guix?
<kitty2>atari_database: I'm not sure, but I don't think it requires much at all given how many people here use old laptops
<kitty2>I'm on a reasonably modern computer ; when doing most tasks I only use like 1% of my CPU lmao , I don't think guix takes any more than any other linux distro so I guess it just depends on what you do on the computer, yknow?
<kitty2>that is, apart from making sure everything works well with linux-libre
<kitty2>np ; if you have any more specific questions hopefully someone who knows more could answer haha , I haven't exactly tried guix on a large amount of hardware, just through it onto my desktop lmao
<kitty2>threw it on* like, a bit over a year ago I believe?
<atari_database>I'm buying a used laptop soon...buying specifically for using Guix, so just want to make sure it's powerful enough
<Christoph[m]>I tried guix shell --pure email@example.com, and guix shell does a great job hiding everything else. So well that when I try to use ghc, it tells me that it cannot find cat and rm. How can I find out which package contains rm and cat?
<jackhill>Christoph[m]: they're in coreutils. What I did was follow the symlinks from a different profile where they were present (in my case /run/current-system…)
<jackhill>Christoph[m]: out of curiosity, what are you doing ith ghc 4? Ordinarily, the fact that it doesn't retain a reference to corutils could be a bug, but I think we have it primarily for bootstrapping, so it's probably ok
<Christoph[m]>jackhill: I'm actually interested in ghc 8.10.7, which is the latest one packaged in guix. But that one cannot find gcc. So I looked up previous versions of ghc to see where it stopped working...
<jackhill>Christoph[m]: ah, I think you might find a newer one works, althougth they may all have that bug? I remember running into something like that before I got distracted… Anyway, the history is that our GHCs where bootstrapped from a 6.x or 7.x binary for a while. 4.x was added reletively recently.
<Christoph[m]>Is there no way to ask guix for packages that contain a given command? firstname.lastname@example.org asks for as, which I don't have in my profile, so there's no symlink to follow.
<jackhill>Christoph[m]: maybe someone can correct me, but I don't think that exists yet. With `as` you'd probably be fine poking around /gnu/store with find (althoguh maybe not efficiently), but in the general case you might want to find stuff that you don't have locally, so the ci server could build some sort of index. I think it's been discussed a number of times but not build.
<jackhill>Guix seems to be a little bit more fluid that e.g. debian which I suppose complicates the problem a little bit.
<jackhill>oh, interesting, but exit works if you don't ls first. My guess is that guix is looking at the exit code of the shell when it exits, and bash is massing on the command not found code from the ls try.
<jackhill>not 100% sure that's what's going on, but sounds good to me :)
<PaulePanter>Unrelated, so to manage different versions of the same package, it’s not so easy with guix either?
<PaulePanter>Our scientists would like to have access to different version of R, for example. Or would they just manage that using the right profile paths?
<civodul>PaulePanter: users can "pin" channels to a specific revision; so for instance, you could do "guix time-machine --branch=version-1.3.0 -- install r" to install the "old" R version, with its old dependencies
<MaNI>civodul, I did see that but as its a year old and theres a fix in the thread, and given I only installed today, I assumed that I must already have whatever fix that was (so presumably not the same issue)
<civodul>MaNI: yeah, it was apparently fixed before 1.3.0
<civodul>to be sure, could you try with the latest & greatest?
<civodul>like so: guix time-machine -- shell -C coreutils
<fiesh>hmm after a pull and system reconfigure, I now get like 20 to 30 "nothing to read on input" (or similar) messages instead of the password prompt for my luks home device
<allana>Hi #guix! Say that I am using a variant of python that I call python-alpha. Is there a nice way on the command-line to enter a guix shell like "guix shell python-alpha" with other python packages that use a graft to my python variant?
<zamfofex>Hello, Guix! At the expense of sounding repetitive, now that there are more people online, I wanted to ask once again about updating glibc. Here is some context: <https://logs.guix.gnu.org/guix/2022-04-08.log#060309> TL;DR: I wanted to help update glibc, but I’m afraid of starting the wrong way. Is it sufficient to update the package definition and submit a patch? How do I test whether it breaks too many packages?
<civodul>zamfofex: hi! testing 20K packages is not feasible, unless you have a build farm at home :-)
<civodul>but it'd be great if you could at least test core packages
<civodul>as in: ./pre-inst-env guix build coreutils grep sed guile
<zimoun>civodul, the cost of --with-c-toolchain=python=gcc-toolchain@7 is not the same as “build -m manifest.scm” where manifest contains the transformation. A different default? Or a bug between my chair and my keyboard?
<apteryx>civodul: well done for fixing the LUKS issue swiftly!
<civodul>zimoun: oh? i'd need more details, i'm not sure i understand
<kitzman>just so i make sure - i'm trying to provision a hurd VM with guix deploy (building stuff on a hurd VM is not feasible). the only way to do this would be to use another i586 vm running linux, right?
<zimoun>civodul: Using the manifest, it almost rebuilds the world. From the CLI, it seems doable. To be concrete, I did using CLI, done, then redid using manifest and… kill before the end. Maybe I am doingg something wrong, since the inspection is something, the first question is: is it the same default? (deep? etc.) I mean maybe it is well-known by it is the same default. :-)
***KimJongWell is now known as discoking
<civodul>zimoun: that sounds bad; but yes, there's a one-to-one mapping between the CLI and 'options->transformation'
<zimoun>civodul: let me check my next remote meeting. ;-) Ok, I will investigate more next week so.
<zimoun>ekaitz: Thanks! The best example ever I know about a really simple code using only integer and returning different values depending on the compiler version https://godbolt.org/z/PfYMje7ee Now the question, where do these binary compilers come from? :-)
<ekaitz>zimoun: the compilers come from the fairies of the forest
<ekaitz>they were created at the beginning of the times
<fiesh>(is there some nice way to git bisect the change that led to this?)
<zimoun>ekaitz: hehe! That’s just email@example.com fails on my machine and 4.7 is not available with Guix, for instance.
<ekaitz>zimoun: I opened an issue with that at Guix, they both exist. The 4.7 is a hidden package but you can unhide it using a manifest (LOL), but also fails. That happens (I think) because we updated the libc and those compilers are not compatible with our libc version.
<ekaitz>As I said, I added an issue, but nobody seemed to care about it :)
<civodul>mbakke: -O2 in nginx, well done! i think we've been unwillingly doing -O0 builds in a number of places...
<fiesh>hmm I'm baffled how hard this is... everything's git, but I can't manage to bisect. Is there no support for this at all?
<zamfofex>civodul: glibc 2.34 and 2.35 don’t include ‘libdl.so’ anymore, only an empty ‘libdl.a’ and an empty ‘libdl.so.2’, so building Bash fails with a missing ‘-ldl’. Should I make it create symlinks to the ‘.so.2’ file like there used to be, or should I instead ensure there is also a ‘.a’ file in the non‐‘static’ output too? (Likewise for the other now empty files too.)
<zamfofex>sneek: later tell civodul: glibc 2.34 and 2.35 don’t include ‘libdl.so’ anymore, only an empty ‘libdl.a’ and an empty ‘libdl.so.2’, so building Bash fails with a missing ‘-ldl’. Should I make it create symlinks to the ‘.so.2’ file like there used to be, or should I instead ensure there is also a ‘.a’ file in the non‐‘static’ output too? (Likewise for the other now empty files too.)
<zamfofex>fiesh: You could just clone the repository and verify the changes manually, though, no?
<mbakke>fiesh: there are ways to bisect, but not currently integrated with Guix
<mbakke>fiesh: you can use gits bisect machinery and do e.g. 'sudo -E ./pre-inst-env guix system reconfigure ...', or 'sudo guix time-machine --commit=$(git rev-parse HEAD) -- reconfigure ...' for each step
<fiesh>zamfofex: no I was talking about some actualy git bisect process integrated into guix
<fiesh>mbakke: ah ok, thanks.. where's this pre-inst-env?
<fiesh>mbakke: anyway, thank you for the short primer, my bisecting process is working smoothly albeit obviously slowly and tediously as is any manual bisect, and even worse one with the reboot of an actual hardware device
<Cassio>I'm about to try using `guix home`, but I need to understand something I couldn't sort out from the documentation. My home environment will set a new profile, appart form my user's `.guix-profile` or my home configuration becomes my default profile?
<bjc>from what i can tell, profiles and home environments coexist
<kitty2>its, kind of a shame there isn't more attention on projects outside of linux; wish BSDs, Hurd, and slightly less posix things like plan9 etc. had more attention lmao , suppose the BSDs are fairly used but sadly nothing guix/nix like on those yet as far as im aware...
<Guest28>civodul: how about implementing guix package -u --only-substitutes ? (similar to -no-substitutes) Would be useful for guix's version of an unattended-upgrades service. on help-guix there's a subject: "guix pull; guix package -u; sudo guix system reconfigure /etc/config.scm" which complains about 6hrs to complete.
<sneek>civodul, zamfofex says: glibc 2.34 and 2.35 don’t include ‘libdl.so’ anymore, only an empty ‘libdl.a’ and an empty ‘libdl.so.2’, so building Bash fails with a missing ‘-ldl’. Should I make it create symlinks to the ‘.so.2’ file like there used to be, or should I instead ensure there is also a ‘.a’ file in the non‐‘static’ output too? (Likewise for the other now empty files too.)
<Guest28>vagrantc: right. it shouldn't need to be that awkward is all Im saying.
<civodul>zamfofex: "everything" depends on -ldl; what is Bash specifically failing?
<zamfofex>civodul: It is failing because it is early on the bootstrapping process.
<civodul>still, you're saying there *is* libdl.so, right?
<alextee>btw I'm trying to update gtksourceview to version 5
<alextee>the current plain "gtksourceview" is on version 4
<PotentialUser-59>After my system shows the console welcome message and login, it takes 30 additional seconds before GDM starts. Is this a known issue? demesg does not have any relevant info. Is there a way I can get more logs out of shepherd?
<alextee>should I declare the package as gtksourceview-5?
<alextee>note that version 5 uses gtk4 and version 4 uses gtk3 so it should probably be a separate package
<zamfofex>Is it a library or an application? If it is an application, I’d imagine it’d be fine for the package name to stay the same.
<zamfofex>alextee: Note that you’ll eventually need to build Guix from source to be able to make and test changes to packages. Though it is easier to set up an environment to work on it once you already have it installed.
<alextee>I used to do that before but i forgot how
<zamfofex>civodul: I was able to build GNU Hello with the updated glibc! Now I’m trying coreutils and the other packages you asked for me to try out too.
<bjc>i'm running into an issue with ‘guix home reconfigure’: Cleaning up symlinks from previous home at /gnu/store/k9r1d...4knq-home.
<bjc>if i use ‘container’ instead of ‘reconfigure’ things start up fine
<bjc>i've tried rolling back to previous generations, and the roll-back is fine, but trying a subsequent reconfigure still fails
<bjc>the store directory exists, so i'm not sure what the problem is
<zamfofex>I’m not too familiar with ‘guix home’, so take my advice with a grain of salt, but do you have write permissions to the appropriate symlinks that it might be referring to? (I assume in ‘~/.guix-home’ or something.)
<bjc>on a somewhat related note: it'd be nice if the ‘--verbosity’ flag values were documented in ‘--help’
<zamfofex>(Or rather, to the directory the symlinks are in.)
<bjc>i don't know what symlink it's trying to deal with or clean up. and i can't figure out how to get that informatino
<bjc>however, i successfully ran a home reconfigure an hour or so ago after a pull. i only ran into this after adding a couple packages to my config
<bjc>(and yes, i put back the old config -- still broken)