A build flagged for QA (yocto-4.3.rc2) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-4.3.rc2
Build URL:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6080
Build hash information:
bitbake: 5
In case busybox's "find" utility is not sufficient for you, you could
disable "find" in busybox's config, and add the full version of find to
your image (recipe is called findutils).
On 10/20/23 07:38, Poornesh G ( India - Bangalore ) wrote:
Greetings !
I am trying to add "etckeeper" to yoc
Greetings !
I am trying to add "etckeeper" to yocto . I have written a recipe and added it
in my Rootfs . But when I try to commit , I am getting the below error log:
-
root@imx6ulevk:~# etckeeper c
On 10/18/23 10:06, Changqing Li wrote:
From: Changqing Li
Since oe-core commit 26d97acc713 [image-artifact-names: include
${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and
${IMAGE_LINK_NAME}], image name has changed to
core-image-minimal-qemux86.rootfs.ext4, change accordingly to fix erro
Fixes dropdown menus so they are functional again.
Signed-off-by: Tim Orling
---
.../static/js/{boostrap-3.4.1.min.js => bootstrap-3.4.1.min.js} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename layerindex/static/js/{boostrap-3.4.1.min.js => bootstrap-3.4.1.min.js}
(100%)
diff --g
On Thu, 2023-10-19 at 14:06 +, Jing Hui Tham wrote:
> Hi all,
>
> Intel and WR YP QA is planning for QA execution for YP build yocto-4.3.rc1.
> We are planning to execute following tests for this cycle:
>
> OEQA-manual tests for following module:
> 1. OE-Core
> 2. BSP-hw
>
> Runtime auto
Hi Darek
Making the recipe compiling for cross and native and adding a DEPENDS from
cross to native seems to be the cleanest and most Yocto-ish way to me.
Alternatively this patch would allow to run cross compiled executables with
Qemu in the cmake project
https://git.yoctoproject.org/poky-contri
On Wed, 2023-10-18 at 07:43 +0200, Marta Rybczynska wrote:
> Hello all,
> There' a discussion pending on the usage of SRTool and CVE management
> for the Yocto project in general. It is related to the need of having
> a list of CVEs the project is affected by, those fixed and those that
> we know w
Hello all,
So I have a cmake project that uses an executable generated from a cmake
subproject.
My architecture is as such
├── ProjectA
├── projecta_1.0.bb ( http://projecta_1.0.bb/ )
├── files
├── ProjectA
├── CMakeLists.txt
├── ProjectB
├── CMakeLists.txt
My recipe is a standard recipe that in
This is now done with a dedicated switch, where previously the file was always
written
out, creating often unneeded clutter.
Signed-off-by: Alexander Kanavin
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.json b/config.json
index 94c86e1..ea6885d 1006
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-4.3.rc1. We
are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
On Thu, 2023-10-19 at 12:52 +0100, Richard Purdie via
lists.yoctoproject.org wrote:
> On Thu, 2023-10-19 at 11:58 +0100, Richard Purdie via
> lists.yoctoproject.org wrote:
> > On Wed, 2023-10-18 at 15:46 +0200, David Pierret wrote:
> > > Inspired from trigger-build and trigger-build-post-trigger
>
On Thu, 2023-10-19 at 14:28 +0200, Alexis Lothoré wrote:
> Hi Ross,
> On 10/19/23 13:04, Ross Burton wrote:
> > > On 19 Oct 2023, at 09:36, Alexis Lothoré via lists.yoctoproject.org
> > > wrote:
> > I just skimmed your report and have some feedback to hopefully make it
> > easier to read in the
Hi Ross,
On 10/19/23 13:04, Ross Burton wrote:
>> On 19 Oct 2023, at 09:36, Alexis Lothoré via lists.yoctoproject.org
>> wrote:
> I just skimmed your report and have some feedback to hopefully make it easier
> to read in the future.
>
> I’d suggest sorting the output in order of importance. Fo
On Thu, 2023-10-19 at 10:36 +0200, Alexis Lothoré wrote:
> Hello,
>
> On 10/18/23 08:16, Pokybuild User wrote:
> >
> > A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder
> > and is available at:
> >
> >
> > https://autobuilder.yocto.io/pub/releases/yocto-4.3.rc
On Thu, 2023-10-19 at 11:58 +0100, Richard Purdie via
lists.yoctoproject.org wrote:
> On Wed, 2023-10-18 at 15:46 +0200, David Pierret wrote:
> > Inspired from trigger-build and trigger-build-post-trigger
> > The branch must be selected on build configuration.
> >
> > Signed-off-by: David Pierret
Hi Alexis,
> On 19 Oct 2023, at 09:36, Alexis Lothoré via lists.yoctoproject.org
> wrote:
> The regression report looks worryingly empty. It has been generated with
> yocto-4.2 as comparison base. When taking a look at yocto-testresults content
> for it, I only find a few test results (11, while
On Wed, 2023-10-18 at 15:46 +0200, David Pierret wrote:
> Inspired from trigger-build and trigger-build-post-trigger
> The branch must be selected on build configuration.
>
> Signed-off-by: David Pierret
> Reviewed-by: Yoann Congal
> ---
> config.json | 30 ++
> 1 fi
This way explicitly listing the test can be avoided, especially when more tests
of the same kind will be added (such as te CDN sstate cache mirror test).
Signed-off-by: Alexander Kanavin
---
config.json | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/config.json b/confi
Hello,
On 10/18/23 08:16, Pokybuild User wrote:
>
> A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder
> and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-4.3.rc1
The regression report looks worryingly empty. It has been generated with
Le jeu. 19 oct. 2023 à 01:22, Jose Quaresma a écrit :
> Hi Yoann,
Hi!
> I have found the same for BBLAYERS that was fixed [1] expanding any relative
> path that could exist.
> Maybe it would be better to also expand BB_LOGCONFIG when the newbuilddir
> argument is present.
>
> [1]
> https://gi
21 matches
Mail list logo
