Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] chrony: update to 4.1.
Date: Thu, 20 May 2021 09:20:32 +0200	[thread overview]
Message-ID: <20210520072032.l7vxU7ldXQCWQYJTfIbN_8M28bWc2yIv2hFcz2qOe4I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30977@inbox.vuxu.org>

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

There is an updated pull request by paper42 against master on the void-packages repository

https://github.com/paper42/void-packages chrony-4.1
https://github.com/void-linux/void-packages/pull/30977

chrony: update to 4.1.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/30977.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chrony-4.1-30977.patch --]
[-- Type: text/x-diff, Size: 1522 bytes --]

From ee273304dbfe0af8d819f949a14ae962e2bc6b7d Mon Sep 17 00:00:00 2001
From: Paper <paper@tilde.institute>
Date: Tue, 18 May 2021 22:33:42 +0200
Subject: [PATCH] chrony: update to 4.1.

---
 srcpkgs/chrony/template | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/chrony/template b/srcpkgs/chrony/template
index 5341b533266c..6e1ee72a66a4 100644
--- a/srcpkgs/chrony/template
+++ b/srcpkgs/chrony/template
@@ -1,20 +1,21 @@
 # Template file for 'chrony'
 # When Updating: Please confirm the upstream config still refers to make_dirs
 pkgname=chrony
-version=4.0
-revision=2
+version=4.1
+revision=1
 build_style=gnu-configure
 configure_args="--without-nss --enable-scfilter
  --with-sendmail=/usr/bin/sendmail"
 hostmakedepends="pkg-config"
-makedepends="libcap-devel libedit-devel libseccomp-devel libtomcrypt-devel gnutls-devel"
+makedepends="libcap-devel libedit-devel libseccomp-devel nettle-devel gnutls-devel"
 conf_files="/etc/chrony.conf"
 short_desc="Versatile implementation of the Network Time Protocol (NTP)"
 maintainer="Anthony Iliopoulos <ailiop@altatus.com>"
 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=be27ea14c55e7a4434b2fa51d53018c7051c42fa6a3198c9aa6a1658bae0c625
+checksum=ed76f2d3f9347ac6221a91ad4bd553dd0565ac188cd7490d0801d08f7171164c
 system_accounts="chrony"
 chrony_homedir="/var/lib/chrony"
 

  parent reply	other threads:[~2021-05-20  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 21:36 [PR PATCH] " paper42
2021-05-19  0:13 ` ericonr
2021-05-19 23:16 ` ericonr
2021-05-20  7:20 ` paper42 [this message]
2021-05-21  4:30 ` [PR PATCH] [Closed]: " ericonr

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=20210520072032.l7vxU7ldXQCWQYJTfIbN_8M28bWc2yIv2hFcz2qOe4I@z \
    --to=paper42@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).