public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. fb7226d0a6fc9a762229bce0f4999995c4413679
Date: Sun, 29 Dec 2019 17:55:47 +0000	[thread overview]
Message-ID: <47m7X348sbz2xyk@people01.haj.ipfire.org> (raw)

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

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  fb7226d0a6fc9a762229bce0f4999995c4413679 (commit)
      from  424442d27da84d36d2670d0c554eae38b39338cb (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit fb7226d0a6fc9a762229bce0f4999995c4413679
Author: Erik Kapfer <ummeegge(a)ipfire.org>
Date:   Tue Dec 10 11:40:04 2019 +0100

    tshark: Update to version 3.0.7
    
    Several bugfixes are included in this version, some protocol support has been added.
    For a complete overview of the changelog, take a look in here -->
    https://www.wireshark.org/docs/relnotes/wireshark-3.0.6.html
    https://www.wireshark.org/docs/relnotes/wireshark-3.0.7.html .
    
    Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
    Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/packages/tshark | 4 ++--
 lfs/tshark                       | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

Difference in files:
diff --git a/config/rootfiles/packages/tshark b/config/rootfiles/packages/tshark
index 1e72493e9..b29a7c7b8 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.5
+usr/lib/libwireshark.so.12.0.7
 #usr/lib/libwiretap.so
 usr/lib/libwiretap.so.9
-usr/lib/libwiretap.so.9.0.5
+usr/lib/libwiretap.so.9.0.7
 #usr/lib/libwscodecs.so
 usr/lib/libwscodecs.so.2
 usr/lib/libwscodecs.so.2.0.0
diff --git a/lfs/tshark b/lfs/tshark
index 7c9cd6613..e8c63f3d8 100644
--- a/lfs/tshark
+++ b/lfs/tshark
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 3.0.5
+VER        = 3.0.7
 
 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    = 3
+PAK_VER    = 4
 
 ###############################################################################
 # Top-level Rules
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = d01fdc4e78ef8ea70f20616c91419bd9
+$(DL_FILE)_MD5 = 5b486f20239545c5af1db614c0d98876
 
 install : $(TARGET)
 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2019-12-29 17:55 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=47m7X348sbz2xyk@people01.haj.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@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