lists.yoctoproject.org wrote: I think there is a regression somewhere: https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/2085/steps/29/logs/stdio Cheers, Richard

I saw you're still having problems even with the latest pseudo revisions. I'll make some comments below. This is saying the file on disk with inode 7868999 is: WORKDIR/lib32-las/M-WBS0.1-r0/git/lasifl

Hi, I'm curious if you upgrade to the latest pseudo revision whether this helps at all. There was a fix that was partially related to issues like this. The error either means the file was deleted on d

lists.yoctoproject.org wrote: Just to loop back, we've updated all the branches to mention 8.7 now and tweaked some of the other entries too (thanks Steve!). Cheers, Richard

lists.yoctoproject.org wrote: We're testing against AlmaLinux 8.7 so I think this is a documentation issue and the value hasn't been updated to match what we're now testing against. I've updated maste

No, it should have changed PATH in the recipe and used these intercept scripts. The intercept scripts should have changed the user/group to "root", which would work under pseudo in the SDK context. Yo

I suspect this was solved with https://git.yoctoproject.org/poky/commit/?id=8dd0a45c858290288e1a1fef046b5cfcf7ff6257 Cheers, Richard

Patches look otherwise ok to me so please resend! Cheers, Richard

lists.yoctoproject.org wrote: The reports have never been useful enough to parse so that should be fine. It still shows incorrectly for me. It is an issue with the bootlin mail setup and DNS, not to d

I'll ask for the third time. Are you running bitbake directly? I'd like to understand the environment bitbake is being run in. Something is breaking the ownership/permissions and I guess it is some ki

Are you running bitbake directly? How did you dump those sudo permissions from inside bitbake? Cheers, Richard

I don't see anything in there which runs that task under fakeroot/pseudo. Are you building this within some kind of container and/or under something like kas? The error suggests that sudo has been res

You didn't say which task this was in, I'm going to guess it is one being run under pseudo, our fakeroot emulator. The fakeroot emulation doesn't work well with "real" sudo commands. Cheers, Richard

You can find the code here: https://git.yoctoproject.org/git-refinery-web/ We've had a few issues deploying an instance of it unfortunately. There are some examples of filter functions here: https://g

This is the second report I've seen of this. I'm wondering about changing the default PN dummy value in bitbake.conf to include a "-"... Cheers, Richard

A reproducibility issue did occur in this release build in kernel- devsrc and perf. I think we should put this through QA and release note the issue. There is a patch which I think should fix it but I

The result of the M2 build is here, specifically the regression report: https://autobuilder.yocto.io/pub/releases/yocto-4.2_M2.rc2/testresults/testresult-regressions-report.txt (warning, it is a 13MB

There looks to be a potential issue here since you drop the use of comparebranch entirely. This comes from config.json: "BUILD_HISTORY_FORKPUSH" : {"poky-contrib:ross/mut" : "poky:master", "poky:maste

lists.yoctoproject.org wrote: Thanks. Since I like living dangerously, I've put these on the master branch for the M2 release build. I wanted to see how this does in a real world test. I did notice on

lists.yoctoproject.org wrote: Thinking about this a little, we can probably push symlinks into the older release branches, at least until we consider backporting some changes. Cheers, Richard