I have submitted this particular commit as v2:
https://lists.openembedded.org/g/openembedded-core/message/211391 as it fixes
an issue that, according to my understanding, prevents using the bbclass in
fashion that is compliant with Yocto reference manual.
-Niko
On 14.1.2025 17.37, Niko Mauno
From: Niko Mauno
According to Yocto reference manual, in description of the
IMAGE_LINK_NAME variable, it is said that
It is possible to set this to "" to disable symlink creation,
however, you also need to set :term:`IMAGE_NAME` to still have
a reasonable value e.g.::
IMAGE
On 15.1.2025 11.16, Niko Mauno via lists.openembedded.org wrote:
On 14.1.2025 17.57, Marta Rybczynska wrote:
On Tue, Jan 14, 2025 at 4:38 PM Niko Mauno via lists.openembedded.org
<http://lists.openembedded.org/
What about a common function to use in both cve-check.bbclass and vex.bbcl
On 14.1.2025 17.57, Marta Rybczynska wrote:
On Tue, Jan 14, 2025 at 4:38 PM Niko Mauno via lists.openembedded.org
<http://lists.openembedded.org/
What about a common function to use in both cve-check.bbclass and vex.bbclass?
I have so far been exposed to using cve-check.bbclass only, an
Remove import from context where it is never used.
Signed-off-by: Niko Mauno
---
meta/classes/cve-check.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 4bd9af4abf..9f0a08becd 100644
--- a/meta/classes/cve
Allow the method to work also when the user has overridden
IMAGE_LINK_NAME value as empty string.
Signed-off-by: Niko Mauno
---
meta/classes/vex.bbclass | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/classes/vex.bbclass b/meta/classes/vex.bbclass
index c9749d4ceb
is referenced in default values of both IMAGE_NAME and
IMAGE_LINK_NAME.
Signed-off-by: Niko Mauno
---
meta/classes-recipe/image-artifact-names.bbclass | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/classes-recipe/image-artifact-names.bbclass
b/meta/classes-recipe
Remove import from context where it is never used.
Signed-off-by: Niko Mauno
---
meta/classes/vex.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/classes/vex.bbclass b/meta/classes/vex.bbclass
index 01d4e52051..c9749d4ceb 100644
--- a/meta/classes/vex.bbclass
+++ b/meta/classes
Allow the method to work also when the user has overridden
IMAGE_LINK_NAME value as empty string.
Signed-off-by: Niko Mauno
---
meta/classes/cve-check.bbclass | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve
From: Anuj Mittal
(From OE-Core rev: a5c24e05e8397e2e353d2d27d9da98375f6ec036)
Signed-off-by: Anuj Mittal
Signed-off-by: Richard Purdie
---
.../sqlite/{sqlite3_3.45.1.bb => sqlite3_3.45.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/sqlite
E-Core rev: a951a900ce459191a9796a7069a1d3b658dda88f)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/conf/bitbake.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index ab4c6a2d9c..59ac1873e0 100644
--- a/meta/conf/bitbake.conf
+++ b
E-Core rev: ec032dd13a19e4d4a332f06ace87f1f02143c3b2)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/conf/bitbake.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 59ac1873e0..1f31b4fcb3 100644
--- a/meta/conf/bitbake.conf
+++ b
This variable was removed in
https://git.yoctoproject.org/poky/commit/?id=2f8806deb7655b37d6f8d12ff54680d6acf7a298
("bitbake.conf: drop VOLATILE_LOG_DIR, use FILESYSTEM_PERMS_TABLES instead")
so ensure that distributions become aware that it no longer has any
effect.
Signed-off-by:
This variable was removed in
https://git.yoctoproject.org/poky/commit/?id=2f46b6f27dfa3a9d5ad177900fcecfe64c3536f1
("bitbake.conf: drop VOLATILE_TMP_DIR, use FILESYSTEM_PERMS_TABLES instead")
so ensure that distributions become aware that it no longer has any
effect.
Signed-off-by:
The contents of the LICENSE file included in the current source code
package match those of Info-ZIP license, which seems to originate from
the year 2007:
This is version 2007-Mar-4 of the Info-ZIP license.
(From OE-Core rev: 3739a1af61ff6f0faca23bb565f9e71666953715)
Signed-off-by: Niko Mauno
was then changed to
LICENSE.md in 2022 commit
https://gitlab.com/libtiff/libtiff/-/commit/fa1d6d787fc67a1eeb3abccb790b5bee969d424b
(From OE-Core rev: 71d8e8b03349ab18dca558055c2b3a3687785ddf)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/recipes-multimedia/libtiff/tiff_4.3.0.bb
=50fbdd118dba066e201c73a8b0155381cd65a32d
("* COPYING: Update to GPL version 3.")
(From OE-Core rev: 26b71cfb7815a096c5962629801cc3bc85147284)
Signed-off-by: Niko Mauno
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/dejagnu/dejagnu_1.6.3.bb | 2 +-
1 file changed, 1
: f3ae58b741e4e6e3a5196ff75fcc4da6ee89d0b9)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/recipes-gnome/gcr/gcr_3.40.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-gnome/gcr/gcr_3.40.0.bb
b/meta/recipes-gnome/gcr/gcr_3.40.0.bb
index 8719884f25..7985339483 100644
--- a
The contents of the LICENSE file included in the current source code
package match those of Info-ZIP license, which seems to originate from
the year 2009:
This is version 2009-Jan-02 of the Info-ZIP license.
(From OE-Core rev: e7c9368e56a6ad90b4ffbba1b765e2b3a331c796)
Signed-off-by: Niko
=622c36ae94a880fb53f7f051f1b26616f5b553c1
("license under ISC").
(From OE-Core rev: 87da7445a2a77fe73e3524cd50112842e91235b6)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/recipes-connectivity/iw/iw_5.16.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
The contents of the LICENSE file included in the current source code
package match those of Info-ZIP license, which seems to originate from
the year 2007:
This is version 2007-Mar-4 of the Info-ZIP license.
(From OE-Core rev: 3739a1af61ff6f0faca23bb565f9e71666953715)
Signed-off-by: Niko Mauno
=50fbdd118dba066e201c73a8b0155381cd65a32d
("* COPYING: Update to GPL version 3.")
(From OE-Core rev: 26b71cfb7815a096c5962629801cc3bc85147284)
Signed-off-by: Niko Mauno
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/dejagnu/dejagnu_1.6.3.bb | 2 +-
1 file changed, 1
: f3ae58b741e4e6e3a5196ff75fcc4da6ee89d0b9)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/recipes-gnome/gcr/gcr_4.2.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-gnome/gcr/gcr_4.2.1.bb
b/meta/recipes-gnome/gcr/gcr_4.2.1.bb
index 26dc1d1bc6..7ffcc1b7a0 100644
--- a/meta
64c5b10b29f0bb8136)
Signed-off-by: Vesa Jääskeläinen
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
...n-architecture-name-resolvation-code.patch | 107 ++
...ation-issue-with-linux-armv7l-archit.patch | 76 +
...n-ABI-name-resolvation-code-as-helpe.patc
was then changed to
LICENSE.md in 2022 commit
https://gitlab.com/libtiff/libtiff/-/commit/fa1d6d787fc67a1eeb3abccb790b5bee969d424b
(From OE-Core rev: 71d8e8b03349ab18dca558055c2b3a3687785ddf)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/recipes-multimedia/libtiff/tiff_4.6.0.bb
The contents of the LICENSE file included in the current source code
package match those of Info-ZIP license, which seems to originate from
the year 2009:
This is version 2009-Jan-02 of the Info-ZIP license.
(From OE-Core rev: e7c9368e56a6ad90b4ffbba1b765e2b3a331c796)
Signed-off-by: Niko
=622c36ae94a880fb53f7f051f1b26616f5b553c1
("license under ISC").
(From OE-Core rev: 87da7445a2a77fe73e3524cd50112842e91235b6)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/recipes-connectivity/iw/iw_6.7.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
upstream bug report:
https://github.com/PyO3/maturin/issues/2203
Associated upstream pull request:
https://github.com/PyO3/maturin/pull/2204
Note - mitigation has not been tested with musl:
https://github.com/PyO3/maturin/pull/2204#issuecomment-2323952320
Signed-off-by: Vesa Jääskeläin
The contents of the COPYING file included in the current source code
package match those of LGPL-2.0 license, which seems to have been the
case since 2011 commit
https://gitlab.gnome.org/GNOME/gcr/-/commit/c6691faa0348ab087e99ab9bd9914e1d5e81fa14
Signed-off-by: Niko Mauno
---
meta/recipes-gnome
was then changed to
LICENSE.md in 2022 commit
https://gitlab.com/libtiff/libtiff/-/commit/fa1d6d787fc67a1eeb3abccb790b5bee969d424b
Signed-off-by: Niko Mauno
---
meta/recipes-multimedia/libtiff/tiff_4.6.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-multimedia
The contents of the LICENSE file included in the current source code
package match those of Info-ZIP license, which seems to originate from
the year 2009:
This is version 2009-Jan-02 of the Info-ZIP license.
Signed-off-by: Niko Mauno
---
meta/recipes-extended/unzip/unzip_6.0.bb | 2 +-
1
The contents of the LICENSE file included in the current source code
package match those of Info-ZIP license, which seems to originate from
the year 2007:
This is version 2007-Mar-4 of the Info-ZIP license.
Signed-off-by: Niko Mauno
---
meta/recipes-extended/zip/zip_3.0.bb | 2 +-
1 file
=50fbdd118dba066e201c73a8b0155381cd65a32d
("* COPYING: Update to GPL version 3.")
Signed-off-by: Niko Mauno
---
meta/recipes-devtools/dejagnu/dejagnu_1.6.3.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/dejagnu/dejagnu_1.6.3.bb
b/meta/recipes-devtools/dejagnu/dej
On 9/1/24 13:55, Richard Purdie wrote:
On Sat, 2024-08-31 at 16:01 +0300, Niko Mauno via
lists.openembedded.org wrote:
Add stripping of STAGING_DIR_NATIVE during target/nativesdk specific
do_install, which mitigates following BitBake failure:
ERROR: icu-75-1-r0 do_package_qa: QA Issue: File
=622c36ae94a880fb53f7f051f1b26616f5b553c1
("license under ISC").
Signed-off-by: Niko Mauno
---
meta/recipes-connectivity/iw/iw_6.9.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-connectivity/iw/iw_6.9.bb
b/meta/recipes-connectivity/iw/iw_6.9.bb
index
do_package_qa: Fatal QA errors were found, failing task.
While doing so, we also drop HOSTTOOLS_DIR stripping, as it's value
does not appear in the content of either file that are manipulated
here.
Signed-off-by: Niko Mauno
---
meta/recipes-support/icu/icu_75-1.bb | 2 +-
1 file changed, 1 inse
low.
(From OE-Core rev: dc086d9a8613143607af3583c72ed892e20b4d66)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/recipes-core/util-linux/util-linux_2.39.3.bb | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/util-linux/util-linux_2.3
Thanks, submitted v6 which adds the new PACKAGECONFIG option for
class-target only.
-Niko
On 21.8.2024 15.17, Alexander Kanavin wrote:
I guess this new API should not be enabled for -native variants?
Alex
On Wed, 21 Aug 2024 at 14:01, Niko Mauno via lists.openembedded.org
wrote:
On
[0x7fa115e818]: failed to init new API
Note: In addition to the aforementioned, this change was tested also
briefly using the current latest kernel versions 6.1.104, 6.6.45 and
6.10.3 that using the old mount API with newest kernels did not
introduce any observable regression to the boot flow.
On 20.8.2024 22.19, Alexandre Belloni wrote:
Hello,
arm64 fails to build with this patch:
https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/9356/steps/13/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/131/builds/4727/steps/13/logs/stdio
Thanks, indeed it s
On 8/19/24 18:23, Peter Kjellerstedt wrote:
Please avoid negative PACKAGECONFIGs. Instead use:
PACKAGECONFIG[new-mount-api] =
"--enable-libmount-mountfd-support,--disable-libmount-mountfd-support"
and add "new-mount-api" to the default for PACKAGECONFIG.
Also, how long will the "new" in "ne
led to init new API
Note: In addition to the aforementioned, this change was
tested also briefly using the current latest kernel versions 6.1.104,
6.6.45 and 6.10.3 that using the old mount API with newest kernels
did not introduce any observable regression to the boot flow.
Signed-
fa115e818]: failed to init new API
Note: In addition to the aforementioned, this change was
tested also briefly using the current latest kernel versions 6.1.104,
6.6.45 and 6.10.3 that using the old mount API with newest kernels
did not introduce any observable regression to the boot flow.
Signe
Sorry, the comments added in this v3 still adhere to v2 content. I will
still submit v4 soon which amends to added comment lines.
-Niko
On 19.8.2024 12.29, Alexander Kanavin wrote:
Thanks, this version lgtm.
Alex
On Mon, 19 Aug 2024 at 11:27, Niko Mauno via lists.openembedded.org
wrote
On 19.8.2024 11.27, Alexander Kanavin wrote:
I don’t think this should be disabled by default actually. If the
default upstream behavior is to enable, and all current linux-yocto
kernels have the needed support, then we should follow that.
Thanks, addressed in v3 which I just submitted.
-Niko
fa115e818]: failed to init new API
Note: In addition to the aforementioned, this change was
tested also briefly using the current latest kernel versions 6.1.104,
6.6.45 and 6.10.3 that using the old mount API with newest kernels
did not introduce any observable regression to the boot flow.
Signe
On 16.8.2024 17.24, Alexander Kanavin wrote:
On Fri, 16 Aug 2024 at 16:04, Niko Mauno via lists.openembedded.org
wrote:
Taking the above findings into consideration, add a new PACKAGECONFIG
option which allows to conveniently opt-out from prematurely using a
feature which can cause issues
init new API
Note: In addition to the aforementioned, this change was
tested also briefly using the current latest kernel versions 6.1.104,
6.6.45 and 6.10.3 that using the old mount API with newest kernels
did not introduce any observable regression to the boot flow.
Signed-off-by: Niko Mauno
613cd3032cc2a2c6e3ff9)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/classes/image_types.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
index 9d5f8c68a4..722450
n which allows to conveniently opt-out from prematurely using a
feature which can cause issues with a bit older kernels.
Signed-off-by: Niko Mauno
---
meta/recipes-core/util-linux/util-linux_2.40.1.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/util-linux/util-linux_2.40.1.
613cd3032cc2a2c6e3ff9)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdie
---
meta/classes-recipe/image_types.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes-recipe/image_types.bbclass
b/meta/classes-recipe/image_types.bbclass
index 2f948ecbf8
ou want to overwrite (y/N) ?
not overwritten
| Error 20 : example-image.cpio : open file error
| WARNING: exit code 20 from a shell command.
ERROR: Task (.../recipes-core/images/example-image.bb:do_image_cpio) failed
with exit code '1'
Signed-off-by: Niko Mauno
---
meta/clas
/var/tmp" already exists
and is not a directory.
Mitigate the issue by defining /var/tmp as symlink corresponding to
the one created by base-files.
(From OE-Core rev: 1f1f6f45e3cfe24dfee8a09d01a5d32f3080e381)
Signed-off-by: Niko Mauno
Signed-off-by: Alexandre Belloni
Signed-off-by: R
emd-tmpfiles[165]: "/var/log" already exists
and is not a directory.
Mitigate the issue by defining /var/log as symlink corresponding to
the one created by base-files, when appropriate.
(From OE-Core rev: 711ee36e88c8968e3c45ea787b3adcf64352adf9)
Signed-off-by: Niko Mauno
Signed-off-by: Alex
On 8/2/24 17:25, Guðni Már Gilbert wrote:
I wonder if it would be good to backport this to Scarthgap. I'm getting
the following warning for unpatched CVE on latest scarthgap:
WARNING: libyaml-0.2.5-r0 do_cve_check: Found unpatched CVE
(CVE-2024-35328), for more information check
/home/builder/y
ck.bbclass:
WARNING: libyaml-native-0.2.5-r0 do_cve_check: Found unpatched CVE
(CVE-2024-35328), for more information check
.../tmp/work/x86_64-linux/libyaml-native/0.2.5/temp/cve.log
Signed-off-by: Niko Mauno
---
meta/recipes-support/libyaml/libyaml_0.2.5.bb | 2 ++
1 file changed, 2
From: Niko Mauno
Use an existing defined CVE_CHECK_STATUSMAP key in
meta/lib/oe/cve_check.py in order to avoid following complaint from
BitBake:
WARNING: libyaml-native-0.2.5-r0 do_create_spdx: Invalid detail "wontfix" for
CVE_STATUS[CVE-2024-35328] = "wontfix: Upstream thi
From: Niko Mauno
Mitigate occurrences where ':append' operator is used and leading
whitespace character is obviously missing, risking inadvertent
string concatenation.
(From OE-Core rev: 314041fd126a4800a5a5d9fcd84c525319479256)
Signed-off-by: Niko Mauno
Signed-off-by: Richard Purdi
On 7/9/24 18:43, Richard Purdie wrote:
On Tue, 2024-07-09 at 16:10 +0200, Alexandre Belloni via
lists.openembedded.org wrote:
Hello,
Can you submit one patch per recipe?
FWIW I tweaked the shortlog prefix in master-next to mesa/dnf: which
resolves this case.
Cheers,
Richard
Apologies, I f
From: Niko Mauno
By adding a leading space character in the value field of appended
BitBake variable, we avoid the risk of inadvertent string
concatenation.
Signed-off-by: Niko Mauno
---
meta/recipes-devtools/dnf/dnf_4.20.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Niko Mauno
By adding a leading space character in the value field of appended
BitBake variable, we avoid the risk of inadvertent string
concatenation.
Signed-off-by: Niko Mauno
---
meta/recipes-graphics/mesa/mesa.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
On 7/4/24 10:49, ChenQi wrote:
There's a pending patch from Changqing, which also handles /var/tmp.
The title is: [OE-core] [PATCH] VOLATILE_TMP_DIR: Extend to specify the
persistence of /var/tmp
I think we'd better handle that patch first because you may need to
change to the way you used in
From: Niko Mauno
When VOLATILE_LOG_DIR evaluates as True, the base-files recipe provides
/var/log -> /var/volatile/log symlink which is in conflict with systemd
upstream tmpfiles.d/var.conf.in which defines it as a directory.
This generates following error in journal:
Jul 03 14:28:00 qemu
From: Niko Mauno
Mitigate occurrences where ':append' operator is used and leading
whitespace character is obviously missing, risking inadvertent
string concatenation.
Signed-off-by: Niko Mauno
---
meta/recipes-devtools/dnf/dnf_4.20.0.bb | 2 +-
meta/recipes-graphics/mesa/mesa.i
From: Niko Mauno
When VOLATILE_LOG_DIR evaluates as True, the base-files recipe provides
/var/log -> /var/volatile/log symlink which is in conflict with systemd
upstream tmpfiles.d/var.conf.in which defines it as a directory.
This generates following error in journal:
Jul 03 14:28:00 qemu
From: Niko Mauno
The base-files recipe provides /var/tmp -> /var/volatile/tmp symlink
which is in conflict with systemd upstream tmpfiles.d/tmp.conf which
defines it as a directory (or subvolume on btrfs).
This generates following error in journal:
Jul 03 15:37:21 qemux86-64 systemd-tmpfi
From: Niko Mauno
Move the default value into a variable which can be overridden to
match more accurately the use case specific scenario.
(From OE-Core rev: 645370e85d8742d0614cd52ca7507b5df2d38ad8)
Signed-off-by: Niko Mauno
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
From: Niko Mauno
Move the default value into a variable which can be overridden to
match more accurately the use case specific scenario.
Signed-off-by: Niko Mauno
---
meta/recipes-devtools/rust/rust-llvm_1.70.0.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta
From: Niko Mauno
Since ccache version 4.0, according to
https://github.com/ccache/ccache/blob/master/doc/NEWS.adoc#ccache-40
* An appropriate cache directory level structure is now chosen automatically.
The cache_dir_levels (CCACHE_NLEVELS) configuration option has therefore been
removed
From: Niko Mauno
Commit ef0654f1453ff0afe98d7e921626b2a96cf2f6f6
("Set XZ_COMPRESSION_LEVEL to -9") changed the xz compression preset
level from previous value of -3 to -9. The commit message explains that
the change was made in order to be consistent with other compressors
that also
From: Niko Mauno
Commit 4a4d5f78a6962dda5f63e9891825c80a8a87bf66 ("package_rpm: use zstd
instead of xz") changed the rpm package compressor from 'xz' to 'zstd'
which results in decompression failure with BusyBox-provided 'rpm2cpio'
applet and 'rpm
On 20.10.2023 19.34, Khem Raj wrote:
> it seems you are quite sensitive to size, I wonder if opkg backend is
> better suited for your usecase than rpm.
Hi Khem, thanks for the idea. We used opkg a few years ago, however
certain technical reasons were in favor of rpm which we have used since.
Perh
On 10/20/23 16:00, Richard Purdie wrote:
As far as I could tell when we looked at this, the rpm world was moving
over to zstd so adding in conditional xz support for a limited use case
probably just creates a maintenance headache going forward as it isn't
something we test or plan to test?
I no
From: Niko Mauno
Commit 4a4d5f78a6962dda5f63e9891825c80a8a87bf66 ("package_rpm: use zstd
instead of xz") changed the rpm package compressor from 'xz' to 'zstd'
which results in decompression failure with BusyBox-provided 'rpm2cpio'
applet and 'rpm
From: Niko Mauno
Some local variables defined in do_package_rpm() are not referenced, so
remove such dead code lines.
Signed-off-by: Niko Mauno
---
meta/classes-global/package_rpm.bbclass | 4
1 file changed, 4 deletions(-)
diff --git a/meta/classes-global/package_rpm.bbclass
b/meta
From: Niko Mauno
Add the missing conventional space characters around bitbake variable
assignment operators. Also fix a typo on a comment line.
Signed-off-by: Niko Mauno
---
meta/classes-global/package_rpm.bbclass | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta
From: Niko Mauno
Fix following subset of observations reported by version 2.10.0 of
pycodestyle utility:
meta/classes-global/package_rpm.bbclass:65:46: E231 missing whitespace after
','
meta/classes-global/package_rpm.bbclass:66:46: E231 missing whitespace after
','
On 20.10.2023 16.00, Richard Purdie wrote:
Is it common for people to need to manipulate rpms on target without
rpm being present using busybox? Do you know if busybox plans to add
zstd support?
As far as I could tell when we looked at this, the rpm world was moving
over to zstd so adding in c
From: Niko Mauno
Commit 4a4d5f78a6962dda5f63e9891825c80a8a87bf66 ("package_rpm: use zstd
instead of xz") changed the rpm package compressor from 'xz' to 'zstd'
which results in decompression failure with BusyBox-provided 'rpm2cpio'
applet and 'rpm
From: Niko Mauno
Some local variables defined in do_package_rpm() are not referenced, so
remove such dead code lines.
Signed-off-by: Niko Mauno
---
meta/classes-global/package_rpm.bbclass | 4
1 file changed, 4 deletions(-)
diff --git a/meta/classes-global/package_rpm.bbclass
b/meta
From: Niko Mauno
Add the missing conventional space characters around bitbake variable
assignment operators. Also fix a typo on a comment line.
Signed-off-by: Niko Mauno
---
meta/classes-global/package_rpm.bbclass | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta
From: Niko Mauno
Fix following subset of observations reported by version 2.10.0 of
pycodestyle utility:
meta/classes-global/package_rpm.bbclass:65:46: E231 missing whitespace after
','
meta/classes-global/package_rpm.bbclass:66:46: E231 missing whitespace after
','
n Wed, May 17, 2023 at 12:06 AM Niko Mauno via lists.openembedded.org
wrote:
From: Khem Raj
some standalone targets e.g. riscv64-elf disable shared linking for
baremetal ELF ABI in ld, therefore lets make it a static library
(From OE-Core rev: 3c6219dfcbcbde314648ba8cc54a90b32ea1c952)
Sig
From: Khem Raj
some standalone targets e.g. riscv64-elf disable shared linking for
baremetal ELF ABI in ld, therefore lets make it a static library
(From OE-Core rev: 3c6219dfcbcbde314648ba8cc54a90b32ea1c952)
Signed-off-by: Khem Raj
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/gcc
From: Mark Hatle
When building with the previous a number of atomic functions come back as
undefined. Switching to linux-latomic fixes this.
(From OE-Core rev: 88d5bf78ffb1d120df48139b1ed3c2e3fa8310d0)
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
Signed-off-by: Luca Ceresoli
Signed-o
On 20.2.2023 19.45, Michael Opdenacker wrote:
Thanks for the patch!
You also have an issue with the way your e-mails are received here. Here
is a workaround:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Fixing_your_From_identity
I fixed the commit manually, but doin
ture.
Signed-off-by: Niko Mauno
---
documentation/ref-manual/features.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/ref-manual/features.rst
b/documentation/ref-manual/features.rst
index 794a6fd15b..051bf9320a 100644
--- a/documentation/ref-manua
Mitigate occurences where ':append' operator is used and leading
whitespace character is obviously missing, risking inadvertent
string concatenation.
(From OE-Core rev: fcd340ec53ff8352b8cae0eb351810072b025a08)
Signed-off-by: Niko Mauno
Signed-off-by: Alexandre Belloni
Signed-off-b
Mitigate occurences where ':append' operator is used and leading
whitespace character is obviously missing, risking inadvertent
string concatenation.
(From OE-Core rev: fcd340ec53ff8352b8cae0eb351810072b025a08)
Signed-off-by: Niko Mauno
Signed-off-by: Alexandre Belloni
Signed-off-b
Mitigate occurences where ':append' operator is used and leading
whitespace character is obviously missing, risking inadvertent
string concatenation.
Signed-off-by: Niko Mauno
---
meta/classes-recipe/core-image.bbclass | 2 +-
meta/classes-recipe/populate_sdk_ext.bbcl
)
Signed-off-by: Niko Mauno
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
---
meta/recipes-core/systemd/systemd_244.5.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/systemd/systemd_244.5.bb
b/meta/recipes-core/systemd/systemd_244.5.bb
ions from glibc.
/Ola
On Tue, Nov 08 2022, Niko Mauno via lists.openembedded.org wrote:
Add default C Preprocessor flags that ensure Y2038 compatible 64 bit
time on 32 bit host applications when glibc is used. Prerequisites
are glibc version 2.34 or newer and Linux kernel version 5.1 or new
)
Signed-off-by: Niko Mauno
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
---
meta/recipes-core/systemd/systemd_250.5.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/systemd/systemd_250.5.bb
b/meta/recipes-core/systemd/systemd_250.5.bb
ov 2022 at 12.48, Niko Mauno <mailto:niko.ma...@vaisala.com>> wrote:
I have not studied the issue, but in order to reproduce this error I
add
'MACHINE = "qemuarm"' to local.conf then issue 'bitbake kbd' against
current master while
2022 11.14, Alexander Kanavin wrote:
We do build for 32 bit arm targets, so is this seen only in specific
circumstances? What are they?
Alex
On Tue, 8 Nov 2022 at 01:09, Niko Mauno via lists.openembedded.org
wrote:
For now add exemption in order to avoid following failure during
do_compile()
block size: %lu, rounding down",
block_size);
| | ^~~~
~~
| ||
| |
size_t {aka unsigned int}
Signed-off-by: Niko Mauno
---
meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-multimedia/pulseaudio/pulsea
/libtswrap.ver:2:
syntax error in VERSION script
| collect2: error: ld returned 1 exit status
Signed-off-by: Niko Mauno
---
meta/recipes-core/kbd/kbd_2.5.1.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-core/kbd/kbd_2.5.1.bb
b/meta/recipes-core/kbd/kbd_2.5.1.bb
index aa3ab6e121
e useful e.g. when working around failure to compile a
component due to lack of 64 bit time support on 32 bit build in the
component's source code.
Signed-off-by: Niko Mauno
---
meta/conf/distro/include/tclibc-glibc.inc| 3 +++
meta/recipes-devtools/gcc/gcc-sanitizers_12.2.b
Since RRECOMMENDS declaration implictly induces building the recipes
that provide the runtime recommended packages, conditionalize adding
such values according to associated PACKAGECONFIG settings in order
to avoid redundant building.
Signed-off-by: Niko Mauno
---
meta/recipes-core/systemd
not
seem to contain any other change, except total of 167 entries like
CVSS v3 BASE SCORE: 0.0
were replaced with similar 'CVSS v3 BASE SCORE:' entries which had
scores that were greater than '0.0' (up to '9.8').
(From OE-Core rev: cc20e4d8ff2f3aa52a2658404af9a0ff
1 - 100 of 143 matches
Mail list logo
