<CharlieBrown>mekeor: I made an exception for Jitsi's site in the LibreJS settings. When that didn't work, I disabled the LbireJS and SpyBlock addons. It still results in a Jitsi session that has unresonsive buttons and blank video boxes.
<CharlieBrown>mekeor: I also tried it in IceWeasel. It didn't work there, either.
<gazon>has anyone experienced a very long wait for make test in /tmp/guix-build-guile-ssh-0.9.0.drv-0/source/tests? it's been on tunnel.scm for several hours. doing a guix pull in a vm which was using guix 0.11.0.
<marusich>luser1, not sure...what exactly is a RAR file, anyway</
<marusich>The Wikipedia page says, "decompression source code is available, but it's not free software due to the restriction that it must not be used to reverse engineer the RAR compression algorithm"
<marusich>If that's true, then I don't think the tool will be included in a free software distribution like GuixSD.
<luser1>I don't expect a tool be included with Guix.
<marusich>I do not know of any tools which can decompress RAR files, myself
<lfam>I think the 'graphical?' toggle is pretty safe. At least, it's no worse than the current situation, where GuixSD's default GRUB menu doesn't show up on most of my installations :)
<lfam>On the other hand, myglc2's message makes me think that 'graphical?' is not going to be useful for servers
<lfam>The values that GRUB accepts for 'terminal_output', 'terminal_input', and 'serial' all seem to be defined in the GRUB manual. So we could abstract them. Validating them fully sounds tricky or maybe even impossible, although GRUB does provide a syntax-checking script we could use when building the new grub.cfg
<janneke>but cannot do it like that -- i cannot get `guix' to work in a guix build recipe
<janneke>i've spent all night to get i686-linux-gnu-gcc to work and finally have something working: with a hardcoded CROSS_LIBRARY_PATH
<reepca>Question(s) (and I'm sorta in a hurry, because I'm not sure when today the applications close - timezones and all that)... how integrated is the GSoC build tool supposed to be with guix? It says "by default runs inside the GNU Guix build system" (no mention of that at https://www.gnu.org/software/guix/manual/html_node/Build-Systems.html), and it also says "in time, we can target out of GNU Guix builds" and "we primarily target GNU Guix
<reepca>because Guix already solves the complexity of handling dependencies and software deployment". Is it talking about the package manager or the system there? I would assume the package manager, but how would such a build tool handle the stuff Guix solves without Guix?
<janneke>civodul: so i was now hoping to calculate the hardcoded library path
<janneke>we really need to just provide a i686-linux-gnu-toolchain package :-)
<reepca>I'm just not sure how much a person would be allowed to assume in developing said build tool if the goal is to eventually work without Guix (is that the goal?)
<rekado>the build tool was Pjotr’s idea, wasn’t it?
<rekado>I’m not really clear on what the goal there is.
<rekado>reepca: sorry, I can’t answer these questions.