QA notification for completed autobuilder build (yocto-3.4.1.rc1)
Richard Purdie
A build flagged for QA (yocto-3.4.1.rc1) was completed on the autobuilder and is
available at: https://autobuilder.yocto.io/pub/releases/yocto-3.4.1.rc1 Build hash information: bitbake: 44a83b373e1fc34c93cd4a6c6cf8b73b230c1520 meta-agl: 83c5764a38902c6d17f106ea545533192ebd46fe meta-arm: 55ae0eb1a6c210e6e87f5a553a1ebbb7dcc7a725 meta-aws: c92344938ab4d37de8bd8b799186dbbe3019a069 meta-gplv2: f04e4369bf9dd3385165281b9fa2ed1043b0e400 meta-intel: d0f1c1ebfd9b7fe8d22c6a62208f78bccc6f3bf6 meta-mingw: f5d761cbd5c957e4405c5d40b0c236d263c916a8 meta-openembedded: f31b9854b13e46cb74569538a33c36730c00c695 oecore: 70384dd958c57d1da924a66cffa35f80eb60d4b0 poky: b53230c08d9f02ecaf35b4f0b70512abbf10ae11 This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-security][PATCH] python3-fail2ban: update to tip
On 11/29/21 8:03 AM, Konrad Weihmann wrote:
It aligns with the tip of branch 0.11. -armin SRC_URI = "
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
M+ & H bugs with Milestone Movements WW48
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Enhancements/Bugs closed WW48!
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Current high bug count owners for Yocto Project 3.5
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yocto Project Newcomer & Unassigned Bugs - Help Needed
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#Newcomer_Bugs Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project. If anyone can help, please take ownership of the bug and send patches! If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.
Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 391 unassigned or newcomer bugs.
We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly four different "priority" classes right now, “3.4”, “3.5, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.
Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
David Babich
On Thu, Nov 25, 2021 at 02:45 AM, Nicolas Jeker wrote:
On Wed, 2021-11-24 at 09:55 -0800, Tim Orling wrote:Ah OK, I wasn't aware of the the python naming convention. That is likely my problem since I'm using Honister which uses Python 3.9. I pulled the wheel from NVIDIA's forums for pytorch, unfortunately they've not released one for Python 3.9 so I will likely have to create it myself using the build from scratch method described in the article I linked. Unfortunately this will likely open a new can of worms... There's a section about building from source with a patch in the I'm using Honister and the machine is 'jetson-tx2-dev-kit-tx2i', I'm making a custom distro based on the meta-tegra-demo from this: A large part of the problem that I have is that many of these custom packages don't provide a nice .tar.gz pypi source distribution that I could use with the pypi class. My target install ends up on a spacecraft, so there is a strong desire to have a fully managed build that can just be flashed onto the target tx2i without the need to do any post installation or configuration. Sadly I'm finding that a lot of these third party dependencies do not lend themselves well to the yocto paradigm. I'm thinking that I may have to setup the target board, install the third party packages on the target using whatever is required to do that, then copy the build products back to the host and use a bitbake recipe to just do_install:append the built products into the rootfs during the yocto build. Does that sound feasible? I've not had to do this before, but it seems like it might be a reasonable approach given the complexity of the situation. Thanks -David
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-security][PATCH] python3-fail2ban: update to tip
Konrad Weihmann <kweihmann@...>
On 29.11.21 16:14, Armin Kuster wrote:
Signed-off-by: Armin Kuster <akuster808@...>according to github 80805cabfcf57dd0454d47d7f86d43c6738ce629 is the tip. any specific reason to pick the commit before that? SRC_URI = " git://github.com/fail2ban/fail2ban.git;branch=0.11;protocol=https \
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-rockchip] dunfell: u-boot build issue when added patch to u-boot
Tom Rini
On Sat, Nov 27, 2021 at 09:24:56PM +0100, Marek Belisko wrote:
Hi,Did some sort of "enable environment support in SPL" option get enabled in your patches perhaps? -- Tom
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[meta-security][PATCH] python3-fail2ban: update to tip
Signed-off-by: Armin Kuster <akuster808@...>
--- recipes-security/fail2ban/python3-fail2ban_0.11.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-security/fail2ban/python3-fail2ban_0.11.2.bb b/recipes-security/fail2ban/python3-fail2ban_0.11.2.bb index 4e344c8..f6394cc 100644 --- a/recipes-security/fail2ban/python3-fail2ban_0.11.2.bb +++ b/recipes-security/fail2ban/python3-fail2ban_0.11.2.bb @@ -9,7 +9,7 @@ HOMEPAGE = "http://www.fail2ban.org" LICENSE = "GPL-2.0" LIC_FILES_CHKSUM = "file://COPYING;md5=ecabc31e90311da843753ba772885d9f" -SRCREV ="d6b884f3b72b8a42b21da863836569ef6836c2ea" +SRCREV ="4fe4ac8dde6ba14841da598ec37f8c6911fe0f64" SRC_URI = " git://github.com/fail2ban/fail2ban.git;branch=0.11;protocol=https \ file://initd \ file://run-ptest \ -- 2.25.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
define extended partition in wks file
Silvan Murer
Hi,
I'm using wic for creating a boot image in my yocto layer. An extended partition is automatically created, when build an image with more than four partitions. The extended partition is added at the end and in my case, the last two logic partitions are included there. Does an option exist which allows the definition of the partitions which are included in the extended partition? In may case, I'm looking for an option to put the two rootfs partitions (rootfs1 and rootfs2) into a common extended partition. And the data partition at the end should be in its own logic partition. Does some option exist or is it possible to handle them in another way? probably by creating an own wic plugin? The *.wks file contains the following entries: part --source rawcopy --sourceparams="file=u-boot-splx4.sfp" --ondisk mmcblk0 --system-id=a2 --align 1024 --fixed-size 10M part /run/mount/bootloader --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 1024 --size 500M part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label rootfs1 --align 1024 --fixed-size 2G part --source rootfs --ondisk mmcblk0 --fstype=ext4 --label rootfs2 --align 1024 --fixed-size 2G part /run/mount/data --ondisk mmcblk0 --fstype=ext4 --label data --align 1024 --fixed-size 3G Thanks, Silvan
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-security][PATCH 2/2] meta-parsec/README.md: fix for append operator combined with +=
thanks.
toggle quoted messageShow quoted text
merged.
On 11/19/21 7:18 AM, Yi Zhao wrote:
Signed-off-by: Yi Zhao <yi.zhao@...>
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-security][PATCH 1/2] openssl-tpm-engine: fix warning for append operator combined with +=
merged.
toggle quoted messageShow quoted text
thanks
On 11/19/21 7:18 AM, Yi Zhao wrote:
Fixes:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-security][PATCH] apparmor: fix warning of remove operator combined with +=
On 11/18/21 11:06 PM, kai wrote:
From: Kai Kang <kai.kang@...>thanks, merged.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[meta-security][PATCH] libest: does not build with openssl 3.x
blacklist for now. Remove from pkg grp
Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/packagegroup/packagegroup-core-security.bb | 1 - recipes-security/libest/libest_3.2.0.bb | 3 +++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/recipes-core/packagegroup/packagegroup-core-security.bb b/recipes-core/packagegroup/packagegroup-core-security.bb index e9dad5b..fefc66d 100644 --- a/recipes-core/packagegroup/packagegroup-core-security.bb +++ b/recipes-core/packagegroup/packagegroup-core-security.bb @@ -38,7 +38,6 @@ RDEPENDS:packagegroup-security-utils = "\ python3-privacyidea \ python3-fail2ban \ softhsm \ - libest \ sshguard \ ${@bb.utils.contains_any("TUNE_FEATURES", "riscv32 ", "", " libseccomp",d)} \ ${@bb.utils.contains("DISTRO_FEATURES", "pam", "sssd google-authenticator-libpam", "",d)} \ diff --git a/recipes-security/libest/libest_3.2.0.bb b/recipes-security/libest/libest_3.2.0.bb index 31fbe3c..41a4025 100644 --- a/recipes-security/libest/libest_3.2.0.bb +++ b/recipes-security/libest/libest_3.2.0.bb @@ -25,3 +25,6 @@ S = "${WORKDIR}/git" PACKAGES = "${PN} ${PN}-dbg ${PN}-dev" FILES:${PN} = "${bindir}/* ${libdir}/libest-3.2.0p.so" + +# https://github.com/cisco/libest/issues/104 +PNBLACKLIST[libest] ?= "Needs porting to openssl 3.x" -- 2.25.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
OpenEmbedded Happy Hour December 3 8pm/2000 UTC after OEDVM
Denys Dmytriyenko
All,
As previously announced, OpenEmbedded Developer Virtual Meeting will take place on December 3 from 12:00 UTC until 20:00 UTC: https://www.openembedded.org/wiki/OEDVM_Nov_2021 Once the meeting is over, everybody is invited to hang out and relax at the OpenEmbedded Happy Hour, which tentatively will start at 20:00 UTC (3pm ET / 12pm PT): https://www.openembedded.org/wiki/Happy_Hours https://www.openembedded.org/wiki/Calendar https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+December+3&iso=20211203T20 -- Regards, Denys Dmytriyenko <denis@...> PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964 Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-rockchip] dunfell: u-boot build issue when added patch to u-boot
Marek Belisko
Hi,
On Fri, Nov 26, 2021 at 11:55 PM Trevor Woerner <twoerner@...> wrote: I'm adding dunfell support for mender :). In this link mender rockchip integration is for older u-boot not 2020.01 https://github.com/mendersoftware/meta-mender-community/tree/dunfell/meta-mender-rockchipBR, marek -- as simple and primitive as possible ------------------------------------------------- Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [OE-core] How to create connman_1.40.bbappend to enable and to build connman with iwd?
JH
Thanks Tim for the link, I have built the iwd.
According to Daniel's advice to configure with "--disable-wifi, --enable-iwd", I added PACKAGECONFIG[wifi] = "--disable-wifi, --enable-iwd", to override PACKAGECONFIG[wifi] in oe-core connman_1.40.bb. The intention is to remove wpa-supplicant and to add iwd to connman_1.40.bbappend, it built the image without error, I believe that the syntax is OK, but the wpa-supplicant was still built and packaged. Any idea from OE/Yocto insiders why PACKAGECONFIG[wifi] in bbappend is not effective? Daniel, how can I verify in the Linux console if the connmand is running with iwd or with wpa_supplicant? I have disabled wpa_supplicant.service, and I'll remove wpa_supplicant completely when I find a way to do it. Thank you. Kind regards, - jh On 11/27/21, Tim Orling <ticotimo@...> wrote: On Fri, Nov 26, 2021 at 5:48 PM Tim Orling via lists.yoctoproject.org -- "A man can fail many times, but he isn't a failure until he begins to blame somebody else." -- John Burroughs
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [OE-core] How to create connman_1.40.bbappend to enable and to build connman with iwd?
Tim Orling
On Fri, Nov 26, 2021 at 5:48 PM Tim Orling via lists.yoctoproject.org <ticotimo=gmail.com@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [OE-core] How to create connman_1.40.bbappend to enable and to build connman with iwd?
Tim Orling
On Thu, Nov 25, 2021 at 10:26 PM JH <jupiter.hce@...> wrote: Hi, Please look at the layer index for recipes: I don’t have any advice for building it however.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|