Re: [yocto] What is the recommended method to patch a recipe?

On 4/13/20 10:31 AM, Nicolas Dechesne wrote: > On Mon, Apr 13, 2020 at 12:55 PM Alexander Kanavin > wrote: > >> On Mon, 13 Apr 2020 at 12:46, Nicolas Dechesne < >> nicolas.deche...@linaro.org> wrote: >> >>> A good rule of thumb is to never modify a metadata that is not yours. >>> That applies to

Re: [yocto] Files get sporadically lost for native packages

Adding Michael (lack of confirmtation email from bugzilla). Alex On Mon, 13 Apr 2020 at 19:59, Konrad Weihmann wrote: > 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

Re: [yocto] Files get sporadically lost for native packages

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 stuck in spam;-)) - guess that's not how it is supposed to be, right :-)? - I don't know where to

Re: [linux-yocto][yocto-kernel-cache][master yocto-5.4][PATCH] features/f2fs: add f2fs fragment support

On Fri, Apr 10, 2020 at 6:02 AM Zhang, Qiang wrote: > > Hi Bruce. > > Trouble help merged features/f2fs to yocto-5.2 cherry picked to 5.2 Bruce > > Thank you > > 发件人: Bruce Ashfield > 发送时间: 2020年3月26日 10:33 > 收件人: Zhang, Qiang > 抄送:

Re: [yocto] Image size reduction

On 2020-04-04 12:27 p.m., Ajam Ali wrote: Hi All, Thanks for your suggestions. I am working on your suggestions. I will let you know if it did not work for me. 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

Re: [linux-yocto] v5.2.x - stable updates comprising v5.2.37

In message: v5.2.x - stable updates comprising v5.2.37 on 13/04/2020 Paul Gortmaker wrote: > Bruce, Yocto kernel folks: > > Here is the next 5.2.x stable update "extension" primarily created for > the Yocto project, as the 16th v5.2.x post-EOL release. > > The content is from an audit of what

Re: [linux-yocto][v5.4/standard/preempt-rt/base][PATCH 1/1] mm: do not warn for suspend when allocate memory on RT

In message: [linux-yocto][v5.4/standard/preempt-rt/base][PATCH 1/1] mm: do not warn for suspend when allocate memory on RT on 10/04/2020 Liwei Song wrote: > Interrupts are off during resume from RAM, this will triger a warning > when allocate memory in non-preemptible context on RT since commit

Re: [linux-yocto] Fix a build failure on zeus

merged Bruce In message: Fix a build failure on zeus on 09/04/2020 Zhang Xiao wrote: > Hi Bruce, > > On zeus, commit 20556f9b02: > http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/arch/x86/kernel/cpu/mce/dev-mcelog.c?h=v5.2/standard/intel-x86=20556f9b022e6318ce8f48 > > used

[yocto] M+ & H bugs with Milestone Movements WW15

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] Distrodata.test_maintainers fails

[yocto] Enhancements/Bugs closed WW15!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macl...@windriver.com 7 richard.pur...@linuxfoundation.org 5 timothy.t.orl...@intel.com 2 akus...@mvista.com 2 ee.peng.y...@intel.com 1 changqing...@windriver.com 1

[yocto] Current Top developers on Yocto Project 3.1

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 release candidates for YP 3.1 needs to be released. Who Count richard.pur...@linuxfoundation.org

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

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 the triage page under the appropriate heading:

[linux-yocto] v5.2.x - stable updates comprising v5.2.37

Bruce, Yocto kernel folks: Here is the next 5.2.x stable update "extension" primarily created for the Yocto project, as the 16th v5.2.x post-EOL release. The content is from an audit of what went into the v5.4.14 and v5.4.15 releases - plus some CVEs and upstream commits listed as Fixes: for

Re: [yocto] What is the recommended method to patch a recipe?

On Mon, Apr 13, 2020 at 12:55 PM Alexander Kanavin wrote: > On Mon, 13 Apr 2020 at 12:46, Nicolas Dechesne < > nicolas.deche...@linaro.org> wrote: > >> 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

Re: [yocto] What is the recommended method to patch a recipe?

On Mon, 13 Apr 2020 at 12:46, Nicolas Dechesne wrote: > 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 you need to modify a bbappend

Re: [yocto] What is the recommended method to patch a recipe?

On Mon, Apr 13, 2020 at 10:20 AM nus1998 wrote: > Hi All, > > I googled some topics on how to patch a recipe, most of them recommend to > generate a corresponding .bbappend to apply the patch, I wonder if > there is already a bbappend file, shall I modify the bbappend file > directly, or create

Re: [yocto] What is the recommended method to patch a recipe?

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 similar mechanism within that bbappend, depending on what I’m developing (an image feature or

[yocto] What is the recommended method to patch a recipe?

Hi All, I googled some topics on how to patch a recipe, most of them recommend to generate a corresponding .bbappend to apply the patch, I wonder if there is already a bbappend file, shall I modify the bbappend file directly, or create another layer to overwrite the bbappend file (and