|
[meta-security][PATCH] suricata: update to 6.0.3
add new crates
minor cleanup
Signed-off-by: Armin Kuster <akuster808@...>
---
.../{libhtp_0.5.37.bb => libhtp_0.5.38.bb} | 2 +-
.../meta-rust/recipes-ids/suricata/suricata.inc | 5
add new crates
minor cleanup
Signed-off-by: Armin Kuster <akuster808@...>
---
.../{libhtp_0.5.37.bb => libhtp_0.5.38.bb} | 2 +-
.../meta-rust/recipes-ids/suricata/suricata.inc | 5
|
By
Armin Kuster
·
#54067
·
|
|
Re: [meta-mingw][PATCH] openssl: support for building nativesdk of mingw
On 1/4/21 9:31 PM, Changqing Li wrote:
It would appear that some or all of this patch is unnecessary. OE-core 166bb89f6d97495b6522786182b4f9623acd7ff4 implements part of this patch,
On 1/4/21 9:31 PM, Changqing Li wrote:
It would appear that some or all of this patch is unnecessary. OE-core 166bb89f6d97495b6522786182b4f9623acd7ff4 implements part of this patch,
|
By
Joshua Watt
·
#54066
·
|
|
Yocto Technical Team Minutes, Engineering Sync, for July 6, 2021
Yocto Technical Team Minutes, Engineering Sync, for July 6, 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit
== disclaimer ==
Best efforts are made
Yocto Technical Team Minutes, Engineering Sync, for July 6, 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit
== disclaimer ==
Best efforts are made
|
By
Trevor Woerner
·
#54065
·
|
|
[PATCH yocto-autobuilder-helper] config.json: add meta-arm-autonomy to check-layer
meta-arm-autonomy now passes check-layer, so add it to the autobuilder.
Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
meta-arm-autonomy now passes check-layer, so add it to the autobuilder.
Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
|
By
Ross Burton <ross@...>
·
#54064
·
|
|
Yocto Project Status WW27`21
Current Dev Position: YP 3.4 M2
Next Deadline: 12th July 2021 YP 3.4 M2 build
Next Team Meetings:
Bug Triage meeting Thursday July 8th at 7:30am PDT
Current Dev Position: YP 3.4 M2
Next Deadline: 12th July 2021 YP 3.4 M2 build
Next Team Meetings:
Bug Triage meeting Thursday July 8th at 7:30am PDT
|
By
Stephen Jolley
·
#54063
·
|
|
M+ & H bugs with Milestone Movements WW27
All,
YP M+ or high bugs which moved to a new milestone in WW27 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
10693
Add a testcase for multilib eSDK on
All,
YP M+ or high bugs which moved to a new milestone in WW27 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
10693
Add a testcase for multilib eSDK on
|
By
Stephen Jolley
·
#54062
·
|
|
Enhancements/Bugs closed WW27!
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
·
#54061
·
|
|
Current high bug count owners for Yocto Project 3.4
All,
Below is the list as of top 50 bug owners as of the end of WW27 of who have open medium or higher bugs and enhancements against YP 3.4. There are 82 possible work days left until the final
All,
Below is the list as of top 50 bug owners as of the end of WW27 of who have open medium or higher bugs and enhancements against YP 3.4. There are 82 possible work days left until the final
|
By
Stephen Jolley
·
#54060
·
|
|
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
·
#54059
·
|
|
Re: Integration of Docker in Read-only Rootfile system through Yocto
Greetings !
I am trying to integrate Docker in Yocto. (Yocto Zeus) . I could able to add Docker in yocto and it is working as expected in the Rootfile system which is having "Read-write" permission .
Greetings !
I am trying to integrate Docker in Yocto. (Yocto Zeus) . I could able to add Docker in yocto and it is working as expected in the Rootfile system which is having "Read-write" permission .
|
By
Poornesh <poornesh.g@...>
·
#54058
·
|
|
Re: [meta-security][PATCH 2/2] apparmor: use its own initscript and service files
Ping ...
On 6/23/21 5:15 PM, Yi Zhao wrote:
Ping ...
On 6/23/21 5:15 PM, Yi Zhao wrote:
|
By
Yi Zhao
·
#54057
·
|
|
Re: QEMU Size Increase from Yocto Thud to Zeus
Hello Ross,
Thanks ! I was able to reduce the size of the image by modifying the QEMU_TARGETS variable.. but on enabling buildhistory and checking under installed-image-sizes.txt , the individual
Hello Ross,
Thanks ! I was able to reduce the size of the image by modifying the QEMU_TARGETS variable.. but on enabling buildhistory and checking under installed-image-sizes.txt , the individual
|
By
Aashik Aswin
·
#54056
·
|
|
Re: meta-parsec build failure
yeah perhaps you need to fork this repo and let main package know via
editing the toml file perhaps.
yeah perhaps you need to fork this repo and let main package know via
editing the toml file perhaps.
|
By
Khem Raj
·
#54055
·
|
|
Re: meta-parsec build failure
I would love to try that out, Where would I apply that?
mbedtls is a dependent create to a dependent create to parsec-service
recipe. The Rust paradigm in OE does make my head hurt.
-armin
I would love to try that out, Where would I apply that?
mbedtls is a dependent create to a dependent create to parsec-service
recipe. The Rust paradigm in OE does make my head hurt.
-armin
|
By
Armin Kuster
·
#54054
·
|
|
Re: meta-parsec build failure
yeah perhaps try using -DMBEDTLS_FATAL_WARNINGS=OFF
yeah perhaps try using -DMBEDTLS_FATAL_WARNINGS=OFF
|
By
Khem Raj
·
#54053
·
|
|
meta-parsec build failure
The parsec-service in meta-parsec has been failing ever since gcc 11 was
merged into core.
https://errors.yoctoproject.org/Errors/Build/123537/
I have already opened an issue with
The parsec-service in meta-parsec has been failing ever since gcc 11 was
merged into core.
https://errors.yoctoproject.org/Errors/Build/123537/
I have already opened an issue with
|
By
Armin Kuster
·
#54052
·
|
|
[yocto-autobuilder-helper][dunfell] config.json: Switch to newer buildtools-extended-tarball
From: Richard Purdie <richard.purdie@...>
This adds locale information which should fix reproducibility issues with vim.
Signed-off-by: Richard Purdie
From: Richard Purdie <richard.purdie@...>
This adds locale information which should fix reproducibility issues with vim.
Signed-off-by: Richard Purdie
|
By
Steve Sakoman
·
#54051
·
|
|
How to handle build time dependencies on native python modules?
Hi,
I ran into the following situation and I am wondering, what the "correct"
way of handling such a setup is?
We have an application that is embedding Python 3 in order to allow users to
modify app
Hi,
I ran into the following situation and I am wondering, what the "correct"
way of handling such a setup is?
We have an application that is embedding Python 3 in order to allow users to
modify app
|
By
Sergey Bostandzhyan
·
#54050
·
|
|
Re: Upgrading connman to a version over 1.37 fails to build.
1.40 is already in oe-core master you should be able to backport the recipe from there.
libnml dependency was already added with wireguard PACKAGECONFIG in 1.38
1.40 is already in oe-core master you should be able to backport the recipe from there.
libnml dependency was already added with wireguard PACKAGECONFIG in 1.38
|
By
Martin Jansa
·
#54049
·
|
|
Upgrading connman to a version over 1.37 fails to build.
Hi,
I'm trying to upgrade our connman recipe to 1.39 or 1.40 version, but when I try to build our image, it fails in "do_configure" because it can't find libmnl.
This is the exact output of my
Hi,
I'm trying to upgrade our connman recipe to 1.39 or 1.40 version, but when I try to build our image, it fails in "do_configure" because it can't find libmnl.
This is the exact output of my
|
By
Moya, Ignacio
·
#54048
·
|