From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Digest-SHA1: Update to 2.13
Date: Mon, 29 Jun 2020 17:45:27 +0100 [thread overview]
Message-ID: <34A0317F-23C6-46C0-9B9D-F75D1C5CA2F7@ipfire.org> (raw)
In-Reply-To: <20200629153708.2306-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2499 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 29 Jun 2020, at 16:37, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> For details see:
> https://metacpan.org/source/GAAS/Digest-SHA1-2.13/Changes
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> config/rootfiles/common/Digest-SHA1 | 1 -
> lfs/Digest-SHA1 | 6 +++---
> 2 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/config/rootfiles/common/Digest-SHA1 b/config/rootfiles/common/Digest-SHA1
> index 7aa9b362d..d01282eed 100644
> --- a/config/rootfiles/common/Digest-SHA1
> +++ b/config/rootfiles/common/Digest-SHA1
> @@ -3,6 +3,5 @@ usr/lib/perl5/site_perl/5.30.0/xxxMACHINExxx-linux-thread-multi/Digest/SHA1.pm
> #usr/lib/perl5/site_perl/5.30.0/xxxMACHINExxx-linux-thread-multi/auto/Digest
> #usr/lib/perl5/site_perl/5.30.0/xxxMACHINExxx-linux-thread-multi/auto/Digest/SHA1
> #usr/lib/perl5/site_perl/5.30.0/xxxMACHINExxx-linux-thread-multi/auto/Digest/SHA1/.packlist
> -#usr/lib/perl5/site_perl/5.30.0/xxxMACHINExxx-linux-thread-multi/auto/Digest/SHA1/SHA1.bs
> usr/lib/perl5/site_perl/5.30.0/xxxMACHINExxx-linux-thread-multi/auto/Digest/SHA1/SHA1.so
> #usr/share/man/man3/Digest::SHA1.3
> diff --git a/lfs/Digest-SHA1 b/lfs/Digest-SHA1
> index c1dfd7258..085fd2e6d 100644
> --- a/lfs/Digest-SHA1
> +++ b/lfs/Digest-SHA1
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2020 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 = 2.10
> +VER = 2.13
>
> THISAPP = Digest-SHA1-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = 4497a499b7c28ddd540a8caab412c6d7
> +$(DL_FILE)_MD5 = bd22388f268434f2b24f64e28bf1aa35
>
> install : $(TARGET)
>
> --
> 2.18.0
>
prev parent reply other threads:[~2020-06-29 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 15:37 Matthias Fischer
2020-06-29 16:45 ` 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=34A0317F-23C6-46C0-9B9D-F75D1C5CA2F7@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