From: Erik Kapfer <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] tshark: Update to version 3.0.5
Date: Fri, 04 Oct 2019 19:26:26 +0200 [thread overview]
Message-ID: <20191004172626.16828-1-ummeegge@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
The jump from 3.0.2 to 3.0.5 includes several bugfixes, updated protocols and new and updated capture support.
The complete release notes can be found in here --> https://www.wireshark.org/docs/relnotes/ .
Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
---
config/rootfiles/packages/tshark | 6 +++---
lfs/tshark | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/config/rootfiles/packages/tshark b/config/rootfiles/packages/tshark
index 816ab920b..dffd2a507 100644
--- a/config/rootfiles/packages/tshark
+++ b/config/rootfiles/packages/tshark
@@ -608,10 +608,10 @@ usr/bin/tshark
#usr/include/wireshark/wsutil/xtea.h
#usr/lib/libwireshark.so
usr/lib/libwireshark.so.12
-usr/lib/libwireshark.so.12.0.2
+usr/lib/libwireshark.so.12.0.5
#usr/lib/libwiretap.so
usr/lib/libwiretap.so.9
-usr/lib/libwiretap.so.9.0.2
+usr/lib/libwiretap.so.9.0.5
#usr/lib/libwscodecs.so
usr/lib/libwscodecs.so.2
usr/lib/libwscodecs.so.2.0.0
@@ -755,7 +755,7 @@ usr/share/wireshark/dtds/xcap-error.dtd
#usr/share/wireshark/help/capture_filters.txt
#usr/share/wireshark/help/capturing.txt
#usr/share/wireshark/help/display_filters.txt
-#usr/share/wireshark/help/faq.py
+#usr/share/wireshark/help/faq.txt
#usr/share/wireshark/help/getting_started.txt
#usr/share/wireshark/help/overview.txt
#usr/share/wireshark/help/toc
diff --git a/lfs/tshark b/lfs/tshark
index 562c70e26..7c9cd6613 100644
--- a/lfs/tshark
+++ b/lfs/tshark
@@ -24,7 +24,7 @@
include Config
-VER = 3.0.2
+VER = 3.0.5
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 = 2
+PAK_VER = 3
###############################################################################
# Top-level Rules
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = e344675283d6329a4bc213b621d7f46a
+$(DL_FILE)_MD5 = d01fdc4e78ef8ea70f20616c91419bd9
install : $(TARGET)
--
2.12.2
reply other threads:[~2019-10-04 17:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191004172626.16828-1-ummeegge@ipfire.org \
--to=ummeegge@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