From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 0fc2c4215737ee4baea98b871c517b6da0b46022
Date: Thu, 10 Sep 2026 20:08:51 +0000 (UTC) [thread overview]
Message-ID: <4hgpfC2pTcz2xYf@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 0fc2c4215737ee4baea98b871c517b6da0b46022 (commit)
via 5dbc14f22e2681337e19ab65ebf2cda8d8365d00 (commit)
from 998d47fd79879aa13918972ed5d7ecd184f58a7a (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 0fc2c4215737ee4baea98b871c517b6da0b46022
Author: Adolf Belka <adolf.belka@ipfire.org>
Date: Thu Sep 10 15:17:50 2026 +0200
core205: Ship suricata-reporter
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
commit 5dbc14f22e2681337e19ab65ebf2cda8d8365d00
Author: Adolf Belka <adolf.belka@ipfire.org>
Date: Thu Sep 10 15:17:51 2026 +0200
suricata-reporter: Fix Bug-14048 incorrect suricata-report-cron file used
- suricata-report-cron was created in August 2025 in the suricata-reporter package. After
this all updates were done in the suricata-report-cron placed in the config/suricata/
directory in the ipfire-2.x repo but that file was not copied across into the /usr/bin
directory
- This patch for the lfs file installs suricata-report-cron from the config/suricata/
directory.
- Confirmed by checking the file contents in the build directory and also by installing
the iso from the build.
Tested-by: Adolf Belka <adolf.belka@ipfire.org>
Fixes: Bug14048
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
.../rootfiles/{oldcore/198 => core/205}/filelists/suricata-reporter | 0
lfs/suricata-reporter | 5 ++++-
2 files changed, 4 insertions(+), 1 deletion(-)
copy config/rootfiles/{oldcore/198 => core/205}/filelists/suricata-reporter (100%)
Difference in files:
diff --git a/config/rootfiles/core/205/filelists/suricata-reporter b/config/rootfiles/core/205/filelists/suricata-reporter
new file mode 120000
index 000000000..23f2cd87d
--- /dev/null
+++ b/config/rootfiles/core/205/filelists/suricata-reporter
@@ -0,0 +1 @@
+../../../common/suricata-reporter
\ No newline at end of file
diff --git a/lfs/suricata-reporter b/lfs/suricata-reporter
index c56e0b5da..5f82a48e4 100644
--- a/lfs/suricata-reporter
+++ b/lfs/suricata-reporter
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2025 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2025-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 #
@@ -88,5 +88,8 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
/etc/suricata/reporter.conf
chown nobody:nobody /var/ipfire/suricata/reporter.conf
+ # Install suricata-report-cron file.
+ install -m 0644 $(DIR_SRC)/config/suricata/suricata-report-cron /usr/bin/suricata-report-cron
+
@rm -rf $(DIR_APP)
@$(POSTBUILD)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-09-10 20:08 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=4hgpfC2pTcz2xYf@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