Roman Penyaev

@eriknordmark If you don't have any objections, can we merge this? This simple "hack" reduces time of build-try-repeat kernel testing cycles from minutes to seconds and does not affect anything...

No progress on that. @eriknordmark can we close this with the "stalled" label?

@zedi-pramodh by any chance did you retest this PR? Do you plan to work on it? Or we can close it and reopen once again if there is a need.

Had the same issue. There are two problems here. **Problem one: different NRNG_NODES define for master/slave and tag targets** This output (which looks like a garbage to me btw: negative...

@eriknordmark now this one updates pillar to fscrypt with cross build. Let's give it a try.

Rebased on latest master. Once #3807 is merged, I will rework correct sha in this one.

@milan-zededa Milan, could you please review this. I also added the following patch: https://github.com/lf-edge/eve/pull/3808/commits/1b2f4fac127d04e5f9f5a015eb4f2de4b17dcc58 which fixes vendoring for the newlog, this repeats the kube/cnirpc line added in pillar/go.mod. I'm not...

> @rouming We will need to merge this first: #3839 Ok, now clean and tidy! Thanks.

> There are build errors of the form: #10 [build 5/6] RUN GO111MODULE=on CGO_ENABLED=0 go build -ldflags "-s -w -X=main.Version=v0.0.0-20240403104824-8a3f5c38d3cb " -mod=vendor -o /out/usr/bin/newlogd ./cmd #10 0.173 go: finding module...

It seems same error: ``` Error: error building "lfedge/eve-newlog:1c0af0a223bf3352fb0233bb8b0a029437098a48": error building for arch amd64: failed to solve: process "/bin/sh -c GO111MODULE=on CGO_ENABLED=0 go build -ldflags \"-s -w -X=main.Version=${GOPKGVERSION}\" -mod=vendor -o...