From: filiprojek <filiprojek@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] chrony: update to 4.4
Date: Sat, 26 Aug 2023 12:10:27 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45777@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
There is a new pull request by filiprojek against master on the void-packages repository
https://github.com/filiprojek/void-packages chrony
https://github.com/void-linux/void-packages/pull/45777
chrony: update to 4.4
tagging the maintainer @paper42
It's just a version bump
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures:
- x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/45777.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chrony-45777.patch --]
[-- Type: text/x-diff, Size: 1124 bytes --]
From d4c973f963caed7a654ec2e6d6bb53f05f114d78 Mon Sep 17 00:00:00 2001
From: Filip Rojek <filip@filiprojek.cz>
Date: Sat, 26 Aug 2023 12:01:39 +0200
Subject: [PATCH] chrony: update to 4.4
---
srcpkgs/chrony/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/chrony/template b/srcpkgs/chrony/template
index 758965f7bce25..9f2f9e72bd2c0 100644
--- a/srcpkgs/chrony/template
+++ b/srcpkgs/chrony/template
@@ -1,7 +1,7 @@
# Template file for 'chrony'
# When Updating: Please confirm the upstream config still refers to make_dirs
pkgname=chrony
-version=4.3
+version=4.4
revision=2
build_style=gnu-configure
configure_args="--without-nss --enable-scfilter
@@ -15,7 +15,7 @@ license="GPL-2.0-only"
homepage="https://chrony.tuxfamily.org/"
changelog="https://chrony.tuxfamily.org/news.html"
distfiles="https://download.tuxfamily.org/chrony/${pkgname}-${version}.tar.gz"
-checksum=9d0da889a865f089a5a21610ffb6713e3c9438ce303a63b49c2fb6eaff5b8804
+checksum=eafb07e6daf92b142200f478856dfed6efc9ea2d146eeded5edcb09b93127088
system_accounts="chrony"
chrony_homedir="/var/lib/chrony"
next reply other threads:[~2023-08-26 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 10:10 filiprojek [this message]
2023-08-26 10:14 ` [PR PATCH] [Updated] " filiprojek
2023-08-26 12:13 ` [PR REVIEW] " mhmdanas
2023-08-26 13:29 ` filiprojek
2023-09-05 19:30 ` [PR PATCH] [Merged]: " leahneukirchen
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45777@inbox.vuxu.org \
--to=filiprojek@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).