From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] chrony: Version bump. 4.5 -> 4.6
Date: Wed, 4 Sep 2024 20:00:39 +0200 [thread overview]
Message-ID: <20240904180039.2611537-1-christian.melki@t2data.com> (raw)
Minor fixes and enhancements.
https://github.com/mlichvar/chrony/blob/4.6/NEWS
* Forward patch, applies cleanly.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
...001-configure-make-unrecognized-option-a-fatal-error.patch | 0
patches/{chrony-4.5 => chrony-4.6}/series | 0
rules/chrony.make | 4 ++--
3 files changed, 2 insertions(+), 2 deletions(-)
rename patches/{chrony-4.5 => chrony-4.6}/0001-configure-make-unrecognized-option-a-fatal-error.patch (100%)
rename patches/{chrony-4.5 => chrony-4.6}/series (100%)
diff --git a/patches/chrony-4.5/0001-configure-make-unrecognized-option-a-fatal-error.patch b/patches/chrony-4.6/0001-configure-make-unrecognized-option-a-fatal-error.patch
similarity index 100%
rename from patches/chrony-4.5/0001-configure-make-unrecognized-option-a-fatal-error.patch
rename to patches/chrony-4.6/0001-configure-make-unrecognized-option-a-fatal-error.patch
diff --git a/patches/chrony-4.5/series b/patches/chrony-4.6/series
similarity index 100%
rename from patches/chrony-4.5/series
rename to patches/chrony-4.6/series
diff --git a/rules/chrony.make b/rules/chrony.make
index 5b320d4a4..c3beabe05 100644
--- a/rules/chrony.make
+++ b/rules/chrony.make
@@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_CHRONY) += chrony
#
# Paths and names
#
-CHRONY_VERSION := 4.5
-CHRONY_MD5 := fa50d026df54f9919e6a37fae1258c61
+CHRONY_VERSION := 4.6
+CHRONY_MD5 := 847eb50fd67a85a9b16c4cf2cd584a29
CHRONY := chrony-$(CHRONY_VERSION)
CHRONY_SUFFIX := tar.gz
CHRONY_URL := https://chrony-project.org/releases/$(CHRONY).$(CHRONY_SUFFIX)
--
2.34.1
next reply other threads:[~2024-09-04 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 18:00 Christian Melki [this message]
2024-09-12 12:12 ` [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=20240904180039.2611537-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