Message ID | cover.1755464538.git.scott.murray@konsulko.com |
---|---|
Headers | show |
Series | Assorted fixes | expand |
On Mon, 18 Aug 2025, Marta Rybczynska (Ygreky) wrote: > > On 17/08/2025 11:07 PM, Scott Murray wrote: > > A variety of fixes for enabling CI against the walnascar branch and fixing > > outstanding build issues, plus a bump of scap-security-guide to its latest > > version to match master brnach since the changes are minimal. > > > > I intent to merge these to walnascar branch in the next day or so if there > > are no objections. > > > > Changes: > > > > Anton Antonov (1): > > parsec-service: update PACKAGECONFIG options as lists of cargo build > > features > > > > Marta Rybczynska (5): > > scap-security-guide: fix fetch > > CI: update build for new CI > > .gitlab-ci.yml: add logging of jobs to files > > gitlab-ci.yml: fix file redirection for qemux86 build logs > > checksecurity: update the debian package > > > > Scott Murray (1): > > scap-security-guide: upgrade 0.1.76 -> 0.1.77 > > > > .gitlab-ci.yml | 45 +++++++++++-------- > > .../checksecurity/checksecurity_2.0.16.bb | 7 ++- > > meta-parsec/README.md | 4 +- > > .../parsec-service/parsec-service_1.4.1.bb | 15 +++---- > > ....1.76.bb => scap-security-guide_0.1.77.bb} | 4 +- > > 5 files changed, 39 insertions(+), 36 deletions(-) > > rename > > recipes-compliance/scap-security-guide/{scap-security-guide_0.1.76.bb => > > scap-security-guide_0.1.77.bb} (95%) > > > > Good idea to backport those. I'll run a walnascar branch CI to make sure, but > I expect no surprises. I've gone ahead and merged these to the walnascar branch to unblock anyone needing checksecurity or scap-security-guide. There's still a branch-specific patch to the CI configuration outstanding to make running it against walnascar straightforward, but I have smoke tested most of the build configurations locally with gitlab-ci-local. Scott