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

Hello, We are pleased to announce the third milestone release for Yocto Project 3.3 (yocto-3.3_M3) is now available for

Hi Damien, IMAGE_NAME variable is the one specifying the name which should be used for the final image. c.f. https://docs.yoctoproject.org/ref-manual/variables.html#term-IMAGE_NAME By default, its

That's just how RPM and opkg work, Yocto can't control or alter that. Ross

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

From: Andrei Gherzan <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

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

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

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.

A build flagged for QA (yocto-3.2.3.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.2.3.rc1 Build hash information: bitbake:

convert to cmake and general cleanup include on oe env patch and glibc 2.33 header fixup if running w/in qemu, need to add qemuparams="-m 2048" to allow freshclam not to oom Signed-off-by: Armin

Right.. I should change the PV of the recipe.  Ill send v2 thanks for the feedback. -armin

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/packagegroup/packagegroup-core-security.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

The following changes since commit ef52b284e8cbe90c18fdab6a0d6fa8095a2c4ed9: send-qa-email: Save the QA email in case it doesn't reach the mailing lists. (2021-02-23 10:24:14 +0000) are available

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/index is close to what you want, but I didn't quite finish it off! Ross

Hi Armin, Are you sure it's not dev/0.103 here? Also, there seems to be a 0.103.1 branch available already. I don't really know which version you're targeting. I would say it makes sense to have this

convert to cmake and general cleanup include on oe env patch and glibc 2.33 header fixup if running w/in qemu, need to add qemuparams="-m 2048" to allow freshclam not to oom Signed-off-by: Armin

Not sure if anyone is still using this, but I did update OpenSSL 1.0.2 to fix the latest three CVEs: CVE-2021-23839 CVE-2021-23840 CVE-2021-23841 All branches updated. Additionally master has been

I guess SiFive is the one you could approach? I actually sent them my CV a few weeks back, as a long shot to try to see if they're interested in Yocto and someone like myself to help them with

Yocto Technical Team Minutes, Engineering Sync, for March 23, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made