I've created an npm package recipe for node-red-node-serialport using devtool add "npm://registry.npmjs.org;package=node-red-node-serialport;version=1.0.1" which generated this recipe. The problem is

This is my first time working with them so I am learning a lot but never encountered anything like it. Trying to look into what it would require to move to a newer version it appears as if they have

It's a contracting issue. You need to specify in writing that the vendor cannot provide ancient Yocto. Otherwise they won't bother. Alex

Yes I know. Not sure why QC is stuck on Thud. Even newer releases from QC for the target that we are working on is stuck at Thud. Mans Den fre 8 apr. 2022 kl 18:59 skrev Alexander Kanavin

Many layers append BBFILE_COLLECTIONS and therefore have 'core <layer>' During update.py, this means we are likely not handling the collection we expect: WARNING:

ERROR: Variable BB_ENV_EXTRAWHITE has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS ERROR: Variable BB_ENV_EXTRAWHITE from the shell environment has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS ERROR:

Add the newish Inactive-Upstream upstream status. Add 0046_alter_patch_status.py migration. Signed-off-by: Tim Orling <tim.orling@...> layerindex/migrations: update patch

The url pattern was not including the trailing / [YOCTO #14445] Signed-off-by: Tim Orling <tim.orling@...> --- layerindex/urls.py | 2 +- 1 file changed, 1 insertion(+), 1

Various fixes to address errors and warnings when running update.py The following changes since commit 796d2455bb862ed4c71eadfa9fcf4c002752c2f3: templates/*: staticfiles -> static (2022-01-13

The build patches are now included in the upstream, the local binary checkes can be disabled with --disable-ptool-checks, the boostrap doesn't need to be called if the release .tar.gz is

Calling autoreconf outside git repo causes the version number to be null. This patch makes the version number fixed. Since Yocto now uses OpenSSL 3.0, the file packaging need to be

The version number is correctly assigned only when the release .tar.gz is used. Signed-off-by: Petr Gotthard <petr.gotthard@...> --- .../tpm2-abrmd/{tpm2-abrmd_2.4.0.bb =>

This deletes the patches that were unused for a long time, updates the tpm2-tss package and introduces a fix to the version number problem that got introduced with the 3.2.0 version. Signed-off-by:

Also, the recipe is fixed to correctly package the openssl provider. This new tpm2-openssl: - Fixed segmentation fault when a signature algorithm is beging initialized without a private key. -

Calling autoreconf outside git repo causes the version number to be null. This patch makes the version number fixed. Signed-off-by: Petr Gotthard <petr.gotthard@...> ---

Hello. I'd suggest some "house cleaning" of the tpm2-software. (I am a member of the tpm2-software community and an upstream developer of the tpm2-openssl provider.) In general: Some tpm2-software

Hi Casey, I've recently had to activate secureboot on some uefi target. I was trying to use meta-secure-core/meta-efi-secure-boot aft first, but after digging a bit more into meta-intel, I've

Hello, We have an Intel Elkhart Lake device that we are trying to get Secure Boot (via meta-secure-core/meta-efi-secure-boot SELoader) working on using the Dunfell release. This device uses Mender for

Hello All, This may not be the issue with Yocto itself but rather related to properly booting up Linux on Avenger96(STM32MP1) board. I am currently working on Avenger96 with Yocto(Dunfell). Aim is to

Thud has been EOL for a long time. You can see when the support been added here (end of 2019 it