|
Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)
Is the sato-sdk on qemuppc also intermittent issue
Is the sato-sdk on qemuppc also intermittent issue
|
By
Raj, Khem <khem_raj@...>
·
#56821
·
|
|
SRC_URI from AWS codecommit with user and password
#yocto
Hi All,
I have an application writing in Qt/QML for specific embedded target, The repo for this application is maintained in AWS codecommit which has user and password .
How to mentioned in the recipe
Hi All,
I have an application writing in Qt/QML for specific embedded target, The repo for this application is maintained in AWS codecommit which has user and password .
How to mentioned in the recipe
|
By
mail2uvijay@...
·
#56820
·
|
|
Re: package and booting an initramfs image
Please, read carefully thru this yocto @ thread.
https://www.yoctoproject.org/pipermail/yocto/2018-July/041680.html
Zee
_______
Please, read carefully thru this yocto @ thread.
https://www.yoctoproject.org/pipermail/yocto/2018-July/041680.html
Zee
_______
|
By
Zoran
·
#56819
·
|
|
IPv6 Autogeneration Not Persisting
I’m trying to auto-generate IPv6 for interfaces on a ZPE Systems device but not able to. It keeps reverting to a value of ‘1’ after a reboot even though the config file clearly has ‘3’.
I’m trying to auto-generate IPv6 for interfaces on a ZPE Systems device but not able to. It keeps reverting to a value of ‘1’ after a reboot even though the config file clearly has ‘3’.
|
By
Syed, Nabeel <nabsyed@...>
·
#56818
·
|
|
[meta-security][PATCH] Add EROFS support to dm-verity-img class
Add support for the EROFS image, and it's compressed options, to the
dm-verity-img.bbclass setup, theoretically this is a simple addition to
the list of types however there is a quirk in how Poky
Add support for the EROFS image, and it's compressed options, to the
dm-verity-img.bbclass setup, theoretically this is a simple addition to
the list of types however there is a quirk in how Poky
|
By
Joshua Harley
·
#56817
·
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)
3.3.6 built but there were two issues. One was a qemu boot test failure for
core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't
any, qemu never seemed to start but nothing
3.3.6 built but there were two issues. One was a qemu boot test failure for
core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't
any, qemu never seemed to start but nothing
|
By
Richard Purdie
·
#56816
·
|
|
QA notification for completed autobuilder build (yocto-3.3.6.rc1)
A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1
Build hash information:
bitbake:
A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1
Build hash information:
bitbake:
|
By
Pokybuild User <pokybuild@...>
·
#56815
·
|
|
[meta-raspberrypi][PATCH] meta-raspberrypi: u-boot: remove the randundant patch
This patch had been merged into u-boot upstream. Its commit is
29f7d05a347a("dm: core: Move ofdata_to_platdata() call earlier").
So, remove the randundant patch to avoid building
This patch had been merged into u-boot upstream. Its commit is
29f7d05a347a("dm: core: Move ofdata_to_platdata() call earlier").
So, remove the randundant patch to avoid building
|
By
Meng Li
·
#56814
·
|
|
package and booting an initramfs image
I have a need to package my kernel, dtb, and rootfs manually and then boot this as an initramfs. I'm not sure which files from the deploy/images directory to use. I see there is an rootfs.cpio.gz file
I have a need to package my kernel, dtb, and rootfs manually and then boot this as an initramfs. I'm not sure which files from the deploy/images directory to use. I see there is an rootfs.cpio.gz file
|
By
Embedded 1
·
#56813
·
|
|
[RFC PATCH yocto-autobuilder-helper 6/6] scripts: run-docs-build: reuse logic to link to latest tag
From: Quentin Schulz <quentin.schulz@...>
Since the latest tag already has a specific handling in the forloop,
let's just move the symlink creation inside the forloop.
Cc: Quentin
From: Quentin Schulz <quentin.schulz@...>
Since the latest tag already has a specific handling in the forloop,
let's just move the symlink creation inside the forloop.
Cc: Quentin
|
By
Quentin Schulz
·
#56812
·
|
|
[RFC PATCH yocto-autobuilder-helper 5/6] scripts: run-docs-build: make latest documentation tag the default version
From: Quentin Schulz <quentin.schulz@...>
Currently, the master branch is the default branch being displayed by
default when reaching the Yocto docs website. When big changes
From: Quentin Schulz <quentin.schulz@...>
Currently, the master branch is the default branch being displayed by
default when reaching the Yocto docs website. When big changes
|
By
Quentin Schulz
·
#56811
·
|
|
[PATCH yocto-autobuilder-helper 4/6] scripts: run-docs-build: use set_versions.py and switchers.js.in from master
From: Quentin Schulz <quentin.schulz@...>
set_versions.py and switchers.js.in need to be up-to-date so that a
consistent behavior is kept between different branches and tags of
From: Quentin Schulz <quentin.schulz@...>
set_versions.py and switchers.js.in need to be up-to-date so that a
consistent behavior is kept between different branches and tags of
|
By
Quentin Schulz
·
#56810
·
|
|
[PATCH yocto-autobuilder-helper 3/6] scripts: run-docs-build: add option to skip upstream rsync
From: Quentin Schulz <quentin.schulz@...>
The rsync only makes sense for the Autobuilder as most people don't have
access to docs@.... Therefore, to allow for
From: Quentin Schulz <quentin.schulz@...>
The rsync only makes sense for the Autobuilder as most people don't have
access to docs@.... Therefore, to allow for
|
By
Quentin Schulz
·
#56809
·
|
|
[PATCH yocto-autobuilder-helper 2/6] scripts: run-docs-build: allow to pass buildtools script and docbook tarball paths
From: Quentin Schulz <quentin.schulz@...>
Currently, the path to buildtools script and docbook tarball are
hardcoded to work on Yocto Project Autobuilder. However, this makes
From: Quentin Schulz <quentin.schulz@...>
Currently, the path to buildtools script and docbook tarball are
hardcoded to work on Yocto Project Autobuilder. However, this makes
|
By
Quentin Schulz
·
#56808
·
|
|
[PATCH yocto-autobuilder-helper 1/6] scripts: run-docs-build: transform argument paths into absolute paths
From: Quentin Schulz <quentin.schulz@...>
The script is written in such a way that absolute paths are expected.
Instead of failing weirdly at some point in the script, let's just
From: Quentin Schulz <quentin.schulz@...>
The script is written in such a way that absolute paths are expected.
Instead of failing weirdly at some point in the script, let's just
|
By
Quentin Schulz
·
#56807
·
|
|
[RFC PATCH] docs: update Bitbake objects.inv location for master branch
From: Quentin Schulz <quentin.schulz@...>
master branch of Bitbake is now located at docs.yoctoproject.org/dev
instead of docs.yoctoproject.org so let's update the switchers
From: Quentin Schulz <quentin.schulz@...>
master branch of Bitbake is now located at docs.yoctoproject.org/dev
instead of docs.yoctoproject.org so let's update the switchers
|
By
Quentin Schulz
·
#56806
·
|
|
Yocto Project Status WW16`22
Current Dev Position: YP 4.0 rc3
Next Deadline: 29th April 2022 YP 4.0 final release
Next Team Meetings:
Bug Triage meeting Thursday Apr.21st 7:30 am PDT
Current Dev Position: YP 4.0 rc3
Next Deadline: 29th April 2022 YP 4.0 final release
Next Team Meetings:
Bug Triage meeting Thursday Apr.21st 7:30 am PDT
|
By
Richard Purdie
·
#56805
·
|
|
Re: NPM support on Dunfell
The takeaways using inherit npm:
1. Does not support 'scoped packages'
2. fetching is not multi-threaded. A NPM based recipe will run uni-proc with a considerable amount of overhead; each package is
The takeaways using inherit npm:
1. Does not support 'scoped packages'
2. fetching is not multi-threaded. A NPM based recipe will run uni-proc with a considerable amount of overhead; each package is
|
By
Joel Winarske
·
#56804
·
|
|
M+ & H bugs with Milestone Movements WW16
All,
YP M+ or high bugs which moved to a new milestone in WW16 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
12279
enhance manifest not found
All,
YP M+ or high bugs which moved to a new milestone in WW16 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
12279
enhance manifest not found
|
By
Stephen Jolley
·
#56803
·
|
|
Enhancements/Bugs closed WW16
All,
The below were the owners of enhancements or bugs closed during the last
All,
The below were the owners of enhancements or bugs closed during the last
|
By
Stephen Jolley
·
#56802
·
|