From: Scott Murray <scott.murray@konsulko.com>
To: yocto-patches@lists.yoctoproject.org
Cc: marta.rybczynska@ygreky.com
Subject: [meta-security][PATCH 0/4] master-next updates
Date: Fri, 18 Jul 2025 10:10:55 -0400 [thread overview]
Message-ID: <cover.1752846514.git.scott.murray@konsulko.com> (raw)
Roll up the submissions since the first batch of whinlatter fixes,
plus an upgrade of scap-security-guide to get it building again
after the CMake 4.0 upgrade in oe-core.
A note about the ptest removal for scap-security-guide; while
having comprehensive ptests is desirable, from the commit history
it is clear that there was no interest in banging these ones into
a working state in the last couple of years. As well, ptests are
not enabled in most of the current CI build configurations, and it
seems clear that the build time hit would be massive in this case
if they were. If someone motivated to try to investigate resolving
these issues appears, this decision can be revisited.
Changes:
Clayton Casciato (1):
suricata: fix "interface" arg in systemd service
Haixiao Yan (1):
samhain: Adapt test output to Automake format for ptest compatibility
Scott Murray (1):
scap-security-guide: upgrade 0.1.76 -> 0.1.77
Yi Zhao (1):
scap-security-guide: disable ptest
.../scap-security-guide/files/run-ptest | 7 --
....1.76.bb => scap-security-guide_0.1.77.bb} | 54 +---------
...t-output-to-match-Automake-standards.patch | 102 ++++++++++++++++++
recipes-ids/samhain/samhain.inc | 1 +
recipes-ids/suricata/files/suricata.service | 2 +-
5 files changed, 106 insertions(+), 60 deletions(-)
delete mode 100644 recipes-compliance/scap-security-guide/files/run-ptest
rename recipes-compliance/scap-security-guide/{scap-security-guide_0.1.76.bb => scap-security-guide_0.1.77.bb} (50%)
create mode 100644 recipes-ids/samhain/files/0001-Format-test-output-to-match-Automake-standards.patch
--
2.50.0
next reply other threads:[~2025-07-18 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 14:10 Scott Murray [this message]
2025-07-18 14:10 ` [meta-security][PATCH 1/4] scap-security-guide: upgrade 0.1.76 -> 0.1.77 Scott Murray
2025-07-18 14:10 ` [meta-security][PATCH 2/4] scap-security-guide: disable ptest Scott Murray
2025-07-18 14:10 ` [meta-security][PATCH 3/4] suricata: fix "interface" arg in systemd service Scott Murray
2025-07-18 14:10 ` [meta-security][PATCH 4/4] samhain: Adapt test output to Automake format for ptest compatibility Scott Murray
2025-07-20 18:26 ` [yocto-patches] [meta-security][PATCH 0/4] master-next updates Marta Rybczynska
2025-07-21 17:10 ` Scott Murray
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=cover.1752846514.git.scott.murray@konsulko.com \
--to=scott.murray@konsulko.com \
--cc=marta.rybczynska@ygreky.com \
--cc=yocto-patches@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.