From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 32a07cec68d0bbb420524c193a46bbb7d6d6bb71
Date: Wed, 14 Jan 2026 11:18:08 +0000 (UTC) [thread overview]
Message-ID: <4drkB90RBqz2xtj@people01.haj.ipfire.org> (raw)
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 32a07cec68d0bbb420524c193a46bbb7d6d6bb71 (commit)
from 097038766be6a70b258a3cd67703d3b3b45f573f (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 32a07cec68d0bbb420524c193a46bbb7d6d6bb71
Author: Adolf Belka <adolf.belka@ipfire.org>
Date: Wed Jan 14 12:17:23 2026 +0100
tshark: Add libxxhash to dependency list
- From version 2.6.0 tshark added libxxhash as an option which is defined as ON by
default. As libxxhash is built as a dependency for rsync and borgbackup the tshark
build worked without problems but then the libxxhash library wass not present and so
tshark failed to run.
- This patch adds libxxhash to the dependency list for tshark
- No change to rootfile
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/tshark | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/tshark b/lfs/tshark
index 07cb1af8e..9ccfda104 100644
--- a/lfs/tshark
+++ b/lfs/tshark
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2025 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2007-2026 IPFire Team <info@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 #
@@ -34,8 +34,8 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = tshark
-DEPS = c-ares
-PAK_VER = 31
+DEPS = c-ares libxxhash
+PAK_VER = 32
SERVICES =
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-01-14 11:18 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=4drkB90RBqz2xtj@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