public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] suricata: Update to 4.0.6
Date: Sat, 23 Feb 2019 13:02:49 +0000	[thread overview]
Message-ID: <E0C8FA1D-938D-4DE1-8F38-14292C8465C1@ipfire.org> (raw)
In-Reply-To: <20190223093232.26433-1-stefan.schantl@ipfire.org>

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

Cool!

Thanks for working on IPFire 3.

How do we proceed from here? Packaging Rust in IPFire 3 should be possible without any bigger problems. Would you be up for doing this some time?

I think that we should port Suricata over to 3 just like we have it in 2 now. We do not necessarily need the latest release here, but eventually I would like to be able to be on the latest release.

-Michael

> On 23 Feb 2019, at 09:32, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> This is a major update to the latest 4.0 series which does not require rust.
> 
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> suricata/suricata.nm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/suricata/suricata.nm b/suricata/suricata.nm
> index f3fe7f44d..a74a50cdc 100644
> --- a/suricata/suricata.nm
> +++ b/suricata/suricata.nm
> @@ -4,7 +4,7 @@
> ###############################################################################
> 
> name       = suricata
> -version    = 3.2.1
> +version    = 4.0.6
> release    = 1
> 
> groups     = Networking/IDS
> -- 
> 2.20.1
> 


      reply	other threads:[~2019-02-23 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23  9:32 Stefan Schantl
2019-02-23 13:02 ` Michael Tremer [this message]

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=E0C8FA1D-938D-4DE1-8F38-14292C8465C1@ipfire.org \
    --to=michael.tremer@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