Re: [linux-yocto] [PATCH 1/1] aufs5:fix:avoid to access rw_sem.owner in RT kernel

Hi Bruce, Please review whether this patch should also be applied to v5.10/standard/preempt-rt. Thanks, Yongxin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9621): https://lists.yoctoproject.org/g/linux-yocto/message/9621 Mute This Topic:

Re: [yocto] Can't build gatesgarth after PSEUDO_IGNORE_PATHS change in poky

Hi, Just to follow up on this, I eventually figured out the root cause, but I still don't understand why PSEUDO_IGNORE_PATHS was allowing it to work... When I setup my PC, I created the user and then changed the UID of the user (for NFS auth reasons). The end result of this is that my user has

[yocto] eula-downloads.yoctoproject.org down???

Getting a message today Fetcher failure for URL: 'https://eula-downloads.yoctoproject.org/index.php'. URL https://eula-downloads.yoctoproject.org/index.php doesn't work. Please ensure your network is configured correctly. Can't ping the url?  Anyone have an ETA on this being back up?  Just

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

All, YP M+ or high bugs which moved to a new milestone in WW13 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 10693 Add a testcase for multilib eSDK on the autobuilder

[yocto] 3Enhancements/Bugs closed WW13!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macl...@windriver.com 5 richard.pur...@linuxfoundation.org 2 r...@burtonini.com 2 yifan...@windriver.com 2 raj.k...@gmail.com 1 kexin@windriver.com 1

[yocto] Current high bug count owners for Yocto Project 3.3

All, Below is the list as of top 40 bug owners as of the end of WW13 of who have open medium or higher bugs and enhancements against YP 3.3. There are 23 possible work days left until the final release candidates for YP 3.3 needs to be released. Who Count r...@burtonini.com 17

[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:

[yocto-announce] [ANNOUNCEMENT]Milestone 3 for Yocto Project 3.3 (yocto-3.3_M3) now available

Hello, We are pleased to announce the third milestone release for Yocto Project 3.3 (yocto-3.3_M3) is now available for download. Download: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.3_M3 bitbake: ed8e1fd4cf9d5ac8a8203638add99d686b4b3521 meta-arm:

[yocto] [ANNOUNCEMENT]Milestone 3 for Yocto Project 3.3 (yocto-3.3_M3) now available

Hello, We are pleased to announce the third milestone release for Yocto Project 3.3 (yocto-3.3_M3) is now available for download. Download: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.3_M3 bitbake: ed8e1fd4cf9d5ac8a8203638add99d686b4b3521 meta-arm:

Re: [yocto] Naming images

Hi Damien, On Mon, Mar 29, 2021 at 03:33:09PM +0300, Damien LEFEVRE wrote: > Hi, > > In my build system the generated images are in this format: > > imagename-machine-timestamp.img > > For release builds, I'd like to replace the time stamp with the image > version. I could rename the image

Re: [yocto] Package indexes for package feeds, ipk and rpm

That's just how RPM and opkg work, Yocto can't control or alter that. Ross On Mon, 29 Mar 2021 at 10:36, keydi wrote: > > Regarding package feed packages index I learned one difference between rpm > and ipk. > For ipk plain-text files named Packages are generated and placed to >

[yocto] Naming images

Hi, In my build system the generated images are in this format: imagename-machine-timestamp.img For release builds, I'd like to replace the time stamp with the image version. I could rename the image after the build but is there a better way? I found a BUILDNAME variable but it has no effect.

[yocto] [meta-zephyr][PATCH 1/1] zephyr-kernel-src.inc: Support samples from external layers

From: Andrei Gherzan The inc file references patch(es) local to the inc file. Including this file from another recipe as part of an external layer, will make bitbake fail finding the files referenced in zephyr-kernel-src.inc's SRC_URI. By including an explicit path to the files directory in

[yocto] Package indexes for package feeds, ipk and rpm

Regarding package feed packages index I learned one difference between rpm and ipk. For ipk plain-text files named Packages are generated and placed to architecture-subdirectories in tmp/deploy/ipk tree. For rpm I see just one file named Packages, it is a binary file yet located in one image

Re: [yocto] To burn 'bitbake package-index' into build process

Thanks for hint. Which qualities might current implementation output still miss? I tried to ask in meantime three Yocto books for help but no clear help got. My search went toward distribution-level meta-data, this can be however wrong direction as package index is not built for target system

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.2.3.rc1)

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC