From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libpcap: Update to 1.10.3
Date: Wed, 18 Jan 2023 23:16:49 +0000 [thread overview]
Message-ID: <7d8e6920-bbe0-780a-4412-d2d39bcd0738@ipfire.org> (raw)
In-Reply-To: <20230114144124.3600330-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> For deails see:
> https://git.tcpdump.org/libpcap/blob/HEAD:/CHANGES#43
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> config/rootfiles/common/libpcap | 2 +-
> lfs/libpcap | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/config/rootfiles/common/libpcap b/config/rootfiles/common/libpcap
> index a3f71b3e6..2371b4601 100644
> --- a/config/rootfiles/common/libpcap
> +++ b/config/rootfiles/common/libpcap
> @@ -22,7 +22,7 @@
> #usr/lib/libpcap.a
> usr/lib/libpcap.so
> usr/lib/libpcap.so.1
> -usr/lib/libpcap.so.1.10.2
> +usr/lib/libpcap.so.1.10.3
> #usr/lib/pkgconfig/libpcap.pc
> #usr/share/man/man1/pcap-config.1
> #usr/share/man/man3/pcap.3pcap
> diff --git a/lfs/libpcap b/lfs/libpcap
> index 5293a5a0c..3f1de9b5a 100644
> --- a/lfs/libpcap
> +++ b/lfs/libpcap
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 1.10.2
> +VER = 1.10.3
>
> THISAPP = libpcap-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -42,7 +42,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = f8280c8e12065b4d86e451df8504c834da9c94b25029f0e5c22359d0ce35cf4e3490fa3343d0112209600ea01ffa54249c82c20e2859515884daee759e4a5e9b
> +$(DL_FILE)_BLAKE2 = 3614042f7d8cd5a25221f52d2ed09f9f44643cdc0901ff21041ddb7ba85193c667036f7d989c8b59e6e205d630e062da46533110914dd287013a9ff80b31e97f
>
> install : $(TARGET)
>
prev parent reply other threads:[~2023-01-18 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 14:41 Matthias Fischer
2023-01-18 23:16 ` Peter Müller [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=7d8e6920-bbe0-780a-4412-d2d39bcd0738@ipfire.org \
--to=peter.mueller@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