Hi!
Hope to shed some light.
I followed all the steps that I hadn't followed before in the
documentation manual about SELinux for guix daemon (ran semodule,
restorecon for all the filesystem and restarted the daemon).
I forgot to set SELinux in permissive mode, so I still got the issue
with the
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
Ludovic Courtès writes:
> Hi Marius,
>
> Marius Bakke skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> The issue that Tobias reports reminds me of the CPATH vs. C_INCLUDE_PATH
>>> issue that was causing troubles with newer GCCs, and that I think Marius
>>> addressed in ‘core-updates’ (?).
Hi Laura,
>> Thanks. Did you install the SELinux policy for the daemon that is
>> included in the source code repository? (It is not included in the
>> files that “guix pull” installs.)
> My bad, I haven 't :/ Shall I put SELinux in enforcing mode and do so?
Permissive mode is better. It
Pierre Neidhardt writes:
>> I was thinking of the Guix package definitions. In the long run,
>> assuming IPFS turns out to be reliable enough, we could put all source
>> into IPFS with a CID reference, rather then today's many ways to
>> download source files.
>
> There would be nothing special
Hi!
> Thanks. Did you install the SELinux policy for the daemon that is
> included in the source code repository? (It is not included in the
> files that “guix pull” installs.)
My bad, I haven 't :/ Shall I put SELinux in enforcing mode and do so?
Regards :)
Laura
Hi!
> Thank you Laura for continuously caring about the videos even after
> your internship ended!
Of course Bruno :) I said I would go on as a contributor and here I am ;)
Alles gute!
Laura
Konrad Hinsen writes:
> I was thinking of the Guix package definitions. In the long run,
> assuming IPFS turns out to be reliable enough, we could put all source
> into IPFS with a CID reference, rather then today's many ways to
> download source files.
There would be nothing special about it
Pierre Neidhardt writes:
>> - A unified way to refer to stuff (I am thinking of IPLD here)
>> No more tarballs, git commits, etc. CIDs everywhere.
>
> Do you have a concrete use case?
I was thinking of the Guix package definitions. In the long run,
assuming IPFS turns out to
On 6/6/19 12:37 PM, n...@n0.is wrote:
> Jonathan Brielmaier transcribed 93K bytes:
>> Hi fellow Guix hackers,
>>
>> the last weekend I tried to install Guix system on the Hetzner Cloud[0].
>> First I tried to use Ubuntu, install Guix with the installer script and
>> then initiate Guix with "guix
Jonathan Brielmaier transcribed 93K bytes:
> Hi fellow Guix hackers,
>
> the last weekend I tried to install Guix system on the Hetzner Cloud[0].
> First I tried to use Ubuntu, install Guix with the installer script and
> then initiate Guix with "guix system init /mnt...". This wasn't
>
Hello Björn,
> For the code I would suggest GPL v3+, for the voices (currently Paul)
> and videos I would suggest CC-BY-SA 4.0
>
> What do you think? Does every contributor agree to that?
That looks good to me.
For the source code we could add copyright statements at the top of the
files in
I've switched to it yesterday and since then it seems I have to compile
everything myself :(
Subversion, git, boost, to name a few.
I do get the source from qualif.ci.guix.gnu.org though:
--8<---cut here---start->8---
downloading from
On Thu, May 09, 2019 at 06:08:46PM +0300, Pavel Maryanov wrote:
> Ludovic, unfortunately Russian translation "Keyboard Layout and Networking
> and Partitioning" have to contain comma because of two 'and'. It is a rule
> of Russian language.
>
It appears you can write “@comma{}” instead of “,”
14 matches
Mail list logo
