<catonano>mekeor Flattrr is launching an algorithm that should "understand" what ti is that you really want to contribute to on te basis of your browsing history. Because they realized that people don't want to manually manage flattrs
<catonano>mekeor but that requires a browser plugin
<catonano>Neither the current Icecat and theh Gnome Browser (I don't remember its name) are supported
<mekeor>the title part "is a symbol that specifies how the device field is to be interpreted."
<mekeor>"When it is the symbol device, then the device field is interpreted as a file name; when it is label, then device is interpreted as a partition label name; when it is uuid, device is interpreted as a partition unique identifier (UUID)."
<efraim>Maybe the tests will run o aarch64 this time
<bavier>the rationale given in the release announcement was "built-in suport for latex in html output", but I thought texinfo could do that too, but I might be mistaken
<bavier>I'd rather they had worked with texinfo devs to add support for that
<mekeor>i wonder why nobody seems to care about bugs #27425 and #27418 which make guix stuck at updating substitutes, i.e. it's an important error. – i mean, there've been no responses to the bug-reports.
<mekeor>koosha: it's a current bug, i'm also having problems with it
<koosha>Is the installation finished after that or I should run the "guix system init" again ?
<lambdatronic>Hi guys, is anyone having trouble with "guix system init"? After running it from the USB install image with my config.scm, I keep getting a grub-install error that's telling me the modinfo.sh is missing. When I check the directory it references, I can see that it, of course, doesn't exist. But it looks like it is trying to install to an EFI target when my system has a normal x86 BIOS. Help?
<bavier>koosha: you'll need to run 'guix system init' if it hasn't already succeeded.
<koosha>bavier: It returned me the message "substitute: updating list of ..." .
<bavier>koosha: hopefully this time it complete that substitute lookup and move on to installation
<janneke>rain1: got new set of non-Guix[SD] build up, if you'd want to check
<janneke>rain1: i was wondering even if you don't use GuixSD yet, [why] aren't you using guix on top of Arch?
<lambdatronic>Hi guys. I'd like to use GuixSD, but "guix system init" won't work for me. It runs for awhile installing packages onto my /mnt partition, but then it errors out at the grub-install stage, because it seems to think that my machine has an EFI boot setup, when it just has a normal ACPI BIOS. I tried running with --no-bootloader and then running grub-install manually with --target=i386-pc, but that errors out with complaints about
<lambdatronic>"unionfs". Does anyone know how to fix this problem? I'd really like to run GuixSD, but if the grub-install stage won't complete, I'm stuck.
<rain1>this is good! some tests failed but make check completed
<janneke>rain1: good news, thanks for checking this.
<janneke>rain1: the mes build system is currently terribly complicated. OriansJ wants to make that simpler at least for bootstrapping...
<janneke>the thing is: mes.c is a scheme interpreter
<janneke>that can be compiled with 1) CC: native gcc (usually x86_64), or 2) CC32 (usually i686-unknown-linux-gnu-gcc) without glibc, but using Mes's libc: mlibc, or 3) using Mescc: guile/mescc.scm run on Guile, or 4) using Mescc: scripts/mescc.mes run on mes
<janneke>4) is the final bootstrap path, but 1), 2) and 3) have been of great help using development
<bavier>civodul: there were some reports earlier about guix hanging when fetching substitute info from mirrors. Do you have any insights about that?
<reepca>Well, I'm just thinking, at the derivation-building level, there's no distinction between native, propagated, and normal inputs, right? So in copying stuff into the /gnu/store under the chroot, that means that if A is needed for building B, and B is needed for building C, A will need to be present along with B even though it's only needed for building. Is that right?
<janneke>i have found `guix system reconfigure' on a 0.13 vm to break on failing to download linux-libre-headers.