Hello Mark,
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
[...]
>> Lesson learned: we should not rely at all on generated patches because
>> they are bound to change frequently (version string at the end, length
>> of commit hash prefixes, etc.) It’s probably worse than
l...@gnu.org (Ludovic Courtès) writes:
> Maxim Cournoyer skribis:
>
l...@gnu.org (Ludovic Courtès) writes:
>>
>>>Lesson learned: we should not rely at all on generated patches because
>>>they are bound to change frequently (version string at the end, length
>>>of commit hash prefixes, etc.)
Hi Efraim,
guix-comm...@gnu.org writes:
> efraim pushed a commit to branch master
> in repository guix.
>
> commit 454e7132d6fffb5c9a5ce086ffd1b687416feb83
> Author: Efraim Flashner
> Date: Sat Dec 1 22:41:19 2018 +0200
>
> gnu: ocaml@4.01: Remove aarch64-linux from supported-systems.
>
Hi guix!
Thanks and please bear with my first ever mailing list post. I was trying to
package coin3d (https://bitbucket.org/Coin3D/coin/wiki/Home) as it is now under
a bsd3 license. The hash of the repo always changes. I think this is due to
the .hg files not being recursively deleted for
Hello,
Maxim Cournoyer skribis:
>>> l...@gnu.org (Ludovic Courtès) writes:
>
>>Lesson learned: we should not rely at all on generated patches because
>>they are bound to change frequently (version string at the end, length
>>of commit hash prefixes, etc.) It’s probably worse than tarballs
Ricardo Wurmus writes:
>> Overall I’m in favor of merging.
>
> I agree.
>
> I’ve been using core-updates on my laptop (both system and user profile)
> for about a week now without any problems.
Me too.
janneke
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'guix-manual' has been submitted
by the French team of translators. The file is available at:
https://translationproject.org/latest/guix-manual/fr.po
(We can arrange things
Hi,
> ‘core-updates’ seems to be in a rather good shape. […]
> On x86_64, LibreOffice, IceCat, etc. are available as substitutes; ‘guix
> weather’ reports only 50% of coverage on berlin and 80% on
> mirror.hydra.gnu.org (we’ll have to elucidate the bad number on berlin.)
> I’m using
Hi Eric,
Eric Bavier writes:
> On Fri, 30 Nov 2018 23:45:04 -0500
> Timothy Sample wrote:
>
>> Hello all,
>>
>> I just tried to build Guix from source and got an error:
>>
>> ERROR: no code for module (json)
>>
>> It looks like the new “swh.scm” module (which is really cool!) makes
>>
Hello Guix!
‘core-updates’ seems to be in a rather good shape. Unfortunately, the
web UI and APIs of hydra.gnu.org and berlin.guixsd.org make it difficult
to have a clear view of the situation.
“make assert-binaries-available” passes for all architectures, meaning
we have Emacs/X11 among other
Hi Laura,
Laura Lazzati writes:
[...]
> Yesterday I mentioned that I installed GuixSD on bare metal over IRC
> channel, in my retroPC that in December this year will be 13 years old
> :)
happy birthday retroPC! a teenager :-)
[...]
> The example for desktop.scm has the line:
> (device
On Fri, 30 Nov 2018 23:45:04 -0500
Timothy Sample wrote:
> Hello all,
>
> I just tried to build Guix from source and got an error:
>
> ERROR: no code for module (json)
>
> It looks like the new “swh.scm” module (which is really cool!) makes
> Guile-JSON a required dependency. I’m not
Timothy Sample writes:
If it is as new dependency, ya'll can use this texinfo patch that adds
guile-json as a dependency and alphabetizes the required packages:
Thanks,
Joshua
>From 2d860d1889b6c4bafe3d605ee47f9c93c3e91091 Mon Sep 17 00:00:00 2001
From: Joshua Branson
Date: Sat, 1 Dec 2018
Hi everyone :)
I have some questions as regards documentation:
Yesterday I mentioned that I installed GuixSD on bare metal over IRC
channel, in my retroPC that in December this year will be 13 years old
:)
I did a basic installation, almost followed the first example in:
14 matches
Mail list logo
