13 hours ago13 hr HelloBuilding an new image with KERNEL_CVE_PATCHES="yes" and the build fails with rejected when including two patches (attached in log files due to formatting). Is it common to run into these kind of problems with cve patches? Any custom workarounds to only ignore the failing patches?Testing a new build again with KERNEL_CVE_PATCHES="no" next, with the following but running into other errors :./compile.sh CLEAN_LEVEL=sources,cache,debs,make rm: cannot remove '/armbian/cache/sources/linux-kernel-worktree': Device or resource busy rm: cannot remove '/armbian/cache/sources/u-boot-worktree': Device or resource busy [|] Error 1 occurred in main shell [ at /armbian/lib/functions/general/cleaning.sh:43Thankspatch-failed.log.gz Edited 12 hours ago12 hr by Raul
9 hours ago9 hr 3 hours ago, Raul said:Is it common to run into these kind of problems with cve patches? Any custom workarounds to only ignore the failing patches?Here and there yes. Things can be improved system wise in two ways:clone https://github.com/armbian/cve repo and tell AI agent to contribute. It will fix failing patches and open a PR. This has to be done each time when things fails, best daily as its not just fixing broken patches but also backport new patches.wait. Automation or someone else will eventually fix it. I do it when this job fails https://github.com/armbian/ci/actions/workflows/build-all-stable.yml (currently disabled due to releasing images)Full API driven automation burns cash quick. Prepared but disabled.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.