<raghav-gururajan>leoprikler Could you rephrase what you meant in a straight forward way please? I am not able to read between the lines,
<leoprikler>current evince does not build gi, so you have to patch that in addition to adding the actual package
<brettgilio>civodul: hey, in your email to bandali and I, are you wanting us to start designing the haunt page now (on a different host) and then move it to the dedicated Savannah repo once we have something, or wait for the Savannah repo and then begin working on it?
<pkill9>how is it preferred to send patches in email: as and attachment, as inline (e.g. a message above the patch), or the whole email being a patch (i.e. what git send-email does by default, with the email message in the patch below the "---" line)?
<oriansj>I thought guix was going to fall back to pulling from software heritage when downloaded source file's checksums fail; so we don't run into the same old issue of upstream changing the file without bumping the number and all of the guix builds failing
<seepel>I have come across another question, I am interested in installing Guix System on an old Macbook 2,1 which seems like it is pretty much fully supported by linux-libre. The problem I'm running into is that while it is a 64 bit machine, the UEFI firmware is 32 bit. I found some instructions for debian that I'm not really sure how to adapt: https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1. Does anyone know off hand an easy way
<str1ngs>seepel: maybe you can use refind to boot guix
<seepel>Ah interesting, I'll investigate. I notice the installer image creates four partitions, the first and last have type microsoft basic data, the second has type EFI, and the third has type HFS. I can't seem to mount the two microsoft basic data partitions, and I assume the HFS partition is the actual system. Is there someplace I could look to understand the boot process? Either the guix manual doesn't explain it, or I'm too dense and
<seepel>Yes the guix installer. I tried the 32 bit installer and unlike the 64 bit, grub managed to boot, but then it wouldn't boot complaining that it couldn't find bzImage.
<str1ngs>the basic boot process for EFI with guix is this. grub efi creates a boot entry for guix to EFI/Guix/grubx64.efi grub load grub config probably from the store. config has location for the linux kernel and initrd. initrd does some setup loading of modules pivot roots to the new root. and then hand off to shepherd . shepherd starts services etc etc
<str1ngs>seepel: maybe search to see if refind can maybe boot grub
<seepel>Just started reading up an refind, if I understand correctly refind is booted by the stock EFI firmware, and then refind in turn is used to boot the OS?
<str1ngs>or potentially there is a way to have refind boot guix but that alot of manual work
<str1ngs>refind is a bootloader same as grub. just it's kinda geared more for macs
<seepel>Ok, I'll read up and then either be back with the same question again, or a new question because it worked and I found something else I didn't understand :D
<seepel>Thanks for the pointers as always! Really psyched that folks here are so friendly.
<str1ngs>guix relieas on grub do to the dynamic location nature of where the kernel might be in the store.
<seepel>I _think_ if I could figure out how to combine the 32 bit grub with 64 bit system it would also suffice...
<str1ngs>one thing that might help is maybe install a foreign distro and see if you can workout boot process with that. they tend to be more static. that way you can resolved hardware/boot issues easier. after that you can use guix to install to a second partion and work through resolving boot issues using the bootable foreign distro
<str1ngs>give this expression (origin-uri (package-source gobject-introspection )) $2 = "mirror://gnome/sources/gobject-introspection/1.60/gobject-introspection-1.60.2.tar.xz" is there a guix help function to get the mirrored url?
<str1ngs>well this dirty hack did the trick I needed for now guix download $(guile -c "(use-modules (guix packages) (gnu packages glib)) (display (origin-uri (package-source gobject-introspection )))")
<lispmacs>I made a package definition for liquid-dsp, which installs. however, I realized that the liquid.h header file is getting placed into "include/liquid/liquid.h" rather than "include/liquid.h". How can I fix this?
<grillon>I have installed anthy ibus and ibus-anthy. I can select foreign keyboard but I do not see anthy in the list. in foreign distro when both are installed it works but on guix ibus-anthy seems not visible for ibus
<pkill9>i don't know if electron is built from source in any distro
<dadinn>I have a question regarding mapped devices: how do I add a key-file to a LUKS device? This is something I can add in a crypttab file, but there is no such field in the mapped-device data format
<nckx>You can provide this file with a single line in your system .scm, but TBH it's probably not worth it because you'll run into other missing library errors. Your best bet is to build the executable with Guix or to use patchelf on the one you have now.
<NieDzejkob>dadinn: That's currently on my TODO, I'm hoping to have this done sometime next week (together with extra-initrd like Nix for one-passphrase boot)
<oriansj>I use software (like guix) on my own terms; that is the advantage of free software. To use it however I see fit (and have the right for the community to call me a dumbass for doing something they think is stupid)
***apteryx_ is now known as apteryx
<lispmacs>autotools question: is there some easy built in way to have debugging flags when your run ./configure or make? Or do you ahve to program something like that into your configure.ac?
<mehlon>and instead of HTML we can use... a blockchain
<leoprikler>and we program everything using the blockchain programming language BCPL
<mehlon>we can also serve sites with a blockchain which runs on top of WebAssembly
<mehlon>... which is implemented on top of Ethereum
<oriansj>mehlon: requiring others to validate one's self is usually a sure sign that the person with that perspective doesn't have much going for themselves and they are just lashing out due to their own feelings of worthlessness
<mehlon>I'm guessing youre talking about the sonic image and not the IPFS thing
<drakonis>ehem, i have a bit of a problem here, i need to cook up my own guix install image
<nckx>oriansj: After decades of absence, wolves have returned to parts Belgium (which is good, mind you). Unfortunately they have developed a taste for kangaroo flesh. Every Belgian, simultaneously: wait why are there so many kangaroos here? Turns out there are, we just hadn't noticed the trend.
<nckx>What does this have to do with #guix? About as much as the past half hour, thank you.
<nckx>raghav-gururajan: At the Scheme level, no, because python-pygobject is just a Scheme variable bound to the older version in glib.scm. Guix doesn't do *any* version comparisons or ‘dependency resolution’. As to why python-pygobject points to an older version: that's unconventional, but probably happened to minimise the number of rebuilds (see ‘guix refresh -l firstname.lastname@example.org’ → staging material). BRB…