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

2022-01-31 Thread Stephen Jolley
All, YP M+ or high bugs which moved to a new milestone in WW05 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 12368 persistent bitbake server does not re-parse if previous build was ctrl+C

[yocto] Enhancements/Bugs closed WW05!

2022-01-31 Thread Stephen Jolley
All, The below were the owners of enhancements or bugs closed during the last week! Who Count mhalst...@linuxfoundation.org 1 trevor.gamb...@windriver.com 1 randy.macl...@windriver.com 1 richard.pur...@linuxfoundation.org 1 Grand Total 4 Thanks, Stephen K. Jolley Yocto P

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

2022-01-31 Thread Stephen Jolley
All, Below is the list as of top 44 bug owners as of the end of WW05 of who have open medium or higher bugs and enhancements against YP 3.5. There are 62 possible work days left until the final release candidates for YP 3.5 needs to be released. Who Count r...@burtonini.com 38 michael

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

2022-01-31 Thread Stephen Jolley
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: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc

[yocto] Yocto Project Status WW05`22

2022-01-31 Thread Stephen Jolley
Current Dev Position: YP 3.5 M3 Next Deadline: 21th Feb. 2022 YP 3.5 M3 build Next Team Meetings: * Bug Triage meeting Thursday Feb. 3rd 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) *

[yocto] QA notification for completed autobuilder build (yocto-3.1.14.rc1)

2022-01-31 Thread Richard Purdie
A build flagged for QA (yocto-3.1.14.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.14.rc1 Build hash information: bitbake: be6ecc160ac4a8d9715257b9b955363cecc081ea meta-agl: 7a644d636237459c54128a71d083cb6f9e1b8e60 meta-arm:

Re: [yocto] How to prevent auto start of matchbox-terminal at boot?

2022-01-31 Thread Dave Beal via lists.yoctoproject.org
Thanks, Alex!  That was it.  The script that started the matchbox-terminal is /usr/bin/mini-x-session.  I just edited this file and commented out the terminal line and another line that was setting my display to an incorrect resolution. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages se

[yocto] Where setup KCONF_AUDIT_LEVEL value

2022-01-31 Thread Mauro Ziliani via lists.yoctoproject.org
Hi all. The KCONF_AUDIT_LEVEL variable must be setup in a .conf file or I can change it in a recipe? I try to understand why my file defconfig is not used my kernel configurator MZ -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56030): http

Re: [yocto] boot script for barebox in build/deploy/images/$IMAGE_NAME/ directory

2022-01-31 Thread Gary Huband via lists.yoctoproject.org
In Zeus I have a recipe that installs the file (a u-boot boot.scr for me): install -m 0644 boot.scr ${DEPLOYDIR} Make sure the recipe is included in your image. Then in my machine conf: IMAGE_BOOT_FILES = "zImage oftree imx7d-phyboard-zeta-004.dtb imx7d-phyboard-zeta-004-m4.dtb boot.scr" Gary

Re: [yocto] Fetch private gitlab repo using ssh with Yocto recipe #bitbake

2022-01-31 Thread Sourabh Hegde
Hello @Nicolas @Erik @Khem, Update from my side: After following some discussion from other posts, I added "config" file. ~/.ssh/config: Host git.example.com HostName git.example.com User git PreferredAuthentications publickey IdentityFile ~/.ssh/id_ed25519.pub # LogLevel DEBUG3 Then I did "ev

Re: [yocto] How to prevent auto start of matchbox-terminal at boot?

2022-01-31 Thread Alexander Kanavin
The logs reveal that 'packagegroup-core-x11 packagegroup-core-x11-base packagegroup-core-x11-xserver' are all installed. x11-base pulls in recipes-graphics/mini-x-session/mini-x-session_0.1.bb which starts a minimal session with a terminal. You should either drop x11-base, or tweak mini-x-session s