From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of core162 (68b5761) for armv6l on arm64-01.dub.ipfire.org
Date: Mon, 20 Dec 2021 16:53:05 +0000 [thread overview]
Message-ID: <4JHlyT3DT3z1xYP@arm64-01.dub.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
https://nightly.ipfire.org/core162/2021-12-17%2008%3A06%3A26%20%2B0000-68b57610/armv6l
commit 68b57610898d586668b586e4a73db0cec98763f2
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Thu Dec 16 20:23:36 2021 +0100
suricata: Do not load rules for dnp3 and modbus.
The parsers for those are disabled in the suricata config so
the rules are not needed, on the contrary they massively will spam
warnings when launching suricate because of the disabled parsers.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=68b57610898d586668b586e4a73db0cec98763f2
Packaged toolchain compilation
Checking for necessary space on disk [ DONE ]
Building LFS
ERROR: No such file or directory: /build/nightly/core/stage2 [ FAIL ]
Check /build/nightly/core/log/_build.base.log for errors if applicable[ FAIL ]
reply other threads:[~2021-12-20 16:53 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=4JHlyT3DT3z1xYP@arm64-01.dub.ipfire.org \
--to=nightly-builds@ipfire.org \
--cc=nightly-builds@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