From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] tshark: Update to version 3.2.3
Date: Mon, 11 May 2020 09:23:52 +0100 [thread overview]
Message-ID: <2108E7E5-E40C-4933-9860-F8DC9C8B71DA@ipfire.org> (raw)
In-Reply-To: <20200509060448.27760-1-ummeegge@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2322 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 9 May 2020, at 07:04, Erik Kapfer <ummeegge(a)ipfire.org> wrote:
>
> This update includes several bugfixes but also updated protocols.
> For a full overview, in here -->
> https://www.wireshark.org/docs/relnotes/wireshark-3.2.3.html the
> changelog can be found.
>
> Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
> ---
> config/rootfiles/packages/tshark | 5 +++--
> lfs/tshark | 6 +++---
> 2 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/config/rootfiles/packages/tshark b/config/rootfiles/packages/tshark
> index 4e262b5a7..5b7824a9f 100644
> --- a/config/rootfiles/packages/tshark
> +++ b/config/rootfiles/packages/tshark
> @@ -612,10 +612,10 @@ usr/bin/tshark
> #usr/include/wireshark/wsutil/xtea.h
> #usr/lib/libwireshark.so
> usr/lib/libwireshark.so.13
> -usr/lib/libwireshark.so.13.0.2
> +usr/lib/libwireshark.so.13.0.3
> #usr/lib/libwiretap.so
> usr/lib/libwiretap.so.10
> -usr/lib/libwiretap.so.10.0.2
> +usr/lib/libwiretap.so.10.0.3
> #usr/lib/libwsutil.so
> usr/lib/libwsutil.so.11
> usr/lib/libwsutil.so.11.0.0
> @@ -623,6 +623,7 @@ usr/lib/libwsutil.so.11.0.0
> #usr/lib/wireshark
> #usr/lib/wireshark/cmake
> #usr/lib/wireshark/cmake/FindGLIB2.cmake
> +#usr/lib/wireshark/cmake/FindWSLibrary.cmake
> #usr/lib/wireshark/cmake/FindWSWinLibs.cmake
> #usr/lib/wireshark/cmake/LocatePythonModule.cmake
> #usr/lib/wireshark/cmake/UseAsn2Wrs.cmake
> diff --git a/lfs/tshark b/lfs/tshark
> index b82b617c4..c32fb181e 100644
> --- a/lfs/tshark
> +++ b/lfs/tshark
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 3.2.2
> +VER = 3.2.3
>
> THISAPP = wireshark-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -33,7 +33,7 @@ DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = tshark
> DEPS = krb5
> -PAK_VER = 5
> +PAK_VER = 6
>
> ###############################################################################
> # Top-level Rules
> @@ -43,7 +43,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = e468b78e1176e0212b13ef809f59dcbb
> +$(DL_FILE)_MD5 = ff732e4586eebeb61a41abe2fcba7431
>
> install : $(TARGET)
>
> --
> 2.20.1
>
prev parent reply other threads:[~2020-05-11 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 6:04 Erik Kapfer
2020-05-11 8:23 ` 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=2108E7E5-E40C-4933-9860-F8DC9C8B71DA@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