|
[PATCH yocto-autobuilder-helper 4/6] scripts: run-docs-build: automatically build new yocto-docs branches
From: Quentin Schulz <quentin.schulz@...>
Since commit 01dd5af7954e24552aca022917669b27bb0541ed, all later
releases of yocto-docs can be built with Sphinx. Instead of
From: Quentin Schulz <quentin.schulz@...>
Since commit 01dd5af7954e24552aca022917669b27bb0541ed, all later
releases of yocto-docs can be built with Sphinx. Instead of
|
By
Quentin Schulz
·
#56492
·
|
|
[PATCH yocto-autobuilder-helper 3/6] scripts: run-docs-build: factor out all yocto-docs branches building
From: Quentin Schulz <quentin.schulz@...>
master, master-next and transition only differ from other branches by
their output directory name. Let's put everything in common and
From: Quentin Schulz <quentin.schulz@...>
master, master-next and transition only differ from other branches by
their output directory name. Let's put everything in common and
|
By
Quentin Schulz
·
#56491
·
|
|
[PATCH yocto-autobuilder-helper 2/6] scripts: run-docs-build: automatically build new Bitbake branches
From: Quentin Schulz <quentin.schulz@...>
Since commit 84ccba0f4aff91528f764523fe1205a354c889ed, docs of all later
releases can be built with Sphinx. Instead of manually updating
From: Quentin Schulz <quentin.schulz@...>
Since commit 84ccba0f4aff91528f764523fe1205a354c889ed, docs of all later
releases can be built with Sphinx. Instead of manually updating
|
By
Quentin Schulz
·
#56490
·
|
|
[PATCH yocto-autobuilder-helper 1/6] scripts: run-docs-build: factor out all bitbake branches building
From: Quentin Schulz <quentin.schulz@...>
master and master-next only differ from other branches by their output
directory name. Let's put everything in common and only have a check
From: Quentin Schulz <quentin.schulz@...>
master and master-next only differ from other branches by their output
directory name. Let's put everything in common and only have a check
|
By
Quentin Schulz
·
#56489
·
|
|
Re: [meta-security][PATCH] python3-privacyidea_3.6.2: remove more py3 that got dropped
I'd hold off that, these just moved to core?
Cheers,
Richard
I'd hold off that, these just moved to core?
Cheers,
Richard
|
By
Richard Purdie
·
#56488
·
|
|
[meta-security][PATCH] python3-privacyidea_3.6.2: remove more py3 that got dropped
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-security/mfa/python3-privacyidea_3.6.2.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-security/mfa/python3-privacyidea_3.6.2.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
|
By
Armin Kuster
·
#56487
·
|
|
Re: QA notification for completed autobuilder build (yocto-3.1.15.rc1)
Hi All,
This is the full report for yocto-3.1.15.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
======= Summary ========
No high
Hi All,
This is the full report for yocto-3.1.15.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
======= Summary ========
No high
|
By
Teoh, Jay Shen
·
#56486
·
|
|
Multiconfig dependency
Hello guys!
Could you please help me with Multiconfig setup?
I’ve "default" configuration with SystemD by default.
And "initramfs" configuration with Busybox and other settings.
I use next
Hello guys!
Could you please help me with Multiconfig setup?
I’ve "default" configuration with SystemD by default.
And "initramfs" configuration with Busybox and other settings.
I use next
|
By
Oleh Kravchenko
·
#56485
·
|
|
do_image_wic error with custom machine
Hello,
I would like to implement two custom machines based on genericx86_64 but I have issue with the do_image_wic
Couldn't get bitbake variable from
Hello,
I would like to implement two custom machines based on genericx86_64 but I have issue with the do_image_wic
Couldn't get bitbake variable from
|
By
Goubaux, Nicolas
·
#56484
·
|
|
Re: Minutes: Yocto Project Weekly Triage Meeting 3/17/2022
On 2022-03-17 11:28, Trevor Gamblin wrote:
Done.
../Randy
-- # Randy MacLeod# Wind River Linux
On 2022-03-17 11:28, Trevor Gamblin wrote:
Done.
../Randy
-- # Randy MacLeod# Wind River Linux
|
By
Randy MacLeod
·
#56483
·
|
|
Re: Minutes: Yocto Project Weekly Triage Meeting 3/17/2022
AR completed.
Stephen
By
Stephen Jolley
·
#56482
·
|
|
Minutes: Yocto Project Weekly Triage Meeting 3/17/2022
Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage
Attendees: Alexandre, Daiane, Luca, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor
ARs:
- Randy to move
Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage
Attendees: Alexandre, Daiane, Luca, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor
ARs:
- Randy to move
|
By
Trevor Gamblin
·
#56481
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
Ah, that's an interesting information.
The dmesg log gives the impression that virgl starts correctly and in the normal shell the examples work flawlessly. The problems start once I tell weston to use
Ah, that's an interesting information.
The dmesg log gives the impression that virgl starts correctly and in the normal shell the examples work flawlessly. The problems start once I tell weston to use
|
By
Edgar Mobile
·
#56480
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
There is no hardware acceleration with bochs at all, if you want it,
you need to make virtio/virgl driver work.
Alex
There is no hardware acceleration with bochs at all, if you want it,
you need to make virtio/virgl driver work.
Alex
|
By
Alexander Kanavin
·
#56479
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
Do you know if bochs driver is available and active for yocto 3.4 or 3.5?
From: Alexander Kanavin <alex.kanavin@...>
Sent: Thursday, March 17, 2022 11:26 AM
To: Edgar Mobile <heideggm@...>
Cc:
Do you know if bochs driver is available and active for yocto 3.4 or 3.5?
From: Alexander Kanavin <alex.kanavin@...>
Sent: Thursday, March 17, 2022 11:26 AM
To: Edgar Mobile <heideggm@...>
Cc:
|
By
Edgar Mobile
·
#56478
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
As I told you, we do not support or test this combination. Which means
that figuring out what the error messages mean and how to fix them is
on you - patches welcome.
Alex
As I told you, we do not support or test this combination. Which means
that figuring out what the error messages mean and how to fix them is
on you - patches welcome.
Alex
|
By
Alexander Kanavin
·
#56477
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
I tried that first and it was horribly slow. That's why I try hardware acceleration now.
Do you _know_ it doesn't work? If yes, why?
From: Alexander Kanavin <alex.kanavin@...>
Sent: Thursday, March
I tried that first and it was horribly slow. That's why I try hardware acceleration now.
Do you _know_ it doesn't work? If yes, why?
From: Alexander Kanavin <alex.kanavin@...>
Sent: Thursday, March
|
By
Edgar Mobile
·
#56476
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
If you want an aarch guest on x86, then drop the gl option from
runqemu. This will fall back to software rendering.
Alex
If you want an aarch guest on x86, then drop the gl option from
runqemu. This will fall back to software rendering.
Alex
|
By
Alexander Kanavin
·
#56475
·
|
|
Re: runqemu - ERROR - Failed to run qemu: qemu-system-aarch64: Virtio VGA not available.
Sorry, but I need an Aarch64 guest.
Ok, using a newer qemu I now encounter the following problem:
root@qemuarm64:/usr/bin# XDG_RUNTIME_DIR=/run/user/0 ./eglinfo
EGL client extensions string:
Sorry, but I need an Aarch64 guest.
Ok, using a newer qemu I now encounter the following problem:
root@qemuarm64:/usr/bin# XDG_RUNTIME_DIR=/run/user/0 ./eglinfo
EGL client extensions string:
|
By
Edgar Mobile
·
#56474
·
|
|
[meta-openssl102-fips][dunfell][PATCH 2/2] openssh: Adapt the patch for CVE-2020-14145 fix on poky/dunfell
From: Harshal Gohel <harshaldhruvkumar.gohel@...>
openssh-8.2p1-fips.patch does not apply after CVE-2020-14145 patch
introduced in (poky:
From: Harshal Gohel <harshaldhruvkumar.gohel@...>
openssh-8.2p1-fips.patch does not apply after CVE-2020-14145 patch
introduced in (poky:
|
By
Harshal Gohel
·
#56473
·
|