Hi all,
I saw this bug as I was updating WxMaxima today. It seems the issue is with
"filetype->GetOpenCommand()" function calls in src/wxMaxima.cpp (lines 3796 and
4078 specifically). These calls are used to find a browser that can open the
HTML help files. We could hard-code a browser (e.g.,
In Gnome clicking on the icon to configure the libpinyin input method
fails. It tries to execute ibus-libpinyin’s
libexec/ibus-setup-libpinyin.
Running it manually reveals this error:
--8<---cut here---start->8---
main2.py:66: DeprecationWarning:
This should be rather easy to fix:
--8<---cut here---start->8---
diff -r /gnu/store/3y97kfanv9ynxnahyykixchlbpbyvjmm-blast+-2.10.1-include
/gnu/store/3y97kfanv9ynxnahyykixchlbpbyvjmm-blast+-2.10.1-include-check
diff -r
Hello,
With Hydra, it is possible for a derivation to have the status of all
"still succeeding jobs", "newly failing jobs", "newly succeeding
jobs". In a word, have a quick overview of an evaluation status.
You can have a look to
https://hydra.nixos.org/jobset/nixos/release-19.09-small where
Am Dienstag, den 30.06.2020, 05:22 -0500 schrieb Nathan Dehnel:
> Thanks for the tip. Do I have to put the entire file inside a string
> in guix? It's quite long.
mixed-text-file allows you to split the string into multiple parts, but
that is essentially the idea, yes. There are of course other
When you search for something with DuckDuckGo, click on a result and
then click on your browsers back button you end up at DDGs start page
and not the results page.
1. Enter "guix" in your search/address bar while having DDG as default
search engine.
2. Click on first result -> guix.gnu.org
3.
Hi Ludo,
> The patch below is a noticeable improvement for me. On my laptop,
>
> GUIX_DAEMON_SOCKET=ssh://localhost ./pre-inst-env guix build libreoffice -n
>
> goes from 5.8s to 3.3s. It just does the same thing as we do for
> guix://.
>
> Could you check what results it gives you?
zimoun skribis:
> On Tue, 30 Jun 2020 at 00:20, Ludovic Courtès wrote:
>
>> The next commit also makes the closure of ‘gcc-toolchain’ much smaller,
>> bringing it to 350 MiB instead of 1 GiB.
>
> Wow! Awesome!
> This deserves a --news. :-)
It’s just that gcc-toolchain:out would pull in
