Ludovic Courtès writes:
> There’s a ledger for the Guix Europe non-profit¹, which is a separate
> entity, but most of the transactions on the funds held at the FSF have
> been made via Guix Europe. Another use of the FSF fund has been the
> Outreachy internship (that predates the recent donati
> Any other opinion?
I’d personally prefer if nss-certs were already available during
installation; but if not, having a link in “System Installation” to
instructions on how to safely install and set it up seems like a fair
compromise.
My 2¢.
swedebugia writes:
[...]
> Actually what is even nicer is emacs-debbugs and its ability to apply
> patches from emails. The UI is somewhat lacking and I think we should
> fork it so that it defaults to guix bugs and packages.
There's no need to fork emacs-debbugs for that; it's already
configur
Pierre Neidhardt writes:
>> Does this really need to have its own branch? I prefer to keep the
>> number of public branches on Savannah low.
>
> I can remove it any time. Is it really problematic?
I wouldn’t say “problematic”, but I think it’s nicer to only have public
branches for very larg
Hi Pierre,
guix-comm...@gnu.org writes:
> ambrevar pushed a commit to branch snapper
> in repository guix.
Does this really need to have its own branch? I prefer to keep the
number of public branches on Savannah low.
> commit b8413e5a3dc67eb064baf1a52fc34302c0a070c1
> Author: Pierre Neidhardt
Hi Joshua,
> As an aside, should Icecat be on this list?
This list is generated automatically. Icecat is a leaf package —
nothing else depends on it.
> I keep having to use "guix package
> --do-not-upgrade=icecat -u", because Icecat takes forever to build, and
> I'm not certain that I have en
Hi,
I think icecat is ok. I’m probably wrong about this but what I understand is
that icecat is being rebuilt after the rust bootstrap got merged. Upgrading
icecat now requires building several versions of the rust compiler. I hope a
substitute becomes available soon since it really does take a
Ludovic Courtès writes:
> Hello Guix!
>
> I’ve just added a new ‘--coverage’ option to ‘guix weather’. The goal
> is to answer the question: “which important packages fail to build?”, or
> at least, “which important packages have no substitutes?”. I believe
> this is what we want to know in par
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 German team of translators. The file is available at:
https://translationproject.org/latest/guix-manual/de.po
(We can arrange things
Pierre Neidhardt skrev: (25 januari 2019 23:22:47 CET)
>"The Perfect Setup" sounds a bit exclusive in my opinion, there is a
>whole world of
>possibilities out there... :)
Agreed. A recommended setup sounds better.
>
>That said, if it's only about Emacs+Geiser+Magit, I'd be happy to make
>a demo
Ricardo Wurmus skrev: (25 januari 2019 23:05:51 CET)
>
>Hi swedebugia,
>
> writes:
>
>> Yesterday when I played around with guix I noticed that the default
>> behavior of
>> $ guix package --search
>> guix package: error: invalid argument: Missing required argument
>after
>> `--search'
>>
>> has c
"Ludovic Courtès" skrev: (25 januari 2019 23:57:21 CET)
>Hi,
>
>Gábor Boskovits skribis:
>
>> swedebugia ezt írta (időpont: 2019. jan. 24.,
>> Cs, 23:04):
>>>
>>> On 2018-09-08 17:11, Christopher Lemmer Webber wrote:
>>> > Ludovic Courtès writes:
>>> >
>>> >> Thanks Mark for your time on the spe
12 matches
Mail list logo
