From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] logrotate: update to 3.19.0.
Date: Sat, 08 Jan 2022 07:42:57 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34936@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
There is a new pull request by Goorzhel against master on the void-packages repository
https://github.com/Goorzhel/void-packages logrotate
https://github.com/void-linux/void-packages/pull/34936
logrotate: update to 3.19.0.
#### Testing the changes
- I tested the changes in this PR: **briefly**
```
$ ./xbps-src pkg logrotate
$ xi !$
$ sudo logrotate -dv /etc/logrotate.conf
```
The above sequence of commands ran without error.
The [changelog](https://github.com/logrotate/logrotate/releases/tag/3.19.0) consists mostly of security fixes, the most interesting one being 427.
A patch file from https://github.com/void-linux/void-packages/pull/34936.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-logrotate-34936.patch --]
[-- Type: text/x-diff, Size: 1079 bytes --]
From 51379543721bc07c4f2a11608e4b76de0afe6626 Mon Sep 17 00:00:00 2001
From: Antonio Gurgel <antonio@goorzhel.com>
Date: Fri, 7 Jan 2022 22:34:03 -0800
Subject: [PATCH] logrotate: update to 3.19.0.
---
srcpkgs/logrotate/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/logrotate/template b/srcpkgs/logrotate/template
index 011beae16a99..b967dd87a21d 100644
--- a/srcpkgs/logrotate/template
+++ b/srcpkgs/logrotate/template
@@ -1,6 +1,6 @@
# Template file for 'logrotate'
pkgname=logrotate
-version=3.18.1
+version=3.19.0
revision=1
build_style=gnu-configure
makedepends="acl-devel popt-devel"
@@ -10,7 +10,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later"
homepage="https://github.com/logrotate/logrotate"
distfiles="${homepage}/releases/download/${version}/logrotate-${version}.tar.xz"
-checksum=14a924e4804b3974e85019a9f9352c2a69726702e6656155c48bcdeace68a5dc
+checksum=ddd5274d684c5c99ca724e8069329f343ebe376e07493d537d9effdc501214ba
make_dirs="/etc/logrotate.d 0755 root root"
post_install() {
next reply other threads:[~2022-01-08 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 6:42 Goorzhel [this message]
2022-01-08 21:48 ` [PR PATCH] [Merged]: " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34936@inbox.vuxu.org \
--to=goorzhel@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).