Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/chrony: bump to version 4.3
Date: Tue, 20 Sep 2022 21:20:16 +0200	[thread overview]
Message-ID: <20220920192016.GQ1419013@scaer> (raw)
In-Reply-To: <20220920190308.3688668-1-francois.perrad@gadz.org>

François, All,

On 2022-09-20 21:03 +0200, Francois Perrad spake thusly:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>

Applied to master, thanks.

Someone recently submitted a patch to fix our gpsd integration with
chrony:
    https://patchwork.ozlabs.org/project/buildroot/patch/8785_1663677905_6329B5D1_8785_15_1_b7ced13c9a2651fbf36d4009a03c0590457c82a3.1663677504.git.yann.morin@orange.com/

Presumably, since you updated chrony, that's because you use it. Do you
know what it would take to switch over to using the chrony upstream
systemd unit, rather than ours?

Could you have a look, please?

Regards,
Yann E. MORIN.

> ---
>  package/chrony/chrony.hash | 4 ++--
>  package/chrony/chrony.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/chrony/chrony.hash b/package/chrony/chrony.hash
> index 7fa67bf04..9c0e11757 100644
> --- a/package/chrony/chrony.hash
> +++ b/package/chrony/chrony.hash
> @@ -1,5 +1,5 @@
>  # Locally calculated after checking pgp signature
> -# https://download.tuxfamily.org/chrony/chrony-4.2-tar-gz-asc.txt
> -sha256  273f9fd15c328ed6f3a5f6ba6baec35a421a34a73bb725605329b1712048db9a  chrony-4.2.tar.gz
> +# https://download.tuxfamily.org/chrony/chrony-4.3-tar-gz-asc.txt
> +sha256  9d0da889a865f089a5a21610ffb6713e3c9438ce303a63b49c2fb6eaff5b8804  chrony-4.3.tar.gz
>  # Locally calculated
>  sha256  ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6  COPYING
> diff --git a/package/chrony/chrony.mk b/package/chrony/chrony.mk
> index 15b200aef..379e95a77 100644
> --- a/package/chrony/chrony.mk
> +++ b/package/chrony/chrony.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -CHRONY_VERSION = 4.2
> +CHRONY_VERSION = 4.3
>  CHRONY_SITE = http://download.tuxfamily.org/chrony
>  CHRONY_LICENSE = GPL-2.0
>  CHRONY_LICENSE_FILES = COPYING
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-09-20 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 19:03 [Buildroot] [PATCH] package/chrony: bump to version 4.3 Francois Perrad
2022-09-20 19:20 ` Yann E. MORIN [this message]

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=20220920192016.GQ1419013@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    --cc=fperrad@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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox