all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vitaliy Shatrov via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 43291@debbugs.gnu.org, Mike Rosset <mike.rosset@gmail.com>
Subject: bug#43291: ntp or nptd services on aarch64
Date: Wed, 16 Dec 2020 19:43:58 +0700	[thread overview]
Message-ID: <D4D22B32-F3F7-43C5-91FD-FEB746452F31@disroot.org> (raw)
In-Reply-To: <20200913195043.GA6116@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

Sorry, my installation now broken.
Also sorry for delay.
Was tweaking Guix and playing with sockets.

Cannot confirm, hope it is working.
Thank You, man.

On September 14, 2020 2:50:43 AM GMT+07:00, Leo Famulari <leo@famulari.name> wrote:
>On Wed, Sep 09, 2020 at 06:35:34PM +0700, Vtly Shtrv wrote:
>> Hello Guixen.
>> From the Guix System (aarch64) powering a RockPro64 SBC.
>> 
>> 
>> What's broken:  ntp-service-type
>>                 chrony
>>                 
>> How it's broken:
>> ntp-service-type segfaults (Mike seen).
>> chrony segfaults:
>
>I fixed a crash of Chrony and NTP with commit
>898fbb60b2354e82e5b7f259b44dbfed112a83aa.
>
>https://git.savannah.gnu.org/cgit/guix.git/commit/?id=898fbb60b2354e82e5b7f259b44dbfed112a83aa
>
>Can you check if it fixes this bug for you?

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 1389 bytes --]

  parent reply	other threads:[~2020-12-16 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 11:35 bug#43291: ntp or nptd services on aarch64 Vtly Shtrv
2020-09-13 19:50 ` Leo Famulari
2020-09-15  4:06   ` Vitaliy Shatrov
2020-12-16 12:43   ` Vitaliy Shatrov via Bug reports for GNU Guix [this message]
2020-12-16 18:25     ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D4D22B32-F3F7-43C5-91FD-FEB746452F31@disroot.org \
    --to=bug-guix@gnu.org \
    --cc=43291@debbugs.gnu.org \
    --cc=guix.vits@disroot.org \
    --cc=leo@famulari.name \
    --cc=mike.rosset@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.