Hi,
Ludovic Courtès writes:
> Hi,
>
> (+Cc: Oleg, who worked on the Nix service.)
>
> Zhu Zihao via web skribis:
>
>> I found that if I put "sandbox = false" to /etc/nix/nix.conf. Nix can update
>> channel. Maybe nix's sandbox forget to import some guix binary path?
>
> Yes, probably. There’s
Hi,
> But I couldn't find any texlive package providing `l3regex.sty`.
> According to https://www.ctan.org/pkg/l3regex it should be included in
> `texlive-latex-l3kernel`.
>
> But something is wrong with the build:
> ```
> find $(guix build --source texlive-latex-l3kernel) -name "*regex*"
> /gnu
On 21.07.20 12:07, Ricardo Wurmus wrote: > Thanks for the report. Yes,
the “texlive-latex-l3kernel” package is
> incomplete. Most of the packages whose names follow the
> “texlive-{latex,tex,generic}-*” pattern are incomplete because they
> predate the introduction of “texlive-origin” (and more i
Dear,
On my laptop and my desktop, both “cat /proc/cpuinfo |grep processor|wc
-l” returning 4, and with 10 guixbuild users, I get these results.
On Thu, 16 Jul 2020 at 23:06, Maxim Cournoyer wrote:
> --8<---cut here---start->8---
> guix build --quiet --check
Jonathan Brielmaier writes:
> On 21.07.20 12:07, Ricardo Wurmus wrote: > Thanks for the report. Yes,
> the “texlive-latex-l3kernel” package is
>> incomplete. Most of the packages whose names follow the
>> “texlive-{latex,tex,generic}-*” pattern are incomplete because they
>> predate the intro
I'm glad to hear it. I'll close the bug.
On Tue, Jul 21, 2020 at 03:22:32AM -0500, Nathan Dehnel wrote:
> No, it's fixed.
>
> On Tue, Jul 21, 2020 at 1:58 AM Efraim Flashner wrote:
> >
> > On Tue, Jul 21, 2020 at 01:12:50AM -0500, Nathan Dehnel wrote:
> > > The patchbay in carla is completely un
Hi,
maxim.courno...@gmail.com skribis:
> The following C++ snippet file reproduces it:
>
> // file: test.cpp
>
> #include
> #include
>
>
> int main() {
> float x = 9.999;
>
> std::cout << "rounding value: " << x << " --> " << std::round(x);
>
> return 0;
> }
>
> // build with:
> //
Hi,
Leo Famulari skribis:
> Exporting a nar and importing it on another machine only works when the
> package being built has a single output.
Note that “guix archive --export foo” only exports foo:out. If you want
to export other outputs, you have to explicitly list them.
> I set up a signin
Hej Ludo,
I see that some time has passed and I believe that the issue can be closed.
Long story short, my hdd has died and I bought a new one and
re-installed. I could imagine that the errors I was running into were
related to the impending hardware failure -- that's a speculation,
though. A
On Tue, Jul 21, 2020 at 05:49:00PM +0200, Ludovic Courtès wrote:
> Hi,
>
> Leo Famulari skribis:
>
> > Exporting a nar and importing it on another machine only works when the
> > package being built has a single output.
>
> Note that “guix archive --export foo” only exports foo:out. If you wan
Hi!
zimoun skribis:
> On Mon, 20 Jul 2020 at 10:39, Ludovic Courtès wrote:
>> zimoun skribis:
>> > On Sat, 11 Jul 2020 at 17:50, Ludovic Courtès wrote:
>
>> There are many many comments in your message, so I took the liberty to
>> reply only to the essence of it. :-)
>
> Many comments becaus
Hi!
Oleg Pykhalov skribis:
> Ludovic Courtès writes:
>
>> Hi,
>>
>> (+Cc: Oleg, who worked on the Nix service.)
>>
>> Zhu Zihao via web skribis:
>>
>>> I found that if I put "sandbox = false" to /etc/nix/nix.conf. Nix can
>>> update channel. Maybe nix's sandbox forget to import some guix bina
Hi!
On Tue, 21 Jul 2020 at 23:22, Ludovic Courtès wrote:
>>> >> • If we no longer deal with tarballs but upstreams keep signing
>>> >> tarballs (not raw directory hashes), how can we authenticate our
>>> >> code after the fact?
>>> >
>>> > Does Guix automatically authenticate code usin
13 matches
Mail list logo
