public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Erik Kapfer <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] hyperscan: Update to version 5.2.1
Date: Wed, 22 Apr 2020 16:01:13 +0000	[thread overview]
Message-ID: <20200422160113.11991-1-ummeegge@ipfire.org> (raw)

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

Several bugfixes, improvements and extra detection has been added.
For the full changelog, take a look into here -->
https://github.com/intel/hyperscan/blob/master/CHANGELOG.md .

Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
---
 config/rootfiles/common/i586/hyperscan   | 4 ++--
 config/rootfiles/common/x86_64/hyperscan | 4 ++--
 lfs/hyperscan                            | 6 +++---
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/config/rootfiles/common/i586/hyperscan b/config/rootfiles/common/i586/hyperscan
index 3cec5c087..945c2b68c 100644
--- a/config/rootfiles/common/i586/hyperscan
+++ b/config/rootfiles/common/i586/hyperscan
@@ -5,10 +5,10 @@
 #usr/include/hs/hs_runtime.h
 #usr/lib/libhs.so
 usr/lib/libhs.so.5
-usr/lib/libhs.so.5.1.1
+usr/lib/libhs.so.5.2.1
 usr/lib/libhs_runtime.so
 usr/lib/libhs_runtime.so.5
-usr/lib/libhs_runtime.so.5.1.1
+usr/lib/libhs_runtime.so.5.2.1
 #usr/lib/pkgconfig/libhs.pc
 #usr/share/doc/hyperscan
 #usr/share/doc/hyperscan/examples
diff --git a/config/rootfiles/common/x86_64/hyperscan b/config/rootfiles/common/x86_64/hyperscan
index 3cec5c087..945c2b68c 100644
--- a/config/rootfiles/common/x86_64/hyperscan
+++ b/config/rootfiles/common/x86_64/hyperscan
@@ -5,10 +5,10 @@
 #usr/include/hs/hs_runtime.h
 #usr/lib/libhs.so
 usr/lib/libhs.so.5
-usr/lib/libhs.so.5.1.1
+usr/lib/libhs.so.5.2.1
 usr/lib/libhs_runtime.so
 usr/lib/libhs_runtime.so.5
-usr/lib/libhs_runtime.so.5.1.1
+usr/lib/libhs_runtime.so.5.2.1
 #usr/lib/pkgconfig/libhs.pc
 #usr/share/doc/hyperscan
 #usr/share/doc/hyperscan/examples
diff --git a/lfs/hyperscan b/lfs/hyperscan
index 45e57bc08..b63c6ecbe 100644
--- a/lfs/hyperscan
+++ b/lfs/hyperscan
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2019  IPFire Team  <info(a)ipfire.org>                     #
+# Copyright (C) 2007-2020  IPFire Team  <info(a)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        #
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 5.1.1
+VER        = 5.2.1
 
 THISAPP    = hyperscan-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -46,7 +46,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = 96f9cd558132dd65ec03648aaaba2a48
+$(DL_FILE)_MD5 = e722ec217282d38b1457cc751f0a4bb6
 
 install : $(TARGET)
 
-- 
2.20.1


             reply	other threads:[~2020-04-22 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 16:01 Erik Kapfer [this message]
2020-04-22 21:19 ` Michael Tremer

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=20200422160113.11991-1-ummeegge@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@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