<tschilptschilp23>I liked the old version too, but with the new one I tend to remember the news better. But I really like to chop things into steps and in the meantime (thanks to the person who told me here about it) also run ~guix weather~ before reconfiguring, as some bigger packages toast my laptop without substitutes being ready...
<tschilptschilp23>0x151: I had some troubles with it too -- where did you install pinentry (home-config, system-config, or ~guix install~)? I have it in the system's package list now, pinentry only though (although running gnome), and it does nicely without any .conf!
<Ox151>tschilptschilp23: i installed with "guix package -i" so i guess guix install
<Ox151>anyone know a good default font for odd symbols such has different type bar characters? eg | _ -, but the odd ones out
<Ox151>I guess ill try gnu-unifont, supposedly has good unicode support
***the-porcupirate is now known as porcupirate
<Syboxez[m]>Hey. New to GUIX here and got a couple of questions. 1: Do flatpaks work? Second, do locally compiled applocations have any issues, and how do dependencies for those work? Is there a Bash environment that's sandboxed in a GUIX package, or will I still have access to all my libs?
***sneek_ is now known as sneek
<user_oreloznog>Syboxez(m]: Hi! You can install flaptalk like this : $ guix install flatpak
<MysteriousSilver>it would be much easier to compile them with guix than to do it manually
<lilyp>Syboxez[m]: See `guix shell' for clean development environments. It is not recommended to install your usual dev tools (GCC, Python, npm, even Guile libraries most of the time) in the user profile.
<attila_lendvai>i'm doing a repeated `guix system reconfigure` after a `guix gc`, with practically the same config and without pulling, and there are a lot of substitutes being downloaded, including stuff that i think shouldn't be. am i missing something, or did the gc delete stuff over-zeaously?
<attila_lendvai>hrm, my channels.scm is bound to my local checkout, but i did not pull from it.
<nouun>Is there a way to insert text into a file in a build phase? (invoke "echo" "test" ">>" "test") just prints because it isn't being interpreted by a shell.
<Lumine>Yeah it happens that it deletes a whole lot of packages even needed ones if you don't specify the options, I had 80 GB freed with gc on my previous setup and I had basically everything being installed back when I did a reconfigure.
<tschilptschilp23>lilyp: your hint from above somehow triggered my 'what to put where' thoughts... do I get you right, that you basically suggest not installing these packages anywhere (neither system nor home)?
<lilyp>tschilptschilp23: which packages in particular? Guile always exists on behalf of it being the Guix hacking language, but othre than that using them in your profile is inviting trouble
<tschilptschilp23>lilyp: what comes to my mind would be packages like python, python-beautifulsoup, python-requests
<lilyp>yep, that's guix shell -D guix.scm material
<lilyp>though perhaps that also depends a little on how well organized your personal scripts are
<tschilptschilp23>cool, thank you! I think it's OK at the moment. Cleaning my home right now, and backpropping GUIs of daily usage to the system-config right now ;)
<lilyp>if you have a Makefile defining generic utility procedures that you need to... idk, fetch some manga over the web and read it, a dirty home will be the consequence
<yarl>This is not strictly related to guix but maybe someone had this issue already. In 18.3 The Perfect Setup of the guix manual, geiser is recommended. I managed to have geiser-edit-symbol at point and geiser-pop-symbol-stack working, which is very useful to browse the source. But I can't get geiser-xref-callees/callers to work.
<tschilptschilp23>whelutyk: I followed civodul's and your discussion yesterday and didn't quite get, where to place inputs in your image-build-config -- but maybe this goes in a similar direction? Like putting pkg-config to the inputs. I hope I'm not bloating things here, just saying, because I think pkg-config does not necessarily get autoloaded...
<yarl>janneke I don't know if that's relevant but guix environment is deprecated according to the manual and the help subcommand
<tschilptschilp23>but I do not have experience with cross-compiling, so maybe someone with could jump in...
<yarl>Do someone here uses emacs+geiser+guile and can use geiser-xref-callees or geiser-xref-callers?
<wehlutyk[m]>tschilptschilp23: thanks! Yes, given civodul's answer yesterday, adding pkg-config to inputs was the first thing I tried and it doesn't change the error
<wehlutyk[m]>actually, pkg-config is currently in `native-inputs`, but the version that appears in the `environment-variables` file of the tmp build folder is the aarch64 one (so it makes sense that the pkg-config for the host machine is not found). I just don't see why pkg-config in native-inputs leads to the aarch64 pkg-config appearing in environment-variables.
<bost>According to the guix.gnu.org the GuixOS proudly claims to be the in version 1.3.0. So, is there any command which returns such a version number? Like e.g. `lsb_release` under Ubuntu? And since we've rolling release, does such a version number have any meaning at all?
<jpoiret>because guix is rolling release, almost all users (all hopefully) run not on 1.3.0 but on the latest master branch
<jpoiret>you could consider point versions as "good snapshots" of Guix
<jpoiret>at the same time, guix search gcc should be enough
<nckx>Not to be facetious, but 'so should guix install gcc' perhaps? Defence of hiding gcc was 'user friendliness'. Current status quo not *that* user-friendly, regular IRC reports suggest.
<tschilptschilp23>reading about encryption above -- any hints where would I have to start to decrypt my system via usb-stick or sd-card during boot? my system is luks encrypted, and so is my home-directory, which is on an external usb-drive. This results in me having to type passwords 4 times, which is OK as I don't reboot very often, but could need some optimization. I had a usb-stick version a while ago on a debian system, but lost my notes. And I
<tschilptschilp23>suppose it will work a little different here too, so I don't cry after it.
<jpoiret>unfortunately, no, touching the system config won't be enough
<jpoiret>you'd need to modify things in gnu/build/linux-boot.scm iirc
<tschilptschilp23>OK, I will look there. If I'm offline for the next two weeks, you know what happened ;)
<tschilptschilp23>Argh. This starts way earlier... would I have to do this at pre-install-time? I cannot see any gnu/build directory on my system. Well yes, on my local checkout, but not on the one I'm running right now...
<jpoiret>tschilptschilp23: what I was saying was that you need to modify guix's source code
<jpoiret>no, yes, you'd need a local checkout on which you would make changes, and use that patched guix for your system
<jpoiret>so the behaviour is pretty non-customizable regarding that
<unmatched-paren>tschilptschilp23: pretty sure that if you mess your initrd up you can just roll back in grub to the previous system generation (after making modifications and guix pulling from your local checkout)...?
<jpoiret>that's right, as long as you don't touch bootloader stuff you should be safe
<unmatched-paren>you should be able to set the `guix` channel to a local checkout, right?
<jpoiret>unmatched-paren: yes, but the easiest way to test is to use ./pre-inst-env, since guix pull'ing will be pretty slow
<tschilptschilp23>i don't think my grub itself is encrypted -- guix just wants me to enter passwords to decrypt the root filesystem (and also for the external usb), before I get to the grub splash screen. how this all goes into each other is very much opaque to me...
<jpoiret>but, in any case, grub needs to see the store to load the kernel and initrd, and so may need to unlock a LUKS device, and I'm not sure you can use a usb key with a keyfile for that
<jpoiret>tschilptschilp23: well, that's actually GRUB asking you that, to be able to read its configuration files/the kernel and initrd
<jpoiret>if your /boot is encrypted, GRUB still wants to read /boot/grub/grub.cfg for example
<unfroq>tschilptschilp23: Even though, I think it would be aweseome, if you would find a way to solve the problem by patching guix, you could also think about alternative solutions: Depending on your requirements, you could also try to boot an unencrypted system with a ssh-server available. Then you could SSH into it and mount an encrypted home or other encrypted devices. That way, you could also solve the grub password issue.
<tschilptschilp23>jpoiret: right, this makes sense. I was wondering about this behaviour already for a while now...
<tschilptschilp23>i just checked, it's really weird -- ~/boot/efi~ (I *think* I'm booting from that one) is on an unencrypted partition, ~/~ is encrypted, therefore ~/boot/grub~ will be as well
<nckx>By the most bizarre coincidence I just logced on. Yes?
<nckx>Did you ask a question earlier? I can't find one, or I forgot, sorry. Away again for now.
<jpoiret>unmatched-paren, tschilptschilp23: tbh it's common to have /boot on /
<jpoiret>Mine is on my EFI partition, but seeing how many people had the luks2 bug i'd say the former occurs more often
<tschilptschilp23>here I have ~/dev/sda1~ on ~/boot/efi~ and the (encrypted) ~/dev/sda2~ on ~/~, ~/var/lib/docker~, and ~/gnu/store~. I did not really put hand on this, for convenience I use the graphical live installer, and then reconfigure with my home-config and system-config
<tschilptschilp23>well, I have to adapt the uuids to get things right, but I can live with that, as I don't do this often
<tschilptschilp23>I could cry though, that we don't have (or I don't get what represents it) an ~/etc/crypttab~ and that mysterious ~/lib/cryptsetup/scripts/passdev~... the mapped-devices section in the system-config /must/ (?) set up something like this, but I cannot find how and where...
<tschilptschilp23>I mean the mapped-device section in combination with the file-systems section...
<old>Anybody has problems with `run-geiser` recently? After some recent update, I get `geiser-repl-project-root: Symbol’s function definition is void: project-root` and the REPL is never spawned :/
<jab>old: I used run-geiser this morning...but I was using doom-emacs's provided package from github....
<jab>I have had some weird issues, where the geiser process can lock up...and it makes emacs almost unuseable...