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

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

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

All, The below were the owners of enhancements or bugs closed during the last

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

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