From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 40811ff383dc358e77afa9c482199336a4ffdca6
Date: Sun, 08 May 2022 09:01:59 +0000 [thread overview]
Message-ID: <4Kwywm1m89z2xgR@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1616 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 40811ff383dc358e77afa9c482199336a4ffdca6 (commit)
from 99a79bcbd89de07e108b836fe7d19bd26aeb02c3 (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 40811ff383dc358e77afa9c482199336a4ffdca6
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Sun May 8 09:01:24 2022 +0000
Suricata: Install Core Update 167 converter script
My fault, again. :-/
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/suricata | 3 +++
1 file changed, 3 insertions(+)
Difference in files:
diff --git a/lfs/suricata b/lfs/suricata
index fa7791cbe..1ebcb4ba4 100644
--- a/lfs/suricata
+++ b/lfs/suricata
@@ -131,5 +131,8 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
# Set correct ownership for /var/log/suricata.
chown suricata:suricata /var/log/suricata
+ # Install converter script needed for Core Update 167
+ install -m 0755 $(DIR_SRC)/config/suricata/convert-ids-backend-files /usr/sbin/convert-ids-backend-files
+
@rm -rf $(DIR_APP)
@$(POSTBUILD)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-05-08 9:01 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=4Kwywm1m89z2xgR@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