Hi, in my current Yocto flow, I test and build recipes locally on my dev machine (I usually test changes on one architecture) and if the build finishes succesfully, I push changes to git repo. My

Hey, I'm just updating my calendar for the new year and spotted a bit of confusion. The website page https://www.yoctoproject.org/public-virtual-meetings/ shows the meeting times an hour earlier

All, YP 3.1 M1 has been released. Please review the bugs at https://wiki.yoctoproject.org/wiki/Bug_Triage#Old_Milestone and move/edit the target milestone to YP 3.1 M2 or later. Thanks,

[Re: [meta-selinux][PATCH] audit: fix host contamination for swig] On 19.12.31 (Tue 14:20) Yi Zhao wrote: Heh, telling that 16.04 is a modern Ubuntu in this context. :-) Anyway, yeah, I don't even

Signed-off-by: Armin Kuster <akuster808@...> --- .../{clamav_0.99.4.bb => clamav_0.101.5.bb} | 63 +++++++------------ 1 file changed, 24 insertions(+), 39 deletions(-) rename

When I dropped it in my previous patch I just tested it on some modern Linux distributions (e.g. Ubuntu 16.04/18.04 Fedora 31). There is no such error because the audit.h on the host is matched to our

Hi Yi, So, just to confirm, this is needed in your experience (I don't have any builders that are that old, so I haven't verified). I just ask because we only just dropped this patch to begin

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

Ok, I just tested with master ff0db7b88ec5026f75a86f6fd8562c35b95b1017 and it works fine.

*ping* //Peter

On 12/29/19 1:06 PM, Thilo Graf wrote: Can you verify Master please. - armin

Hi I 've used the devtool option -S to upload striped binaries to my test hardware but binaries are not executable. The rights were only set to 644. Without -S it works fine. Can anybody verifiy this

Hi All, I'm experiencing a strange issue when using thud branch with the following recipe snippet on thud I get the following error github.com-pkg-diff-native-20190930-r0: task do_patch:

Agreed. That is kind of where we are at. Yes, these closed source layers/packages simply point to closed source repos. I need them to prepare pre-compiled archives for these packages that can be

There are ways to adapt such a proprietary layer. If the intranet location is set with a bitbake variable, then you can adjust the variable to point to *your* intranet, and mirror all the needed

I think that was their intention from the start. they wanted to only give their customer the ability to produce user level apps, without modifying the system, but for our enterprise that is

On 12/27/19 5:17 PM, Alexander Kanavin wrote: Alex, Isn't that even mentioned is the manual as best practices? Odd a OEM would not even follow that :(. Nick

To me it seems that the SDK is the wrong kind of delivery to begin with (as it is basically a frozen target image configuration without the ability to customize the entire system build; Yocto SDKs are

thanks for the followup! yeah...no legal advice is expected online...just a forum to vent in, sometimes. Yup...been there, done that. Yes, very bad choice in a field with no notably good

I would like to add that it helps enormously if you introduce yourself to the community properly. When you do not state what your company is, who is your OEM, and write from a gmail account using what