public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] logrotate: Update to 3.5.1
Date: Sun, 01 Sep 2019 13:34:06 +0100	[thread overview]
Message-ID: <F5D034FF-084A-4495-B841-095B0E6DC504@ipfire.org> (raw)
In-Reply-To: <20190901073726.31121-1-matthias.fischer@ipfire.org>

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

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 1 Sep 2019, at 08:37, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> For details see:
> https://github.com/logrotate/logrotate/releases
> 
> "use correct create mode in examples/btmp (#257)"
> => https://github.com/logrotate/logrotate/pull/257
> 
> "fix several bugs found by fuzzing (#254)"
> => https://github.com/logrotate/logrotate/issues/254
> 
> "do not abort globbing on a broken symlink (#251)"
> => https://github.com/logrotate/logrotate/issues/251
> 
> "rearrange logrotate.8 man page to improve readability (#248)"
> => https://github.com/logrotate/logrotate/pull/248
> 
> "encourage admins to use the su directive in logrotate.8 man page (#236)"
> => https://github.com/logrotate/logrotate/pull/236
> 
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/logrotate | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lfs/logrotate b/lfs/logrotate
> index 143d09531..5f7314bbd 100644
> --- a/lfs/logrotate
> +++ b/lfs/logrotate
> @@ -1,7 +1,7 @@
> ###############################################################################
> #                                                                             #
> # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2007-2018  IPFire Team  <info(a)ipfire.org>                     #
> +# Copyright (C) 2007-2019  IPFire Team  <info(a)ipfire.org>                     #
> #                                                                             #
> # This program is free software: you can redistribute it and/or modify        #
> # it under the terms of the GNU General Public License as published by        #
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 3.15.0
> +VER        = 3.15.1
> 
> THISAPP    = logrotate-$(VER)
> DL_FILE    = logrotate-$(VER).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = 240105d3288657d0ad7782c6a34c9a85
> +$(DL_FILE)_MD5 = 629cb3b933a281f25741e385bc030203
> 
> install : $(TARGET)
> 
> -- 
> 2.18.0
> 


      reply	other threads:[~2019-09-01 12:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-01  7:37 Matthias Fischer
2019-09-01 12:34 ` Michael Tremer [this message]

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=F5D034FF-084A-4495-B841-095B0E6DC504@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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