|
Re: [RFC][WIP]{honister] kernel-lab manual
Hi Tim
Many thanks for these instructions, and sorry for the late reply.
However, I wouldn't have forgotten to review it if you had copied the
docs@ mailing list ;-)
The whole instructions look very
Hi Tim
Many thanks for these instructions, and sorry for the late reply.
However, I wouldn't have forgotten to review it if you had copied the
docs@ mailing list ;-)
The whole instructions look very
|
By
Michael Opdenacker
·
#57188
·
|
|
Re: CVE metrics tracking from the autobuilder
Hi Anuj,
I will just disable it then, thanks for the info.
Cheers,
Richard
Hi Anuj,
I will just disable it then, thanks for the info.
Cheers,
Richard
|
By
Richard Purdie
·
#57187
·
|
|
Re: CVE metrics tracking from the autobuilder
Hi Richard,
This is very nice.
Yeah, there is only a week left and I wasn't planning to take those
patches in my final pull request.
Thanks,
Anuj
Hi Richard,
This is very nice.
Yeah, there is only a week left and I wasn't planning to take those
patches in my final pull request.
Thanks,
Anuj
|
By
Anuj Mittal
·
#57186
·
|
|
Need help in namespace journal implementation
Hi,
I am working on a yocto based project, I am trying to add namespace journal logging.
Can anyone share the steps to create a namespace journal logging in the yocto based project.
Also it would
Hi,
I am working on a yocto based project, I am trying to add namespace journal logging.
Can anyone share the steps to create a namespace journal logging in the yocto based project.
Also it would
|
By
Prashant Badsheshi <prashantsbemail@...>
·
#57185
·
|
|
CVE metrics tracking from the autobuilder
I'm happy to say that automatic CVE metric tracking is now on the
autobuilder and automatically feeding to:
https://autobuilder.yocto.io/pub/non-release/patchmetrics/
and the git repository that
I'm happy to say that automatic CVE metric tracking is now on the
autobuilder and automatically feeding to:
https://autobuilder.yocto.io/pub/non-release/patchmetrics/
and the git repository that
|
By
Richard Purdie
·
#57184
·
|
|
Re: [meta-security][PATCH] meta-parsec: Update Parsec runtime tests
Very nice. This is much better than what I did.
may thanks,
Armin
Very nice. This is much better than what I did.
may thanks,
Armin
|
By
Armin Kuster
·
#57183
·
|
|
[meta-security][PATCH] meta-parsec: Update Parsec runtime tests
Signed-off-by: Anton Antonov <Anton.Antonov@...>
---
meta-parsec/README.md | 65 +++++++++
meta-parsec/lib/oeqa/runtime/cases/parsec.py | 135 ++++++++++++++++--
Signed-off-by: Anton Antonov <Anton.Antonov@...>
---
meta-parsec/README.md | 65 +++++++++
meta-parsec/lib/oeqa/runtime/cases/parsec.py | 135 ++++++++++++++++--
|
By
Anton Antonov
·
#57182
·
|
|
OpenEmbedded Happy Hour May 25 5pm/1700 UTC
All,
You are cordially invited to the next OpenEmbedded Happy Hour on May 25
for Europe/Americas time zones @ 1700/5pm UTC (1pm ET / 10am
All,
You are cordially invited to the next OpenEmbedded Happy Hour on May 25
for Europe/Americas time zones @ 1700/5pm UTC (1pm ET / 10am
|
By
Tim Orling
·
#57181
·
|
|
[meta-selinux][master][kirkstone][PATCH 2/2] refpolicy: add file context for findfs alternative
Add file context for findfs alternative which is provided by util-linux.
Signed-off-by: Yi Zhao <yi.zhao@...>
---
...s-apply-policy-to-findfs-alternative.patch | 29 +++++++++++++++++++
Add file context for findfs alternative which is provided by util-linux.
Signed-off-by: Yi Zhao <yi.zhao@...>
---
...s-apply-policy-to-findfs-alternative.patch | 29 +++++++++++++++++++
|
By
Yi Zhao
·
#57180
·
|
|
[meta-selinux][master][kirkstone][PATCH 1/2] refpolicy: backport patches to fix policy issues for systemd 250
Backport the following patches to fix systemd-resolved and
systemd-netowrkd policy issues:
systemd-systemd-resolved-is-linked-to-libselinux.patch
Backport the following patches to fix systemd-resolved and
systemd-netowrkd policy issues:
systemd-systemd-resolved-is-linked-to-libselinux.patch
|
By
Yi Zhao
·
#57179
·
|
|
Re: [ANNOUNCEMENT] Yocto Project 4.0.1 is Released
This is in my to do list.
Chee Yang
This is in my to do list.
Chee Yang
|
By
Lee Chee Yang
·
#57178
·
|
|
Enhancements/Bugs closed WW21
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
michael.opdenacker@...
2
mhalstead@...
1
Grand Total
3
Thanks,
Stephen K. Jolley
Yocto
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
michael.opdenacker@...
2
mhalstead@...
1
Grand Total
3
Thanks,
Stephen K. Jolley
Yocto
|
By
Stephen Jolley
·
#57177
·
|
|
Current high bug count owners for Yocto Project 4.1
All,
Below is the list as of top 36 bug owners as of the end of WW21 of who have open medium or higher bugs and enhancements against YP 4.1. There are 110 possible work days left until the final
All,
Below is the list as of top 36 bug owners as of the end of WW21 of who have open medium or higher bugs and enhancements against YP 4.1. There are 110 possible work days left until the final
|
By
Stephen Jolley
·
#57176
·
|
|
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
·
#57175
·
|
|
Yocto Project Status WW21`22
Current Dev Position: YP 4.1 M1
Next Deadline: 30th May 2022 YP 4.1 M1 Build
Next Team Meetings:
Bug Triage meeting Thursday May 26th 7:30 am PDT
Current Dev Position: YP 4.1 M1
Next Deadline: 30th May 2022 YP 4.1 M1 Build
Next Team Meetings:
Bug Triage meeting Thursday May 26th 7:30 am PDT
|
By
Stephen Jolley
·
#57174
·
|
|
Yocto-generated image does not pass the systemd-boot bootloader
Good morning,
I generated a Linux Image by following the intel document "Yocto Project*-based Board Support Package for Intel Atom® x6000E Series, and Intel® Pentium® and Celeron® N and J Series
Good morning,
I generated a Linux Image by following the intel document "Yocto Project*-based Board Support Package for Intel Atom® x6000E Series, and Intel® Pentium® and Celeron® N and J Series
|
By
lucas@...
·
#57173
·
|
|
Re: [ANNOUNCEMENT] Yocto Project 4.0.1 is Released
Hi Lee and others
Many thanks for the new release!
Now that we also have release notes in the documentation (see
https://docs.yoctoproject.org/migration-guides/release-notes-3.4.2.html
for example,
Hi Lee and others
Many thanks for the new release!
Now that we also have release notes in the documentation (see
https://docs.yoctoproject.org/migration-guides/release-notes-3.4.2.html
for example,
|
By
Michael Opdenacker
·
#57172
·
|
|
Re: Building rust package fails with "can't find crate for `std`"
#bitbake
#toolchain
#rust
#kirkstone
Forgot to mention that the build machine is x86_64 and I want to build for target aarch64.
This is the generated bitbake recipe:
# Auto-Generated by cargo-bitbake 0.3.15
#
inherit cargo pkgconfig
# If
Forgot to mention that the build machine is x86_64 and I want to build for target aarch64.
This is the generated bitbake recipe:
# Auto-Generated by cargo-bitbake 0.3.15
#
inherit cargo pkgconfig
# If
|
By
martin.stolpe@...
·
#57171
·
|
|
Re: Building rust package fails with "can't find crate for `std`"
#bitbake
#toolchain
#rust
#kirkstone
It helps if you can share the recipe that you're trying to build.
Alex
It helps if you can share the recipe that you're trying to build.
Alex
|
By
Alexander Kanavin
·
#57170
·
|
|
Building rust package fails with "can't find crate for `std`"
#bitbake
#toolchain
#rust
#kirkstone
Hello,
I'm trying to build a rust package which pulls openssl-sys as a dependency. I've used cargo bitbake to create the build script.
When I try to build the package using bitbake I get the following
Hello,
I'm trying to build a rust package which pulls openssl-sys as a dependency. I've used cargo bitbake to create the build script.
When I try to build the package using bitbake I get the following
|
By
martin.stolpe@...
·
#57169
·
|