From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 4/7] suricata: This package is supported on all architectures
Date: Wed, 24 Nov 2021 15:54:27 +0100 [thread overview]
Message-ID: <d6d9d8cec7185d6a6c57c7632301e262@ipfire.org> (raw)
In-Reply-To: <20211119174458.789486-4-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
Is rust now available on risc-v ?
You have introduces this.
Am 2021-11-19 18:44, schrieb Michael Tremer:
> There is no need to list them specifically.
>
> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
> ---
> lfs/suricata | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/lfs/suricata b/lfs/suricata
> index bd57b829e..0a1dcf2b8 100644
> --- a/lfs/suricata
> +++ b/lfs/suricata
> @@ -31,7 +31,6 @@ DL_FILE = $(THISAPP).tar.gz
> DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> -SUP_ARCH = x86_64 i586 aarch64 armv6l
>
>
> ###############################################################################
> # Top-level Rules
next prev parent reply other threads:[~2021-11-24 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 17:44 [PATCH 1/7] suricata: Include all default rules Michael Tremer
2021-11-19 17:44 ` [PATCH 2/7] rust: Drop Cargo home directory after build Michael Tremer
2021-11-19 17:44 ` [PATCH 3/7] suricata: Drop extra rootfiles Michael Tremer
2021-11-19 17:44 ` [PATCH 4/7] suricata: This package is supported on all architectures Michael Tremer
2021-11-24 14:54 ` Arne Fitzenreiter [this message]
2021-11-24 16:53 ` Michael Tremer
2021-11-19 17:44 ` [PATCH 5/7] suricata: Load *.config files from default location Michael Tremer
2021-11-22 4:21 ` Stefan Schantl
2021-11-22 9:52 ` Michael Tremer
2021-11-19 17:44 ` [PATCH 6/7] IPS: Do not try to show rules when stat on rules tarball fails Michael Tremer
2021-11-19 17:44 ` [PATCH 7/7] suricata: Handle retransmitted SYN with TSval 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=d6d9d8cec7185d6a6c57c7632301e262@ipfire.org \
--to=arne_f@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