|
Re: [meta-security][PATCH 1/1] LICENSE: adopt standard SPDX names
Mater-next has these.
https://git.yoctoproject.org/meta-security/commit/?h=master-next&id=ece41f7543bbd42c57f4208c7309f90cbd02e852
Looks like a few more need to be added based on these
Mater-next has these.
https://git.yoctoproject.org/meta-security/commit/?h=master-next&id=ece41f7543bbd42c57f4208c7309f90cbd02e852
Looks like a few more need to be added based on these
|
By
Armin Kuster
·
#56583
·
|
|
Re: [meta-security][PATCH] openscap-daemon: inherit python_setuptools_build_meta
I believe this is sitting in master-next.
https://git.yoctoproject.org/meta-security/commit/?h=master-next&id=398047a7a6310b1ef70d22430fb6df4effd8cf92
I believe this is sitting in master-next.
https://git.yoctoproject.org/meta-security/commit/?h=master-next&id=398047a7a6310b1ef70d22430fb6df4effd8cf92
|
By
Armin Kuster
·
#56582
·
|
|
Re: Strange sporadic build issues (incremental builds in docker container)
Yes I've been seeing exactly these issues as well.
I'm not using any sort of virtualization, I'm using Jenkins to do nightly
builds directly on my host. My host machine is openSUSE 15.3. These
Yes I've been seeing exactly these issues as well.
I'm not using any sort of virtualization, I'm using Jenkins to do nightly
builds directly on my host. My host machine is openSUSE 15.3. These
|
By
Trevor Woerner
·
#56581
·
|
|
[meta-security][PATCH 1/1] LICENSE: adopt standard SPDX names
Correct LICENSE for samhain, ecrypt-utils, ding-libs,
libmhash, and sssd.
Signed-off-by: Joe Slater <joe.slater@...>
---
recipes-ids/samhain/samhain.inc | 2 +-
Correct LICENSE for samhain, ecrypt-utils, ding-libs,
libmhash, and sssd.
Signed-off-by: Joe Slater <joe.slater@...>
---
recipes-ids/samhain/samhain.inc | 2 +-
|
By
Joe Slater <joe.slater@...>
·
#56580
·
|
|
[PATCH yocto-autobuilder-helper] config.json: no need to explicitly exclude the NPM tests
These tests now skip themselves automatically[1] if meta-oe isn't
present, so there is no need to explicitly skip them.
[1] oe-core d22ed015d8f38241acb783e1a468fb15d4317670
Signed-off-by: Ross
These tests now skip themselves automatically[1] if meta-oe isn't
present, so there is no need to explicitly skip them.
[1] oe-core d22ed015d8f38241acb783e1a468fb15d4317670
Signed-off-by: Ross
|
By
Ross Burton <ross@...>
·
#56579
·
|
|
Yocto Project Status WW132`22
Current Dev Position: YP 3.5 M4
Next Deadline: 4th April. 2022 YP 3.5 M4 build
Next Team Meetings:
Bug Triage meeting Thursday Mar. 31st 7:30 am PDT
Current Dev Position: YP 3.5 M4
Next Deadline: 4th April. 2022 YP 3.5 M4 build
Next Team Meetings:
Bug Triage meeting Thursday Mar. 31st 7:30 am PDT
|
By
Stephen Jolley
·
#56578
·
|
|
Yocto poky/meta/recipes-devtool/perl
Hi,I have the question: is anybody aware that patches in a recipe are not fully applied?
When retrieved the archive for package unpacked.
Аttributes of multiple files are set as readonly.
For
Hi,I have the question: is anybody aware that patches in a recipe are not fully applied?
When retrieved the archive for package unpacked.
Аttributes of multiple files are set as readonly.
For
|
By
Mike Ulan
·
#56577
·
|
|
Re: [OE-core] Which vendors maintain SDIO WiFi in mainline stable kernel
Hi Jupiter,
The QCA9377 is well supported in the mainline kernel by the ath10k driver:
drivers/net/wireless/ath/ath10k/
Just use 5.10 or 5.15 stable tree and there will be no need to use
Hi Jupiter,
The QCA9377 is well supported in the mainline kernel by the ath10k driver:
drivers/net/wireless/ath/ath10k/
Just use 5.10 or 5.15 stable tree and there will be no need to use
|
By
Fabio Estevam <festevam@...>
·
#56576
·
|
|
Re: [OE-core] Which vendors maintain SDIO WiFi in mainline stable kernel
Hi Jupiter,
I cannot help you on the specific chip you ask, but responding to the second part of your question I have quite good experience with Microchip WILC1000/3000 on SDIO which, after a part
Hi Jupiter,
I cannot help you on the specific chip you ask, but responding to the second part of your question I have quite good experience with Microchip WILC1000/3000 on SDIO which, after a part
|
By
Federico Pellegrin
·
#56575
·
|
|
Which vendors maintain SDIO WiFi in mainline stable kernel
Hi,
I could not understand why so many large WiFi chip vendors retreat to
stop maintaining WiFi SDIO chips to mainline Linux kernel, and to
settle it's chip support to out of the tree, use its own
Hi,
I could not understand why so many large WiFi chip vendors retreat to
stop maintaining WiFi SDIO chips to mainline Linux kernel, and to
settle it's chip support to out of the tree, use its own
|
By
JH
·
#56574
·
|
|
M+ & H bugs with Milestone Movements WW13
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+
5322
Global DNS fallback mechanism not
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+
5322
Global DNS fallback mechanism not
|
By
Stephen Jolley
·
#56573
·
|
|
Enhancements/Bugs closed WW13!
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
·
#56572
·
|
|
Current high bug count owners for Yocto Project 3.5
All,
Below is the list as of top 39 bug owners as of the end of WW13 of who have open medium or higher bugs and enhancements against YP 3.5. There are 23 possible work days left until the final
All,
Below is the list as of top 39 bug owners as of the end of WW13 of who have open medium or higher bugs and enhancements against YP 3.5. There are 23 possible work days left until the final
|
By
Stephen Jolley
·
#56571
·
|
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
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
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
|
By
Stephen Jolley
·
#56570
·
|
|
psplash: Wrong spashscreen resolution in case of two displays with different resolution
Hi,
In my system I have two displays (virtual) with different resolution
first: 1080x1920 (portrait orientation)
second: 640x720
When psplash is run, it shows boot animation with resolution 640x720
Hi,
In my system I have two displays (virtual) with different resolution
first: 1080x1920 (portrait orientation)
second: 640x720
When psplash is run, it shows boot animation with resolution 640x720
|
By
Vasyl Vavrychuk
·
#56569
·
|
|
Re: QA notification for completed autobuilder build (yocto-3.4.3.rc1)
Hello everyone,
This is the full report for yocto-3.4.3.rc3:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
======= Summary ========
No high
Hello everyone,
This is the full report for yocto-3.4.3.rc3:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
======= Summary ========
No high
|
By
Teoh, Jay Shen
·
#56568
·
|
|
Re: firewalld isssue
#yocto
Judging by this stack exchange thread[1] from a quick search, you might
be missing the appropriate kernel configs[2].
[1]: https://unix.stackexchange.com/questions/632113
[2]:
Judging by this stack exchange thread[1] from a quick search, you might
be missing the appropriate kernel configs[2].
[1]: https://unix.stackexchange.com/questions/632113
[2]:
|
By
Nicolas Jeker
·
#56567
·
|
|
Re: CVE patch updates
lists.yoctoproject.org wrote:
If you look at the source for cve-update-db-native.bb[1], you see how
the URLs are being generated. It tries to send requests to the
following URLs (if you didn't change
lists.yoctoproject.org wrote:
If you look at the source for cve-update-db-native.bb[1], you see how
the URLs are being generated. It tries to send requests to the
following URLs (if you didn't change
|
By
Nicolas Jeker
·
#56566
·
|
|
firewalld isssue
#yocto
Hi Team,
I have built a custom image core-image-base on riscv target machine installed nftables,firewalld,JSON packages support. I am using firewalld_0.9.3 sources depends
Hi Team,
I have built a custom image core-image-base on riscv target machine installed nftables,firewalld,JSON packages support. I am using firewalld_0.9.3 sources depends
|
By
sateesh m
·
#56565
·
|
|
firewalld isssue
#yocto
Hi Team,
I have built a custom image core-image-base with nftables,firewalld,json packages support. I am using firewalld_0.9.3 sources depends nftables-python is present. But I am
Hi Team,
I have built a custom image core-image-base with nftables,firewalld,json packages support. I am using firewalld_0.9.3 sources depends nftables-python is present. But I am
|
By
sateesh m
·
#56564
·
|