From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 34d72e754243fe86fb1772d39e1b45876b8c72f4
Date: Thu, 02 May 2019 18:36:52 +0100 [thread overview]
Message-ID: <20190502173653.4502484FDC8@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1698 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, master has been updated
via 34d72e754243fe86fb1772d39e1b45876b8c72f4 (commit)
from 0c52297641c96927eba3476851957ef0fe321ec8 (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 34d72e754243fe86fb1772d39e1b45876b8c72f4
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Wed May 1 20:19:01 2019 +0200
suricata: Update to 4.1.4
This is a minor update to the latest available version from
the suricata 4.1 series.
Fixes #12068.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/suricata | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/suricata b/lfs/suricata
index d7b5b71d6..310920606 100644
--- a/lfs/suricata
+++ b/lfs/suricata
@@ -24,7 +24,7 @@
include Config
-VER = 4.1.3
+VER = 4.1.4
THISAPP = suricata-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 35c4a8e6be3910831649a073950195df
+$(DL_FILE)_MD5 = cb8bf6b8330c44ae78dfb5b083a6fe82
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-05-02 17:36 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=20190502173653.4502484FDC8@people01.i.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