From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] chrony: Version bump. 4.4 -> 4.5
Date: Thu, 7 Dec 2023 20:40:31 +0100 [thread overview]
Message-ID: <20231207194031.981319-1-christian.melki@t2data.com> (raw)
Various fixes.
https://github.com/mlichvar/chrony/compare/4.4...4.5
https://github.com/mlichvar/chrony/blob/4.5/NEWS
Chrony could do with a little bit of option polishing.
* Forward patch, fix offset. Applies ok.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
...001-configure-make-unrecognized-option-a-fatal-error.patch | 4 ++--
patches/{chrony-4.4 => chrony-4.5}/series | 0
rules/chrony.make | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
rename patches/{chrony-4.4 => chrony-4.5}/0001-configure-make-unrecognized-option-a-fatal-error.patch (89%)
rename patches/{chrony-4.4 => chrony-4.5}/series (100%)
diff --git a/patches/chrony-4.4/0001-configure-make-unrecognized-option-a-fatal-error.patch b/patches/chrony-4.5/0001-configure-make-unrecognized-option-a-fatal-error.patch
similarity index 89%
rename from patches/chrony-4.4/0001-configure-make-unrecognized-option-a-fatal-error.patch
rename to patches/chrony-4.5/0001-configure-make-unrecognized-option-a-fatal-error.patch
index 01f213633..c7b762015 100644
--- a/patches/chrony-4.4/0001-configure-make-unrecognized-option-a-fatal-error.patch
+++ b/patches/chrony-4.5/0001-configure-make-unrecognized-option-a-fatal-error.patch
@@ -12,10 +12,10 @@ Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
-index 323f5743cd57..080f7bce746d 100755
+index eefe5de82cb6..000021624709 100755
--- a/configure
+++ b/configure
-@@ -388,6 +388,7 @@ do
+@@ -410,6 +410,7 @@ do
;;
* )
echo "Unrecognized option : " $option
diff --git a/patches/chrony-4.4/series b/patches/chrony-4.5/series
similarity index 100%
rename from patches/chrony-4.4/series
rename to patches/chrony-4.5/series
diff --git a/rules/chrony.make b/rules/chrony.make
index b7e831eed..faa7e9a69 100644
--- a/rules/chrony.make
+++ b/rules/chrony.make
@@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_CHRONY) += chrony
#
# Paths and names
#
-CHRONY_VERSION := 4.4
-CHRONY_MD5 := f9876c57f9385c193c806ad8d5c6aec7
+CHRONY_VERSION := 4.5
+CHRONY_MD5 := fa50d026df54f9919e6a37fae1258c61
CHRONY := chrony-$(CHRONY_VERSION)
CHRONY_SUFFIX := tar.gz
CHRONY_URL := http://download.tuxfamily.org/chrony/$(CHRONY).$(CHRONY_SUFFIX)
--
2.34.1
next reply other threads:[~2023-12-07 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 19:40 Christian Melki [this message]
2023-12-13 7:47 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20231207194031.981319-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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