From: Chen Qi
Set CVE_PRODUCT and CVE_VERSION for ovmf. NVD uses 'edk2' and the
version should be the date only. Here's an example:
https://nvd.nist.gov/vuln/detail/CVE-2023-45232
Signed-off-by: Chen Qi
---
meta/recipes-core/ovmf/ovmf_git.bb | 3 +++
1 file changed, 3 insertions(+)
diff
On Wed, 6 Mar 2024 at 05:33, Chen Qi via lists.openembedded.org
wrote:
> +CVE_VERSION = "202308"
This will almost certainly become mismatched with PV on version
updates, so please set from PV with a helper function.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this
From: Chen Qi
Set CVE_PRODUCT and CVE_VERSION for ovmf. NVD uses 'edk2' and the
version should be the date only. Here's an example:
https://nvd.nist.gov/vuln/detail/CVE-2023-45232
Signed-off-by: Chen Qi
---
meta/recipes-core/ovmf/ovmf_git.bb | 3 +++
1 file changed, 3 insertions(+)
diff
From: Fabio Estevam
Mesa 24.0.2 release notes:
https://lists.freedesktop.org/archives/mesa-announce/2024-February/000751.html
Signed-off-by: Fabio Estevam
---
.../mesa/{mesa-gl_24.0.1.bb => mesa-gl_24.0.2.bb} | 0
meta/recipes-graphics/mesa/mesa.inc
Hi,
I checked on kirkstone using OE-Core with DISTRO="nodistro" and when
running bitbake useradd-example I can see this:
configuration error - unknown item 'SYSLOG_SU_ENAB' (notify administrator)
configuration error - unknown item 'SYSLOG_SG_ENAB' (notify administrator)
in the
On Tue, 2024-03-05 at 14:36 -0600, Tom Hochstein wrote:
> The rename of bmap-tools to bmaptool creates an incompatibility for
> pre-scarthgap layers. Restore compatibility by adding bmap-tools as
> an alias.
>
> Acked-by: Otavio Salvador
> Signed-off-by: Tom Hochstein
> ---
>
From: Chen Qi
The clear text password support has been dropped. So let's just
use a normal ecrypted one. The password remains to be 'user3'.
Signed-off-by: Chen Qi
Signed-off-by: Richard Purdie
(cherry picked from commit cd8232f9c58980d95180ad320b7b0bb0fcfd9ff5)
Signed-off-by: Fabio Berton
The 'FIXME' comment itself says to remove this once the minimum bitbake
version has been bumped. This was in 2012.
The function was introduced in bitbake commit f7b55a94 ("bitbake:
bitbake: ensure -f causes dependent tasks to be re-run") and is already
part of bitbake 1.15.3 which is the minimum
When modifying the kernel config by invoking '-c menuconfig' manually, a
sensible next step is to persist this changed configuration somewhere.
A way to do this is to copy the generated .config back to the original
config location.
For this purpose, emit a copy+pasteable printout of the saved
The rename of bmap-tools to bmaptool creates an incompatibility for
pre-scarthgap layers. Restore compatibility by adding bmap-tools as an
alias.
Acked-by: Otavio Salvador
Signed-off-by: Tom Hochstein
---
meta/recipes-support/bmaptool/bmaptool_git.bb | 8
1 file changed, 8
Since commit 7a036b1a1ec7 ("bmaptool: now part of Yocto Project")
'bmap-tools-native' has been renamed as 'bmaptool-native'.
Adjust the references in the documentation accordingly.
Suggested-by: Khem Raj
Signed-off-by: Fabio Estevam
---
Changes since v1:
- Add d...@lists.yoctoproject.org on Cc
I wonder if it should go to docs ml too
On Tue, Mar 5, 2024 at 11:46 AM Khem Raj wrote:
>
> Thanks for doing this quickly.
>
> On Tue, Mar 5, 2024 at 11:46 AM Fabio Estevam wrote:
> >
> > Since commit 7a036b1a1ec7 ("bmaptool: now part of Yocto Project")
> > 'bmap-tools-native' has been renamed
Thanks for doing this quickly.
On Tue, Mar 5, 2024 at 11:46 AM Fabio Estevam wrote:
>
> Since commit 7a036b1a1ec7 ("bmaptool: now part of Yocto Project")
> 'bmap-tools-native' has been renamed as 'bmaptool-native'.
>
> Adjust the references in the documentation accordingly.
>
> Suggested-by:
Since commit 7a036b1a1ec7 ("bmaptool: now part of Yocto Project")
'bmap-tools-native' has been renamed as 'bmaptool-native'.
Adjust the references in the documentation accordingly.
Suggested-by: Khem Raj
Signed-off-by: Fabio Estevam
---
documentation/dev-manual/bmaptool.rst | 6 +++---
This also needs to reflect in docs.
On Tue, Mar 5, 2024 at 4:52 AM Trevor Woerner wrote:
>
> On Tue 2024-03-05 @ 11:59:17 AM, Richard Purdie wrote:
> > On Mon, 2024-03-04 at 14:25 -0500, Trevor Woerner wrote:
> > > The bmaptool (previously: bmap-tools, bmap-tool, bmaptool) has been moved
> > >
From: Ross Burton
If an image ends up with both matchbox-terminal and rxvt installed then
there are two Terminal applications that only differ in the description.
Rename the rxvt desktop entry to specifically identify itself as rxvt.
Signed-off-by: Ross Burton
---
On 4 Mar 2024, at 15:57, Peter Kjellerstedt via lists.openembedded.org
wrote:
> +modulesloaddir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
> '${nonarch_libdir}', '${sysconfdir}', d)}/modules-load.d"
> +modprobedir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
>
Will this work in the case of a system boot? I know if we load the kernel
directly to memory and boot, we can pass kernel command line through QEMU.
However many boards I have worked with in the past (and still do) do a system
level boot that starts with BIOS/Firmware, goes into a second stage
Extract the GNU build ID from all files containing debug symbols and
store it within the "extended" package information of pkgdata as an
attribute of the files contained within a package - e.g.
{
"files_info": {
"/lib/.debug/ld-linux-x86-64.so.2": {
"gnu_build_id":
So far, reading the "extended" data of a package stored within "pkgdata"
is not supported. Extend oe-pkgdata-util to support this use case.
For symmetry to `read-value` and `package-info` it expects the runtime
package name as its package name. Passing in multiple packages is not
supported as
This is the follow up to "package.bbclass: Expose list of split out
debug files" adding the extraction of the build IDs directly into the
do_package task.
Build IDs are stored inside the "extended" section of the pkgdata and to
enable easier testing the "read-extended" command is added to
As correctly determining the list of debug files based on existing
variables is non-trivial, this patch introduces the PKGDEBUGFILES
variable which holds the path to all files generated during stripping.
This list may then be used for further processing, such as extracting
the GNU build ID of all
Current Dev Position: YP 5.0 M3 - Feature Freeze
Next Deadline: 19th February 2024 YP 5.0 M3 build
Next Team Meetings:
-
Bug Triage meeting Thursday March 7th at 7:30 am PST (
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
-
Weekly Project Engineering Sync
Richard Purdie escreveu (domingo,
3/03/2024 à(s) 16:31):
> On Fri, 2024-03-01 at 09:53 +, Richard Purdie via
> lists.openembedded.org wrote:
> > On Wed, 2024-02-28 at 18:30 +, Jose Quaresma wrote:
> > > Upgrade to latest 1.21.x release [1]:
> > >
> > > $ git --no-pager log --oneline
Richard Purdie escreveu (domingo,
3/03/2024 à(s) 23:03):
> On Thu, 2024-02-29 at 22:19 +, Richard Purdie via
> lists.openembedded.org wrote:
> > On Thu, 2024-02-29 at 21:42 +, Jose Quaresma wrote:
> > >
> > >
> > > A quinta, 29/02/2024, 09:35, Jose Quaresma via
> > >
Enable libseccomp-ptest in PTESTS_SLOW as
all tests are passing now.
Signed-off-by: Sourav Pramanik
---
meta/conf/distro/include/ptest-packagelists.inc | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/conf/distro/include/ptest-packagelists.inc
On Mon, Mar 4, 2024 at 1:29 PM Ross Burton wrote:
>
> On 3 Mar 2024, at 13:18, Peter Marko via lists.yoctoproject.org
> wrote:
> >
> > I already mentioned this last week.
> > https://lists.openembedded.org/g/openembedded-core/message/196199
> >
> > I think that partial NVD DB update is not
On Tue 2024-03-05 @ 11:59:17 AM, Richard Purdie wrote:
> On Mon, 2024-03-04 at 14:25 -0500, Trevor Woerner wrote:
> > The bmaptool (previously: bmap-tools, bmap-tool, bmaptool) has been moved
> > to be under the Yocto Project umbrella and is now hosted at:
> >
> >
On Mon, 2024-03-04 at 14:25 -0500, Trevor Woerner wrote:
> The bmaptool (previously: bmap-tools, bmap-tool, bmaptool) has been moved
> to be under the Yocto Project umbrella and is now hosted at:
>
> github.com/yoctoproject/bmaptool
>
> Signed-off-by: Trevor Woerner
> ---
>
LGTM, I'm sorry I've missed it when updating other types.
Signed-off-by: Martin Jansa
On Tue, Mar 5, 2024 at 9:46 AM Taedcke, Christian
wrote:
>
> From: Christian Taedcke
>
> Remove the appended ${IMAGE_NAME_SUFFIX}, since it is already included
> in ${IMAGE_NAME}.
>
> In commit 26d97acc7137
From: Christian Taedcke
Without this commit the configuration node includes the compatible
line 'compatible = [00];' if EXTERNAL_KERNEL_DEVICETREE is not
defined, i.e. if PREFERRED_PROVIDER_virtual/dtb is not used.
This prevents u-boot from using this configuration and it prints the
message
From: Christian Taedcke
Remove the appended ${IMAGE_NAME_SUFFIX}, since it is already included
in ${IMAGE_NAME}.
In commit 26d97acc7137 ("image-artifact-names: include
${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and
${IMAGE_LINK_NAME}") ${IMAGE_NAME_SUFFIX} was included into
32 matches
Mail list logo
