Remove __pycache__ directories when do_install. Signed-off-by: Yi Zhao <yi.zhao@...> --- .../setools/{setools_4.2.2.bb => setools_4.3.0.bb} | 8 +++++--- 1 file changed, 5

Signed-off-by: Yi Zhao <yi.zhao@...> --- recipes-security/selinux/libsepol_2.9.bb | 7 ------- recipes-security/selinux/libsepol_3.0.bb | 7 +++++++ 2 files changed, 7 insertions(+), 7

Signed-off-by: Yi Zhao <yi.zhao@...> --- .../selinux/{selinux_20190315.inc => selinux_20191204.inc} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

I think having just this would make this statement not do anything as these machine files includes x86-base.inc which also sets this variable using a ?=. This would probably also need a ??= in

Done: https://lists.yoctoproject.org/g/yocto/message/49131 BR, marek

This add possibility to override in custom layer. Signed-off-by: Marek Belisko <marek.belisko@...> --- conf/machine/intel-core2-32.conf | 2 +- conf/machine/intel-corei7-64.conf | 2

I just ran across a bbappend that change configure options, but looking at the original recipe, there is a PACKAGECONFIG option to do the same thing. So they could have used that mechanism instram of

Adding Michael (lack of confirmtation email from bugzilla). Alex

Hi Randy, I'm trying all day to create an account at bugzilla to file the issue, but somehow I don't get any confirmation mail (although I tried several mail accounts today, and no it didn't got

Ajam, It would be useful if you could reply either way. If there's still a problem then perhaps someone can help. If you are able to resolve the issue,

All, YP M+ or high bugs which moved to a new milestone in WW15 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 13604 [master-next]

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 43 developers as of the end of WW15 of who have open medium or higher bugs and enhancements against YP 3.1. There are 13 possible work days left until the final

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.. you're right. Well at least my answer is not complete ;) This is correct. We should encourage everyone to report, and even better propose a fix, to the relevant layer, when the 'problem' is

I beg to differ! Bbappends are making it difficult to reason about what the recipe with all its appends is doing (because they destroy spatial locality and aren't easily visible), and I would actually

A good rule of thumb is to never modify a metadata that is not yours. That applies to everything: * if you need to modify a bb file from a 3rd party library, create a bbappend file in your layer * if

As with a lot of things, I’m sure it all depends on the scope of the change. Personally, if I ‘own’ the original bbappend, then I consider if it’s worth establishing an override or some other

Hi All, I googled some topics on how to patch a recipe, most of them recommend to generate a corresponding <foo>.bbappend to apply the patch, I wonder if there is already a bbappend file, shall I

Hello all, This is the full report for yocto-3.1.rc2: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high