Hi George,
myg...@gmail.com skribis:
> In guix (GNU Guix) 0.14.0.4032-cfb55 the attached config no longer
> produces these errors, so I think this should be closed.
Thanks for the update, closing!
Ludo’.
myg...@gmail.com skribis:
> As of guix (GNU Guix) 0.14.0.4032-cfb55 I can't reproduce this, and
> haven't seen it since ~ when first reported, so I suggest it be
> closed. TIA - George
Great, thanks for the update.
myg...@gmail.com skribis:
> As of guix (GNU Guix) 0.14.0.4032-cfb55 I can't reproduce this so I
> suggest it be closed. TIA - George
Closing.
(Note: Just email nnn-d...@debbugs.gnu.org to close bug NNN.)
Thanks,
Ludo'.
Hi Leo,
Leo Famulari skribis:
> Since the update to Shepherd 0.4.0, I've found that OpenSSH's sshd is
> killed almost immediately after it starts with signal 15. I confirmed
> the issue started with the Shepherd upgrade by bisecting our Git
> history.
>
> I can reproduce the issue from commit
>
myg...@gmail.com writes:
> As of guix (GNU Guix) 0.14.0.4032-cfb55 I can't reproduce this so I
> suggest it be closed. TIA - George
Before we close it, could you try reproducing this with both "guix
system vm" and "guix system vm-image"? I recall that when I tried to
reproduce this problem, I wa
myg...@gmail.com writes:
> As of guix (GNU Guix) 0.14.0.4032-cfb55 I can't reproduce this, and
> haven't seen it since ~ when first reported, so I suggest it be
> closed. TIA - George
I'll close it now, then.
--
Chris
signature.asc
Description: PGP signature
On Fri, Apr 06, 2018 at 10:21:09AM +0200, Ludovic Courtès wrote:
[...]
> > Server listening on 0.0.0.0 port 22.
> > debug1: Bind to port 22 on ::.
> > Server listening on :: port 22.
> > Received signal 15; terminating.
> > --
>
> Hmm, where could that SIGTERM come from? ‘make-kill-destructor
Hello,
Martin Castillo skribis:
> guix build grep --no-substitutes -M 1 --verbosity=4 2>builderr
> # I aborted the first after a few seconds
You’re right about --verbosity=4 interrupting builds, I get:
--8<---cut here---start->8---
$ guix build --verbosity=4
Leo Famulari skribis:
> On Fri, Apr 06, 2018 at 10:21:09AM +0200, Ludovic Courtès wrote:
> [...]
>> > Server listening on 0.0.0.0 port 22.
>> > debug1: Bind to port 22 on ::.
>> > Server listening on :: port 22.
>> > Received signal 15; terminating.
>> > --
>>
>> Hmm, where could that SIGTER
Hi,
On 02.04.2018 23:48, Ludovic Courtès wrote:
> Hello Martin,
>
> As a foreword, note that ‘--verbosity’ is almost useless, even to Guix
> developers. I think we should hide it under a weird name, maybe
> ‘--daemon-debug’?
Ok.
>
> Your Raspberry will handle the build if and only if you’re r
On 04/06/2018 at 02:06 Chris Marusich writes:
> myg...@gmail.com writes:
>
>> As of guix (GNU Guix) 0.14.0.4032-cfb55 I can't reproduce this so I
>> suggest it be closed. TIA - George
>
> Before we close it, could you try reproducing this with both "guix
> system vm" and "guix system vm-image"?
Hello Guix
I have experienced some unexpected behaviour when running `guix build
lilypond':
After verifying that there was a substitute available with `guix weather
-m m.scm' (Where m.scm evaluates to a manifest containing only lilypond)
I ran `guix build lilypond --dry-run' which claimed that a s
On 05.04.2018 21:25, Alex Kost wrote:
It probably wouldn't help but... all these commands work for me without
any error (I use smartparens 1.11 installed with Guix).
I don't use "smartparens-mode", I use these commands directly (bound to
some keys). This is the configuration for smartparens I
13 matches
Mail list logo
